@tangle-network/traces 0.11.0 → 0.11.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +161 -13
- package/dist/{chunk-JCI5YXNT.js → chunk-CK5F5TWO.js} +3566 -913
- package/dist/cli.js +208 -21
- package/dist/index.d.ts +1137 -9
- package/dist/index.js +167 -1
- package/docs/replay-batch-20260802.md +76 -0
- package/docs/replay-verify.md +105 -0
- package/package.json +6 -4
- package/skills/inspect-agent-traces/SKILL.md +31 -2
|
@@ -8,6 +8,34 @@ description: Inspect real agent workflows with the published Traces CLI and expo
|
|
|
8
8
|
Use the deterministic CLI first.
|
|
9
9
|
Keep inspection local and read-only.
|
|
10
10
|
|
|
11
|
+
## Choose the way in
|
|
12
|
+
|
|
13
|
+
If the trace is already OTLP (a system that emits `@tangle-network/agent-trace-contract`
|
|
14
|
+
spans, or any conforming exporter), read it directly. No adapter is involved.
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
traces validate spans.otlp.jsonl # what can this trace answer? exit 1 on error findings
|
|
18
|
+
traces analyze --otlp spans.otlp.jsonl --out .traces/current.md
|
|
19
|
+
traces analyze --otlp results/sessions --out .traces/all.md # a directory of exports
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
Use `--harness` only for coding agents whose on-disk format we do not control.
|
|
23
|
+
Those adapters are the legacy edge, not the way to integrate a system you own.
|
|
24
|
+
|
|
25
|
+
A directory is a run directory: it holds the span export beside raw event, stream and
|
|
26
|
+
SDK logs that are also `*.jsonl`. Only the OTLP files are read, and the rest are listed
|
|
27
|
+
with what they actually hold. An `otlp/` subdirectory, when the producer made one, is
|
|
28
|
+
read on its own.
|
|
29
|
+
|
|
30
|
+
Any section headed `inputs incomplete`, or carrying an `Inputs incomplete` line above
|
|
31
|
+
its table, is computed from a field the trace does not carry everywhere. Report those
|
|
32
|
+
numbers as uncaptured, never as zero spend. The `trace conformance` section at the top
|
|
33
|
+
names every such capability once; the markers repeat it where the number actually is.
|
|
34
|
+
|
|
35
|
+
For a loop trace, read `round-over-round convergence` (did round N+1 improve on N) and
|
|
36
|
+
`steering chain` (which verdict caused which retry) before drawing any conclusion about
|
|
37
|
+
whether the agent was making progress.
|
|
38
|
+
|
|
11
39
|
## Select the workflow
|
|
12
40
|
|
|
13
41
|
```bash
|
|
@@ -32,7 +60,7 @@ Write normalized OpenInference spans for another tool:
|
|
|
32
60
|
|
|
33
61
|
```bash
|
|
34
62
|
traces convert --harness codex --current --latest-turn --workflow \
|
|
35
|
-
--otlp .traces/current.otlp.jsonl
|
|
63
|
+
--otlp-out .traces/current.otlp.jsonl
|
|
36
64
|
```
|
|
37
65
|
|
|
38
66
|
Write the complete deterministic review packet:
|
|
@@ -47,7 +75,8 @@ It does not edit an agent, repository, memory store, or knowledge base.
|
|
|
47
75
|
|
|
48
76
|
## Report
|
|
49
77
|
|
|
50
|
-
- State the harness, selected task boundary, session and span counts, and integrity warnings.
|
|
78
|
+
- State the source (`--otlp <path>` or the harness), selected task boundary, session and span counts, and integrity warnings.
|
|
79
|
+
- State which capabilities the trace could not support, and name the analyses that reported nothing because of it.
|
|
51
80
|
- Cite each finding with its exact `trace://` reference.
|
|
52
81
|
- Mark missing outcome, cost, token, skill, or relationship data as unknown.
|
|
53
82
|
- Do not infer task success from a completion message.
|