From the 0.11.0 field report (the trace-audits-itself session; findings 1-2 fixed in c9c9a7b).
ToolCallEvidence carries paths, mutation_capable, mutates_workspace, reads — but not what the call actually did. Paths cover Edit/Write fine, but for Bash only redirect targets survive (extractRedirectPaths), so a mutation record for a Bash step answers "did it touch the workspace" while hiding how. The reporter had to open the raw JSONL to learn what each Bash mutation ran. An audit trace's whole job is "what did it touch".
Fix: add a bounded one-line summary field to ToolCallEvidence, populated for command-carrying tools from the command text — condenseCommandText (internal/trace/analysis.go) already exists for narration and can be reused with a short budget. Keep paths as-is.
Priority: P1 (usefulness). Next trace schema touch.
From the 0.11.0 field report (the trace-audits-itself session; findings 1-2 fixed in c9c9a7b).
ToolCallEvidencecarriespaths,mutation_capable,mutates_workspace,reads— but not what the call actually did. Paths cover Edit/Write fine, but for Bash only redirect targets survive (extractRedirectPaths), so a mutation record for a Bash step answers "did it touch the workspace" while hiding how. The reporter had to open the raw JSONL to learn what each Bash mutation ran. An audit trace's whole job is "what did it touch".Fix: add a bounded one-line
summaryfield toToolCallEvidence, populated for command-carrying tools from the command text —condenseCommandText(internal/trace/analysis.go) already exists for narration and can be reused with a short budget. Keep paths as-is.Priority: P1 (usefulness). Next trace schema touch.