verificationlisted

# Nebu Verification Match the proof to the claim. Bigger claim, stronger evidence. ## Verification Match the proof to the claim. Bigger claim, stronger evidence. - **One bug fixed:** reproduce the bug path and show the focused proof now passes - **Feature works:** run targeted tests and exercise the important path - **Ready to merge or hand off:** run the relevant suite, build, or lint checks that cover the touched surface ### Rules 1. Use fresh evidence, not memory. 2. Verify the original symptom when possible, not just nearby tests. 3. Say plainly what was not checked. 4. Do not inflate a partial check into a full-success statement. ## Workspace wrap-up Close out multi-repo work: verify integrated state, leave the workspace intentional. 1. Identify every repo touched by the task. 2. Use the repo's existing wrap-up helper or state system when one exists. 3. Check each repo: branch of record, remote target, working tree cleanliness. 4. Define the proof target for each repo before mutating anything. 5. Remove disposable worktrees before disposable branches; leave branch of record clean. 6. Before final claim, check whether the session exposed a reusable workflow improvement. 7. Claim completion only when every touched repo is either reconciled or explicitly blocked. ## Use with - `code-review` before verification when meaningful code changed - `agent-workflows` when multiple agents or terminals touched different repos - `writing-nebu-skills` when the session uncover