One documented exit-code table across the verification commands

## Gap Each verification command carries its own exit-code contract, documented (at best) in its own module: | Command | Codes observed | |---|---| | `replay --verify` | 0 intact / 1 divergence | | `verify receipt` | 0 verified / 1 malformed / 2 tamper | | `lineage verify ` | 0 / 1 intact-but-partial (SEAL ONLY) / 2 / 3 | | `audit verify` | 0 all pillars / 1 any pillar failed | An operator scripting CI gates has to read four sources to know what a nonzero code means, and nothing stops the contracts drifting. ## What to write One docs table covering every verification command's exit codes and verdict strings, plus a test per command asserting the documented codes on a fixture run (pass case + one failure case each), so drift breaks CI instead of operators. ## Acceptance criteria - Docs table exists and is linked from the verification docs entry point. - Tests pin each documented code; changing a code without updating the table fails CI. ## Out of scope Changing any exit code (that would be its own issue per command). Questions welcome in this thread.