karvey-impllisted

# Karvey Impl ## Purpose Execute the implementation tasks in DB→Backend→Frontend order. Per-task cycle: read → execute → test → validate. Update ClickUp or PLAN.md in real time. ## Execution steps ### Step 1 — Load context Read: - `docs/spec/changes/{change-id}/spec.json` - `docs/spec/changes/{change-id}/tasks.md` - `docs/spec/changes/{change-id}/architecture.md` - `docs/spec/changes/{change-id}/requirements.md` Verify `approvals.tasks.approved = true`. If not, stop. If a specific task is given (`F{n}.T{n}`): execute only that one. If `--from F{n}.T{n}` is given: start from that task and continue sequentially. If nothing is specified: start from the first pending task. ### Step 2 — Select the task to execute Identify the next pending task while respecting dependencies: - Do not execute [Backend] until its dependent [DB] is completed - Do not execute [Frontend] until its dependent [Backend] is completed - Tasks marked `(P)` can be executed in parallel with subagents ### Step 3 — Start the task in management **If ClickUp:** ``` clickup_update_task(task_id, status="in progress") clickup_start_time_tracking(task_id) ``` **If Markdown:** Edit `PLAN.md`, change `⬜ pending` → `🔄 in progress` for the task. ### Step 4 — Execute the task Read the full task description and its acceptance criteria. Do the technical work: create/modify files per the File Structure Plan. **Execution rules:** - Respect the task's boundary — do not touch code outside its scope - Follow the ex