final-branch-auditlisted

# Final Branch Audit Trace EVERY criterion of the source spec to the plan tasks that cover it, then walk EVERY task and prove, one at a time, that its acceptance criteria were delivered — with `file:line` citations the auditor located itself. **This is not a code review.** The code reviewer judges the quality of the diff it is handed. The audit answers a different question: *was everything the plan asked for actually built?* A branch passes code review with three tasks silently missing, because a missing task produces no diff to criticize. **Read-only.** The auditor fixes nothing, commits nothing, and never mutates the working tree, the index, HEAD, or branch state. It reports; the controller routes the gaps into the fix wave. **Evidence-or-zero.** A criterion with no located citation is NOT DELIVERED. There is no "probably done", no "looks implemented", no partial credit. ## When to Use - After the last task of a plan, BEFORE the final code review (superpowersplus:subagent-driven-development dispatches it there) - Before presenting merge options (superpowersplus:finishing-a-development-branch requires it) - Any time you inherited a branch and need to know what the plan promised versus what the branch contains ## The Spec Is the Root, Not the Plan The plan is an artifact under audit, not the requirement. A spec requirement the plan dropped in translation leaves no trace in the plan — checking the plan against itself can never find it. **Where the spec comes fro