stage-buildlisted

# Build one story Input: the story, `tasks/<story>/plan.md`, `tasks/<story>/tests.md`, the product scope's `## Look and feel` and `## Qualities`, and — in a repeat round — the gate or judge report. Nothing else. Open the files the plan's and the tests' `## Files` name first; search the tree only for what they do not answer. Output: the production code, plus `tasks/<story>/build.md`. ## Do 1. Read the plan and the failing tests. Implement the **smallest** change that makes them pass — the smallest that also meets the product scope's `## Look and feel` and `## Qualities`, where the change has a surface. A page built to no stated look is correct only where the product scope states none. 2. Follow the plan's change list. An element the plan did not name is a sign the plan was wrong: note it in the build file rather than quietly extending the design. 3. Keep the architecture intact — the same rules the plan worked under: no framework types in the domain, ports declared inward and implemented in adapters, no raw cross-context imports, one aggregate per transaction, domain events published and cleared where the plan says so. 4. Use the project's own building blocks and conventions: its markers, its base types, its package layout, its error handling. Where the project ships an architecture rule suite, run it and take it as binding. 5. Run what the stack profile declares — compile, unit tests, end-user tests, the architecture suite, the formatter. Do not