Extract Proof Command Handlers

`registerProofCommand` is 1695 lines — a single function containing 8 inline action handlers for the proof subcommands. A developer navigating proof.ts has to scroll through the entire function to find the audit handler at line 1607 or the stale handler at line 2226. The function is structurally correct — each handler is self-contained — but it violates "finished means a stranger can extend it." A stranger adding a new proof subcommand would need to understand the full 1695-line function body to know where to add it.

verdict PASSscore 24 / 24findings 3 (0 risk · 2 debt · 1 obs)duration 19h 55mrejection cycles 0shipped May 25, 2026surface cli

Pipeline timeline

Intent to proven code in 19h 55m across Think, Plan, Build, and Verify.

Think
42m
Plan
5m
Build
9m
Verify
4m

Assertion ledger

24 claims, each independently verified. Showing 8 — show all →

IDSaysMatcher
A001The registration function is compact enough to read in one screenverifiedok
A002The list/detail handler exists as a standalone functionverifiedok
A003The context handler exists as a standalone functionverifiedok
A004The close handler exists as a standalone functionverifiedok
A005The promote handler exists as a standalone functionverifiedok
A006The strengthen handler exists as a standalone functionverifiedok
A007The audit handler exists as a standalone functionverifiedok
A008The health handler exists as a standalone functionverifiedok

Findings 3 total

debtpackages/cli/src/commands/proof.ts→ closed
Inconsistent body indentation in extracted handlers — 4-space for root, 6-space for subcommands, project standard is 2-space
debtpackages/cli/src/commands/proof.ts→ closed
~1560 lines of handler body at 6-space indent from verbatim extraction — visual noise when reading top-level functions
obs→ closed
Contract A001 matcher says greater/0 but intent is under-150 — mechanical check weaker than stated goal

Integrity seal

scopesha256:2178efc8b6979...
contractsha256:44803a6698e90...
plansha256:b6384529703c2...
specsha256:861a9dacad688...
build-reportsha256:9ec530b289f23...
build-datasha256:431da980575cd...
verify-reportsha256:a7e5f002551d8...
verify-datasha256:4a8f74dfebd52...
audit cmd$ ana proof audit extract-proof-handlers   → all hashes match