gensokyo-dev
a989c0e458
Declare logical Evidence sources once and resolve exact retained inputs through shared application workflows across 20 composition tools. Preserve domain-owned authentication, source closure, caller choices, coverage and resource admission. Validation includes public CLI/MCP regressions, local Codex terra/high trials and fresh-import real-artifact workflows. Measurements, failed attempts and coverage limits are recorded in docs/verification/evidence-input-composition-2026-10-31.md. Fixes #8293. Fixes #8281. Assisted-by: Suika (gensokyo-skills:suika-scatter-gather-planning)
Analysis verification test support
These files support the existing comparison, independent-oracle, receipt and
cleanup regressions. The TypeScript consumers live in tests/boundary/,
tests/evaluation/ and tests/conformance/; npm run test:python discovers
the Python checks here. Build first for checks that use the compiled runtime.
The agent-harness tests inject command outcomes and own temporary workspaces. They do not invoke a real model or establish real-provider behavior. The retained resource observer keeps its process-family CPU, memory and cleanup guards. Public corpus identities and original receipt provenance stay intact.
The historical allocation report and receipt JSON belong to documentation. Their numerical sections are produced and checked by:
node tests/support/analysis-efficiency/mcp-integer-report.mjs --check
The full experiment suite was retired. For historical reproduction, use the recorded runtime and producer revisions; the archived source tree preserves the former layout. Current deterministic checks do not requalify those historical measurements.