# Start prompt: K3 Card purchases, web

You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/kvitt`), plan K3: card purchases, web. You have no context other than this prompt and the files it names.

Read PLAN-K3.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both (§15, §9.12, FR-22, §15.6 W-21 to W-23).

Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
- Next free decision id: {{NEXT_DECISION}}
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
- Schema version for any schema change: {{SCHEMA_VERSION}}
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.

Orchestrator notes for this run:
{{ORCHESTRATOR_NOTES}}

Essentials (the plan has the detail):
- First step: from the main checkout, `git worktree add .claude/worktrees/agent-k3 -b agent-k3 main`; work only there, on branch `agent-k3`; `git reset --hard main`; `npm ci` in `web/`. Stop and report if SPEC v0.36 is not on `main`. You may start before K1 and K2 land; rebase on both before the gate.
- Edit only the paths of PLAN-K3 §4 (`web/src/features/cards/**` new; the route, the sidebar entry and `web/src/lib/domain/`; the named edits in `features/expenses`, `features/accounts`, `features/settings`; the regenerated dictionaries); anything else is a request to the orchestrator.
- Gate: `npm run check` in `web/`. Report only results you ran in this session.
- Never use the owner's development stack or the Pi for checks; use a throwaway server with a stubbed Enable Banking (PLAN-K3 §6).
- Stop and ask when the plan says so, when a step could touch the owner's real data, or when the spec is ambiguous in a way that changes a decision.
- Commit on your branch when the gate is green, `git rebase main`, rerun the gate. Never merge, push or remove the worktree.

Report: end with the report described in PLAN-K3.md §10: branch, head commit hash, gate result lines, strings added, proposed spec text and decisions, how the orchestrator notes were applied, HUMAN steps outstanding (worded for relay), requests to the orchestrator, open questions with section numbers.