SPEC v0.8: UX-session decisions (D-047 to D-054), category contract v2, M12 plans
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
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
# Start prompt: M12a Category contract v2, contracts
|
||||
|
||||
You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/kvitt`), milestone M12a: Category contract v2, contracts. You have no context other than this prompt and the files it names.
|
||||
|
||||
Read PLAN-M12a.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, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Say whether `docs/ux/category-keywords.csv` is on `main` or must be read from the branch `UX-sprint`; agent-m12a may already have run from the UX-session documents, in which case this prompt is for a re-run against SPEC v0.8.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
- First step: from the main checkout, `git worktree add .claude/worktrees/agent-m12a -b agent-m12a main`; work only there, on branch `agent-m12a`; then copy the git-ignored files the plan names.
|
||||
- Edit only `contracts/**` (the files named in the plan) and `tools/contracts-check.py`; anything else is a contract request to the orchestrator.
|
||||
- Gate: `python3 tools/contracts-check.py` from the repository root. 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-M12a.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.
|
||||
@@ -0,0 +1,24 @@
|
||||
# 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, write `TODO(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 branch `agent-m12b`; then copy the git-ignored files the plan names.
|
||||
- Edit only the server paths of PLAN-M12b §4 (the OpenAPI `DefaultCategoryKey` and 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 test` in `server/`. 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.
|
||||
@@ -0,0 +1,24 @@
|
||||
# Start prompt: M12c Category contract v2, Android
|
||||
|
||||
You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/kvitt`), milestone M12c: Category contract v2, Android. You have no context other than this prompt and the files it names.
|
||||
|
||||
Read PLAN-M12c.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, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Confirm M12a has landed. No phone is needed.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
- First step: from the main checkout, `git worktree add .claude/worktrees/agent-m12c -b agent-m12c main`; work only there, on branch `agent-m12c`; then copy the git-ignored files the plan names.
|
||||
- Edit only the Android paths of PLAN-M12c §4 (`:core:model`, `:data`, `:core:fakes`, and existing default-name string files if any; `:domain`'s suggestion landed with M12a); anything else is a contract request to the orchestrator.
|
||||
- Gate: `PATH=/opt/homebrew/opt/openjdk@25/bin:$PATH ../tools/gradle-serial.sh check` in `android/`. 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-M12c.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.
|
||||
+8
-4
@@ -2,7 +2,7 @@
|
||||
|
||||
One ready-to-paste start prompt per plan (`PLAN-<id>.md` at the repository root), plus `ORCHESTRATOR-prompt.md`. Before pasting, the orchestrator fills `{{NEXT_DECISION}}`, `{{SPEC_VERSION}}`, `{{SCHEMA_VERSION}}` (disjoint ranges for agents that run in parallel, CLAUDE.md › Numbering) and `{{ORCHESTRATOR_NOTES}}` (answers to the plan's open points, phone assignment, overrides). `U2.md` also takes `{{OWNER_PICK_AND_COMMENTS}}`. U1 and U2 run in the owner's own Claude session in `~/orca/workspaces/kvitt/UX-sprint` on branch `UX-sprint`. The numbers are for proposed entries in agents' reports: implementation agents never edit `SPEC.md` or `docs/decisions.md`; a docs agent records what the orchestrator accepts (CLAUDE.md › Orchestration).
|
||||
|
||||
Dependencies follow SPEC §11.1 and §11.2 (v0.7). Status as of 2026-10-18: M0 done, M1 landed (`c6df2ab`), M2c-dev landed (`c885aba`), M2a landed (`fdf2093`), M2b landed (`fad6fc9`), M3 landed (`503cee5`), M5 landed (`c28c52b`), M4 landed (`bd6f10a`), M9 landed (`ab298ab`); U1 committed on `UX-sprint` (owner's direction pick pending). The plans' open points are resolved in SPEC v0.3 and recorded in each plan's §4; v0.4 records the M2a and M2b decisions (D-005 to D-014); v0.5 the M3 and M5 decisions (D-026 to D-034, D-040 to D-043); v0.6 the M4 decisions (D-035 to D-039); v0.7 the M9 decisions (D-044 to D-046).
|
||||
Dependencies follow SPEC §11.1 and §11.2 (v0.8). Status as of 2026-10-18: M0 done, M1 landed (`c6df2ab`), M2c-dev landed (`c885aba`), M2a landed (`fdf2093`), M2b landed (`fad6fc9`), M3 landed (`503cee5`), M5 landed (`c28c52b`), M4 landed (`bd6f10a`), M9 landed (`ab298ab`); SPEC v0.7 landed (`e8ee518`); M12a landed (`6b60ef7`); U1 done on `UX-sprint`, direction 3 "Kalas" muted picked (D-047), U2 in progress there. The plans' open points are resolved in SPEC v0.3 and recorded in each plan's §4; v0.4 records the M2a and M2b decisions (D-005 to D-014); v0.5 the M3 and M5 decisions (D-026 to D-034, D-040 to D-043); v0.6 the M4 decisions (D-035 to D-039); v0.7 the M9 decisions (D-044 to D-046); v0.8 the owner's UX-session decisions (D-047 to D-054) and the milestone group M12.
|
||||
|
||||
## Dependency order and waves
|
||||
|
||||
@@ -19,10 +19,13 @@ Plans in the same wave can run in parallel (they own disjoint paths, SPEC §14.7
|
||||
| 2 | M3 Server core API | `M3.md` | M2a | done (`503cee5`) |
|
||||
| 2 | M4 Server sync, audit, push, scheduler | `M4.md` | M2a; lands after M3 (D-015) | done (`bd6f10a`) |
|
||||
| 2 | M5 Android data layer | `M5.md` | M1, M2b | done (`c28c52b`) |
|
||||
| 2 | M6 Design system | `M6.md` | U2 approved, M2b, the §9.7 colour spec change | M3, M4, M5 |
|
||||
| 2 | M12a Category contract v2: contracts | `M12a.md` | M1, SPEC v0.8 | done (`6b60ef7`) |
|
||||
| 2 | M12b Category contract v2: server | `M12b.md` | M12a (M3, M4, M9 landed) | M12c, U2 |
|
||||
| 2 | M12c Category contract v2: Android | `M12c.md` | M12a (M2b, M5 landed) | M12b, U2 |
|
||||
| 2 | M6 Design system | `M6.md` | U2 approved, M2b, M12c, the §9.7 colour spec change | M12b |
|
||||
| 3 | M7a Feature onboarding | `M7a.md` | M6 | M7b to M7f, M9 |
|
||||
| 3 | M7b Feature home and account | `M7b.md` | M6 | M7a, M7c to M7f, M9 |
|
||||
| 3 | M7c Feature expense | `M7c.md` | M6 | M7a, M7b, M7d to M7f, M9 |
|
||||
| 3 | M7c Feature expense | `M7c.md` | M6, M12c | M7a, M7b, M7d to M7f, M9 |
|
||||
| 3 | M7d Feature settle | `M7d.md` | M6 | M7a to M7c, M7e, M7f, M9 |
|
||||
| 3 | M7e Feature analytics | `M7e.md` | M6 | M7a to M7d, M7f, M9 |
|
||||
| 3 | M7f Feature settings | `M7f.md` | M6 | M7a to M7e, M9 |
|
||||
@@ -37,6 +40,7 @@ Plans in the same wave can run in parallel (they own disjoint paths, SPEC §14.7
|
||||
- **M3 and M4** (D-015): M2a provides `next_occurrence_date`, the `AuditWriter`/`PushQueue` traits with no-op implementations and `tasks::start`; M3 writes the recurring generation function and calls the traits; M4 replaces the implementations, its scheduler calls M3's function, and M4 lands after M3.
|
||||
- **M2a and M2b** create shell files and modules in later milestones' paths (D-004); ownership passes on when they land.
|
||||
- **M7a to M7f** follow the feature convention of SPEC §6.2 (D-017) and take the ledger rows and expense editor fields from M6's `:core:design` (D-019).
|
||||
- **M6** starts only after the §9.7 colour change from U2's proposal has landed in SPEC (§11.1).
|
||||
- **M6** starts only after the §9.7 colour change from U2's proposal (the muted Kalas values, `slate` and `amber` included, D-051) has landed in SPEC and M12c has landed (§11.1).
|
||||
- **M12** (D-054): SPEC v0.8 changes the §10.8 table that the importer test `category_table_matches_the_spec` parses, so the server gate on `main` is red from SPEC v0.8 until M12b lands; land M12b soon after (or land SPEC v0.8 together with it).
|
||||
- **Phone:** M2b (one `installDebug`), M5 (only if instrumented tests), M8 and M10 use the phone; only one at a time, named in the notes.
|
||||
- **Outside the repository:** M2c-dev (D-022, done), M2c-pi (the Kvitt Pi, the Home Assistant Pi, Gitea, Drive: allowances requested at the start of that sprint, D-023), M8 (dev server on the Mac), M10 and M11 (production) need the owner's allowance in the notes.
|
||||
|
||||
Reference in New Issue
Block a user