jacobh2
d9dd5848fe
- D-035 unusable mutation_id/entity_type/entity.id fails the whole push with 400; other shape errors per mutation.
- D-036 0 mutations is batch_too_large ("outside 1 to 100").
- D-037 never-synced delete runs full step-8 validation; current on every rejection; created_at kept; canonical ids.
- D-038 FCM retries: one send plus three retries (1/5/25 s), 401 drops the token, other 4xx not retried.
- D-039 pruning strictly older than 90 days; tasks::start returns AppState with the push queue, SqlAuditWriter default.
- Clarifications: step 8 order, negative since, pull read transaction, FCM JWT kid and cache, token clearing only if
unchanged, unusable credentials, scheduler clock jumps, rotate-epoch exit codes, /i/ empty code, image build needs
a C toolchain and CA roots (dev image rebuilt 2026-10-18).
- PLAN-M4 pruning wording, prompts/README status, HANDOFF at bd6f10a.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQd3pEP9UeN2uifbHknQ7B
4.3 KiB
Start prompts
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.6). 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 in flight; 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).
Dependency order and waves
Plans in the same wave can run in parallel (they own disjoint paths, SPEC §14.7). Android agents share one Gradle build at a time (tools/gradle-serial.sh) and one agent on the phone at a time.
| Wave | Plan | Prompt | Depends on | Parallel with |
|---|---|---|---|---|
| 0 | M1 Contracts and vectors | M1.md |
M0 | done (c6df2ab) |
| 0 | U1 UX directions | U1.md |
M0 | everything in waves 0 to 2 (owner's session) |
| 1 | M2a Server skeleton and kvitt-domain |
M2a.md |
M1 | done (fdf2093) |
| 1 | M2b Android skeleton and :domain |
M2b.md |
M1 | done (fad6fc9); installDebug on the phone outstanding |
| 1 | M2c-dev Infra for development | M2c-dev.md |
M0 (its health check needs M2a's image) | done (c885aba) |
| 1 | U2 UX design spec | U2.md |
U1 and the owner's pick | M2a, M2b, M2c-dev, wave 2 |
| 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 |
| 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 | 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 |
| 3 | M9 Splitwise importer | M9.md |
M2a, M4 | M5, M6, M7a to M7f |
| 4 | M8 App integration | M8.md |
M3, M4, M5, M7a to M7f, M2c-dev | M9 if still running |
| 5 | M2c-pi Infra on the Pi | M2c-pi.md |
M2c-dev, M8; OQ-3 answered | none needed |
| 6 | M10 First release | M10.md |
M2c-pi, M3, M4, M8 | none |
| 7 | M11 Import history | M11.md |
M9, M10 | none |
Constraints the orchestrator must keep in mind
- M3 and M4 (D-015): M2a provides
next_occurrence_date, theAuditWriter/PushQueuetraits with no-op implementations andtasks::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).
- 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.