verification-before-completionlisted

# Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. **Core principle:** Evidence before claims, always. **Violating the letter of this rule is violating the spirit of this rule.** ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` If you haven't run the verification command in this message, you cannot claim it passes. ## CRITICAL: Green Tests ≠ Done **Tests passing is a floor, not a ceiling.** Passing all tests only proves the code doesn't visibly break existing expectations — it does NOT prove the work meets the user's actual request. ``` VERBOTEN: "All tests pass → task complete" "CI is green → it works as requested" "No failures → requirements fulfilled" PFLICHT stattdessen: 1. Re-read the original user request / issue / spec 2. Compare actual output/behavior against each stated requirement 3. Only then: conclude whether the requirement is met ``` This rule applies even when 100% of tests pass. Even when CI is fully green. Even when the agent "feels confident". **Green tests prove regression safety. They do not prove intent fulfillment.** A task is done when the user's stated requirement is demonstrably satisfied — not when the test suite is happy. ## The Gate Function ``` BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. READ: Full output, ch