## Description
[Clear description of what needs to be done]

## Context
[Any relevant background, source file, or screenshot reference]

**Source spec:** [GitHub URL of the spec in the project's repository, plus the relevant section. Not a local path.]

## Bug Details
_Bugs only; omit for other issues._

- **Steps to reproduce:** [Numbered steps from a known starting state]
- **Expected:** [What should happen]
- **Actual:** [What happens instead, with any error message or screenshot reference]

## Acceptance Criteria and Verification
_Each criterion with how to check it and what counts as passing. Carry forward the source spec's relevant verification requirements, including any specific existing behavior this change could break. These are planned checks, not completed results._

- [ ] [Specific, measurable criterion] — **Verify:** [Test, walkthrough, measurement, or review, with relevant inputs and environment] → [Observable evidence or threshold required to pass]
- [ ] [Specific existing behavior this change could break, if any] — **Verify:** [Regression check] → [Still behaves as before]

**End-to-end check:** [The user journey this issue completes, exercised through the real user path rather than internal shortcuts or test-only endpoints; how an agent drives it (browser, terminal, HTTP calls); and the side effects to confirm, such as saved records, files written, or messages sent]

## What Agents Should Ask You
_Carry forward from the source spec when it has this section; omit otherwise._

- **Check with me first:** [e.g., new paid services, changes to existing data, anything public-facing]

## Dependencies
[When splitting a spec into multiple issues, record prerequisites and ordering. Omit if none apply.]

- **Blocked by:** [Issue link + what it must deliver first. Blockers are created first, so link the real issue; in the preview, use its draft title.]

## Notes
[Any additional context, constraints, or suggestions]