review-deliverylisted

# Review before delivery Review the actual diff, acceptance criteria and test output for the named final revision. Use [the review template](../deliberate-dev/assets/review.md). A passing test suite is an input to review, not a substitute for it. Perform these three passes on every task: - **Correctness / QA:** acceptance coverage, edge and error cases, regressions, relevant red-before-green evidence, and tests that could catch the implementation being wrong. Confirm worktree and revision identities against actual Git state. - **Security:** changed trust boundaries, authorization, untrusted input, injection, secrets in logs, unsafe filesystem/shell operations, dependency changes and sensitive data handling. Test a relevant abuse case when the change introduces such a boundary. Record a reason if an area is not applicable; avoid unrelated hardening scope. - **Quality / architecture:** clear ownership/interfaces, maintainability, complexity, compatibility, failure handling, and whether the diff remains within the brief. Inspect conflicts and generated code just as carefully as handwritten code. When subagents are available, request an independent reviewer with the brief, task, final revision, diff and evidence. Keep the reviewer read-only unless explicitly assigning a fix to its own task worktree. Without subagents, perform separate self-review passes and state that limitation. Never claim several people or independent agents reviewed work when they did not. For each findi