story-donelisted

# Story Done Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" → "yes", asked as an `AskUserQuestion` with the recommended action first and the real alternatives (coordination-rules, rule 7); delegated agents follow the same protocol. After the "write" answer: `touch .claude/.write-consent` (rule 7). ## Phase 1: Story and evidence Read the story, the feature-spec criteria, the latest `/code-review` report (chat history or `production/reviews/` if kept). ## Phase 2: Run Run the tests from the criteria matrix (and the whole affected package), lint/typecheck, `govulncheck`/`audit` when dependencies changed; for UI — axe on new pages (if e2e exists). Output in the report. Anything red → `NOT DONE`. ## Phase 3: DoD checklist Criteria ↔ tests ✅ — the criterion → test → result table **rendered in the chat message** (rule 7), not just written to the story file; review APPROVED; security rules for sensitive paths (appsec review happened?); docs (README/API/runbook) updated; contract and codegen in sync; the story branch is pushed with no uncommitted changes; CI green on the branch (`gh run list --branch <branch>` when `gh` exists). ## Phase 4: Close "May I set the story status → Done, tick `[x]` in the roadmap (add `🔗 [PR #N](url)` inline — same rule as the ID: file-relative link, not a `## Links` ref