implement-issuelisted

# Implement Issue Perform the SDD phase `Implement` for exactly one prepared issue. ## Workflow 1. Resolve the current repository and exact issue. 2. Read the issue body, all comments, linked issues/PRs, applicable repository instructions, current code, tests, documentation, and relevant Git history. 3. Confirm the issue contains implementation-safe `Specify`, `Clarify`, `Plan`, and proportional `Tasks`. Do not silently invent a missing product decision. 4. When preparation is insufficient, identify the exact missing phase/decision, recommend or delegate to `capture-issue` or `plan-issue`, and do not continue into speculative implementation. 5. Check Git status, current branch, base branch, remotes, repository policy, existing issue branches, and existing PRs. 6. Route specialized work only when applicable: `debug`, `domain-model`, `module-design`, `research`, `prototype`, `dont-reinvent-the-wheel`, `resolve-conflicts`. Keep issue ownership and scope inside `implement-issue`. 7. Implement the smallest coherent solution satisfying the issue. Preserve behavior outside scope. 8. Update focused tests and canonical documentation with the change. 9. Run the narrowest relevant validation first, expanding validation according to risk and repository guidance. 10. Update completed Tasks only after evidence exists. Refetch the issue before editing its body or comments. 11. Inspect the final diff to ensure no unrelated changes, temporary artifacts, secrets, generated logs, or accident