mirror of
https://github.com/n8n-io/n8n.git
synced 2026-10-22 20:41:50 +02:00
9b6843af28
The comparison report priced two arms against each other but said nothing about whether the context layer delivered. Cost alone cannot tell a better context system from a cheaper one that fetches nothing, which is the comparison the report exists to support. Read the per-iteration context/build classification the harness now persists, and print a per-arm tally under each arm's cost summary, ordered so it reads as a diagnosis: never retrieved, present but unused, context used, passed without it. The last cell is there deliberately. A working approach moves iterations out of `never retrieved`; it must not move them into `passed without it`, which is the build succeeding while the context lacked the fact — something other than the context system carried it, and crediting the system there would flatter it. The field is optional, and absent renders nothing rather than an empty tally: a results file recorded before the harness wrote the classification genuinely has none, and "not measured" must not read as "measured, found nothing". A cell name the report has not been taught to order is still printed rather than dropped, so a future classification cannot go silently missing. |
||
|---|---|---|
| .. | ||
| args.ts | ||
| build-cost-report.ts | ||
| build-mcp-manifest.ts | ||
| compare-pairwise.ts | ||
| index.ts | ||
| langtracer-push.ts | ||
| mcp-builder.ts | ||
| pairwise.ts | ||
| report.ts | ||
| serve-fixture.ts | ||