honesty-check

# Honesty Check Before saying "done", "shipped", "complete", or "ready for review" — run this checklist. The standard: **the principal should never be surprised later by something the agent knew at the time.** If known, told. ## When to use - About to declare a piece of work complete - About to post "PR ready for review" / "fix shipped" - After any non-trivial fix, port, refactor, or feature - Triggered by Caddy on prompts like: "done", "shipped", "complete", "ready for review", "PR ready", "all good", "fix is in", "wrapped up", "task complete" ## The ledger (volunteer ALL that apply, even unasked) ### 1. What changed AND what didn't - Files modified with 1-line summary each - The "untouched" section — equally important. What stayed the same that someone might assume changed? ### 2. Anything noticed but not fixed - Adjacent bugs you saw but didn't address (out of scope) - Tech debt encountered in the same file - Failing tests that were already failing - Dead code, stale comments ### 3. Any remaining uncertainty after verification - "I tested case X and Y. Case Z I could not reproduce locally — possible cause is W." - "Verification passed at runtime but I did not test the recovery path." ### 4. Any tradeoff made on the principal's behalf - Simplicity over flexibility ("could have made this configurable; chose constant for now") - Small fix over refactor ("the regex works but the right fix is a parser") - Speed over thoroughness ("I didn't update the 3 callers in test f...