@tangle-network/traces 0.15.1 → 0.15.4

package/README.md

@@ -214,7 +214,7 @@ not the way to integrate a system you own — for that, [emit the contract](#int
 
 | Harness (aliases) | Reads from | Status |
 |---|---|---|
-| `claude-code` (`claude`, `claudish`, `openclaw`, `nanoclaw`) | `~/.claude/projects/<cwd>/*.jsonl` (+ subagent sidechains) | verified |
+| `claude-code` (`claude`, `claudish`, `openclaw`, `nanoclaw`) | `~/.claude/projects/<cwd>/*.jsonl` (+ subagent sidechains), or an explicit `claude -p --output-format stream-json --verbose` JSONL file | verified |
 | `codex` (`codex-acp`) | `~/.codex/sessions/**/rollout-*.jsonl` | verified |
 | `codex-exec` (`codex-json`) | explicit `codex exec --json` JSONL file | fixture |
 | `opencode` | `~/.local/share/opencode/storage/` | verified |
@@ -228,6 +228,8 @@ not the way to integrate a system you own — for that, [emit the contract](#int
 
 Every adapter captures the conversation stored in one session file: the **user's prompt** and the **assistant's response** text, plus tool calls/results and token usage.
 Claude Code's nested subagent files are folded into the parent trace.
+Claude Code's stream-json output also records the tools the harness offered the model and whether the run failed.
+The root span keeps them as `gen_ai.tool.definitions` and `run.status`, so a trace contract can check what the harness enforced.
 Claude source UUIDs remain searchable in `traces.claude.source_*` attributes, while exported OTLP IDs use deterministic `deriveHexId` values.
 The Claude transcript proves turns and tool calls, but does not prove loop iterations or causal links, so those fields remain absent.
 Codex stores each worker in a separate session file; add `--workflow` to resolve the connected coordinator and worker files.
@@ -257,6 +259,7 @@ traces convert  --harness claude-code --last 1 --otlp-out spans.jsonl   # OTLP o
 traces index    --all --since 24h --out session-index.json
 traces bundle   --harness claude-code --session <id|path> --out bundle-dir   # one session's durable evidence dir
 traces bundle-view bundle-dir --view evidence-only --out writer-dir   # same session, without its own words
+traces bundle verify bundle-dir                                        # every file against its manifest SHA-256
 traces inspect  session-index.json --out inspection-report.md
 traces evidence --harness codex --last 20 --out policy-evidence.jsonl
 traces evidence --harness codex-exec --session /tmp/codex.jsonl --cwd "$PWD" --out policy-evidence.jsonl
@@ -612,6 +615,18 @@ The allow-list is the structure. A content check is the proof it is right: befor
 
 A projected view also carries the full bundle's `manifest.json` hash, so an auditor can prove which record it came from. Projecting a view of a view is refused.
 
+### Verify a bundle
+
+```bash
+traces bundle verify bundle-dir            # VERIFIED, or FAILED with each difference; exit 1 on failure
+traces bundle verify writer-dir --format json
+```
+
+`bundle verify` checks every file the manifest lists for its recorded size and SHA-256.
+It reports a listed file that is missing, a file on disk that the manifest does not list, a manifest path that is absolute or climbs out of the directory, and any symbolic link.
+For a projected view it also checks that the full bundle it names still has the manifest bytes the view recorded; a moved or deleted source is `unavailable`, not a failure.
+It proves the bytes are the bytes `traces` wrote. It does not prove who wrote them: anyone who can rewrite a file can rewrite the manifest.
+
 ## Policy-mining evidence
 
 `traces` does **not** emit benchmark campaign cells. It emits normalized coding-agent session evidence that another system can mine.
@@ -665,7 +680,7 @@ halo spans.openinference.jsonl --prompt "Analyze this trace slice" --max-turns 1
 `traces export` accepts:
 
 - compact `traces.policy_evidence.session` JSONL from `traces evidence`
-- JSON arrays with `start`, `raw`, `result`, `done`, and `error` events
+- JSON arrays with `start`, `raw`, `result`, `done`, and `error` events. A tool call becomes one span, keyed by its message part id, however many events report on that part. The Sandbox SDK records each call as a `message.part.updated` event and again as the harness's raw `tool_use` event. The span takes its start from the part's first event, its final state from the last, and `ERROR` if any event reported one. The root span's `traces.event.tool_part_updates_merged` counts the events folded in.
 - existing OpenInference JSONL, rewritten through the local redaction path
 - chat message arrays and objects with a `messages` array