jacobh2
d39eb2c79b
Records the owner's UX-sprint decisions UX-1 to UX-8 of docs/ux/proposed-decisions.md: D-047 direction Kalas muted, D-048 three tabs, D-049 category suggestion (§9.11, suggestCategory, contracts/category-keywords.csv, suggest_category.json), D-050 S-1 display-name field, D-051 colour token values from Kalas (slate, amber TODO(U2)), D-052 smaller UX rules, D-053 finer Splitwise mapping, D-054 fourteen default categories with server schema 2 (migration 0002, §14.1.1). Adds milestone group M12 (PLAN-M12a/b/c, prompts), the CLAUDE.md UX-sprint note, and rewrites HANDOFF. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQd3pEP9UeN2uifbHknQ7B
2.2 KiB
Start prompt: M12b Category contract v2, server
You are an Opus implementation agent on Kvitt (repository /Users/jhag/projects/kvitt), milestone M12b: Category contract v2, server. You have no context other than this prompt and the files it names.
Read PLAN-M12b.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
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, writeTODO(spec)wherever the number would go and say so in the report.
Orchestrator notes for this run: (To fill: Confirm M12a has landed; say whether the agent may restart the development stack on the Mac to upgrade its database (default: no, report the steps).) {{ORCHESTRATOR_NOTES}}
Essentials (the plan has the detail):
- First step: from the main checkout,
git worktree add .claude/worktrees/agent-m12b -b agent-m12b main; work only there, on branchagent-m12b; then copy the git-ignored files the plan names. - Edit only the server paths of PLAN-M12b §4 (the OpenAPI
DefaultCategoryKeyand the category examples M12a held back, migration 0002,SCHEMA_VERSION, token lists, the key enum, the importer table and key list, their tests); anything else is a contract request to the orchestrator. - Gate:
cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo testinserver/. Report only results you ran in this session. - 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-M12b.md §10: branch, head commit hash, gate result lines, versions chosen with sources, numbering used, how the orchestrator notes were applied, HUMAN steps outstanding (worded for relay), contract requests, open questions and spec gaps with section numbers.