Test Evidence is a standalone command, and, for any caller entitled to Claim Check's full mode, it's also automatically composed into shipmoor claim-check as one more concurrent evidence producer over the same change surface. How passed, reduced, and weakened each land in the gate, what changes without the hook wired, and running Test Evidence directly in CI.
The full depth on the three signals shipmoor test-evidence reports: passed (deterministic, harvested with three assurance levels), reduced (a test-id set difference that catches a deleted test), and weakened (a judgment-only signal whose schema makes a pass literally unrepresentable). Includes the anti-gaming design and findings measured in Shipmoor's own evaluation harness.
Wire the PostToolUse hook into your coding agent, run shipmoor test-evidence over a real change, and read your first passed, reduced, and weakened report in about five minutes.
Test Evidence checks whether a coding agent's tests actually ran and passed, whether the test surface was quietly shrunk, and whether a kept test was gutted so it can never fail again. Two signals are fully deterministic; the third rides Claim Check's judge machinery and can only ever flag weakened or stay silent, never certify a pass.
The complete shipmoor test-evidence surface in v0.8.0: the positional target, the --staged/--diff/--all/--from/--to selectors, the --agent weakened-test judge, --high-assurance, --attest-out, --json, --terse, --no-color, exit codes, the hook subcommand, and the test_evidence: config block.