Jev test output interpretation asks what a supplied runner transcript establishes. This example covers a passing summary, a failing assertion and output that cannot support either conclusion. The exit code is deliberately absent. The model labels the reported text; it does not reconstruct process metadata that was never captured.
An API-collected X post about agentsreplay described this specific problem: a pipeline can lose the test command's exit status, leaving an agent with text to inspect. Our original exercise supplies short runner-like records and preserves their provenance. The separate agent-claim sample contains no runner output. Saying all tests passed is not the same evidence as a captured test summary.
The official TypeSafe workflow guide recommends keeping deterministic work in code. If you can preserve a runner's structured report and actual exit code, use those directly. This page addresses the narrower case where text survived but the status did not. It does not install the source replay tool or measure the reliability of an entire coding agent.