story-developmentlisted

# Story Development Treat the approved Story as the intent boundary and repository verification as the completion authority. ## Develop the Story 1. Locate `specs/stories/<story-id>/story.md` and `acceptance.md`. Read any optional `task.md` as progress context only. If the Story is missing, ambiguous, or conflicts with another requirement, identify the exact blocker before changing code. 2. Extract the Goal, in-scope behavior, out-of-scope boundary, inputs, outputs, business rules, expected errors, constraints, and every acceptance item. The implementation contract is complete when each acceptance item maps to an observable behavior or verification check. When the Story is security sensitive, treat every row of its security fixture matrix as a required case with an exact payload and expected persisted output; when it declares superseded behavior, change the named tests deliberately instead of treating the conflict as a defect. 3. Read the repository agent guide and inspect the relevant architecture, code, tests, dependencies, and documented commands. Project tooling is the source of truth for technology-specific mechanics. 4. Form a dependency-ordered implementation plan for the smallest coherent end-to-end change. Keep requirement decisions with the human; ask only when a missing decision materially changes behavior or risk. 5. Implement within the Story boundary. Add or update tests at the lowest useful boundary for changed be