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` - `docs/spec/changes/{change-id}/deviations.md` (if it exists — deviations already approved at design time) - **Engineering standards** for the layers being implemented: resolve `project.json:standards` (or `docs/spec/standards/_index.md`) and read the relevant `standards/{layer}.md` (see `karvey/rules/engineering-standards.md`). These are a **hard constraint** on the code you write. 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_s