Task Template

Task Template

Historical template. New work must be a detailed GitHub Issue with phase/status labels, blockers, acceptance criteria, live verification, required evidence, and Closes #<issue> PR linkage.

Every task card on the phase pages follows this shape. Copy it when adding cards.

### [PHASE-N-XX] Short title

**Status:** unclaimed | claimed (@who) | in-review | done
**Depends on:** [PHASE-N-YY] (or none)

**Scope**
One paragraph: what this delivers and where it stops. Name the anara element it
maps to if relevant.

**Files**
- core/... / src/... / electron/... — what to add or touch

**Acceptance criteria**
- [ ] Concrete, checkable statement
- [ ] Tests: which behaviours are covered (vitest)
- [ ] Typecheck + build pass
- [ ] Live verification: exact Electron clicks/typing and expected visible result
- [ ] Console/error-state/restart checks where relevant
- [ ] Real-paper or signed-in ACP check where relevant
- [ ] Caveman prose in any docs; code/PR normal

**Notes**
Gotchas, links to skills/docs, design hints.

Rules for agents

• Build test-first (tdd skill). No card is "done" without tests and applicable live user-flow evidence.
• Delegated implementation must include focused test evidence. Parent agent reviews diff, integrates work, runs full checks, and performs live verification.
• One current GitHub issue = one focused PR against master. Use Closes #<issue> in PR body.
• Respect Architecture guardrails. If a card seems to require breaking one (Python, raw API key, custom RAG, OAuth bridge), stop and flag — don't.
• Don't pull later-phase work forward. Stubs stay stubs until their card.
• Existing merged code may still be broken. Reproduce behavior; do not infer working status from merged PRs, component presence, or mocked tests.