morluto
60149282fc
* test: strengthen integration oracles and verification * test: bound lifecycle gates and strengthen workflow checks * test: verify complete paged and extracted results * test: preserve bytecode and cancellation evidence * test: strengthen retained evidence and fixture cleanup * test: require cross-projection bridge identities * test: retain fixture owners through cleanup failures * test: verify graph examples and project selectors * test: tighten provider and lifecycle regressions * test: consolidate hex coverage and bound cutter cleanup * test: bound subprocess output waits and strengthen graph checks * test: check mcp recovery and preserve cleanup owners * test: verify structured mcp argument failures * test: preserve artifact cleanup and gdb limit evidence * test: preserve evidence identities and bound provider gates * test: retain browser and comparison cleanup owners * test: bound startup and strengthen fixture oracles * test: bound lifecycle gates and verify recovered evidence * test: verify public outcomes and lifecycle ownership * test: assert precise evidence and release lifecycle gates * test: verify selected facts and bound cleanup waits * test: check retained evidence and decoded records * test: verify final reports and retain cleanup ownership * test: bound reviewed startup gates and retain cleanup * test: verify PE errors and preserve MCP cleanup * test: preserve MCP fixture cleanup ownership * test: release provider gates before late startup
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.