## Summary ## Story / task - Story / task: `EP--S0N-T0N` - Spec: `specs/EP--S0N/` (link.md points back to the product repo) ## Impact & Risk - **Domains / repos touched:** - **Contract surface touched:** no - **Risk level:** low - **Rollback plan:** > **Routing:** the merge needs **1 approval, which should not be the author’s own**. `high` risk adds 1 > and a touched contract surface adds 2 to the count (the larger, never the sum); that step is advisory > (`yad open-pr` shows it capped by the active people). A change to a directory the base branch's `.sdlc/risk-map` marks `high` adds 1 > too, even when this says `low`. Run `bash checks/risk-route.sh ` on this branch to > print the count. ## Testing ## Checklist - [ ] Commits carry a `Task: -` trailer (spec-link gate) - [ ] No contract-surface change without `Contract-Change: yes` + a re-locked contract (contract-check gate) - [ ] Lint, build, and tests pass (build/test/lint gate) - [ ] Diff stays inside the files the task's spec declared (≤3 where possible) - [ ] Impact & Risk filled; for `high` risk, ask reviewers who know the touched domains