SPEC v0.1 and project rules for Kvitt

Write SPEC.md v0.1 from the owner interview (requirements, data model,
stack, API outline, security, business rules, deployment, milestones,
UX sprint brief, contracts). Fill the CLAUDE.md blanks, move the Gradle
pin files into android/, point the tools at android/ and server/, and
record the git bootstrap exception in the handoff.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/HANDOFF.md

@@ -3,17 +3,27 @@
 Living document, rewritten in place (never a second copy). A new orchestrator session reads CLAUDE.md, then this.
 
 ## 1. Where things stand
-- `main` at <hash>, last gate: <date, result line>.
-- Installed on the owner's phone: <package> from <hash>.
+- `main` at `8bef22a` (root commit "Scaffold: agent starter kit (seeded from Ebb)"). No gate yet: neither `android/` nor `server/` has a project.
+- Branch `agent-spec` (on top of `main`, not landed): `SPEC.md` v0.1, filled `CLAUDE.md`, Gradle files moved to `android/`, tool scripts adjusted.
+- Installed on the owner's phone: nothing.
+- **Bootstrap exception (2026-10-17):** the repository had no commits, so the normal worktree flow could not start. The spec agent created the root commit directly in the main checkout (stray `.DS_Store` files deleted, `.DS_Store` added to `.gitignore`), then branched `agent-spec` there. From now on the normal flow of CLAUDE.md › Orchestration applies.
 
 ## 2. Open work (one line each, with who owns it: agent or owner)
+- Land `agent-spec` (orchestrator).
+- Plans agent: write `PLAN-*.md` and a start prompt per plan in `prompts/` from SPEC §11 (M1, M2a, M2b, M2c, M3, M4, M5, M6, M7a-M7f, M8, M9, M10, M11, U1, U2).
+- UX agent: U1 UX directions (SPEC §13), in parallel with M1. Owner reviews the directions before U2 and before any UI work.
+- Owner: answer SPEC §12 OQ-1 to OQ-4 (needed by M2c and M9).
 
 ## 3. Owner questions (asked, unanswered)
+- OQ-1 Local container registry address, HTTP or HTTPS, credentials (SPEC §12).
+- OQ-2 Splitwise CSV format confirmed against a real export, group list and target account names, non-SEK rows (SPEC §12).
+- OQ-3 LAN addresses and SSH users of the Kvitt Pi and the Home Assistant Pi; certificate directory on the HA Pi; which SSH add-on (SPEC §12).
+- OQ-4 Google Drive folder id for backups (SPEC §12).
 
 ## 4. Paused (waiting on something outside the repo)
 
 ## 5. Numbering
-Next free: D-001, SPEC v0.1, schema 1.
+Next free: D-001 (no decisions logged yet; the interview decisions are in SPEC v0.1 itself). SPEC v0.1 is written; the next spec version is v0.2. Schema version 1 is defined in SPEC §14.1 (not yet implemented); the next schema version is 2. Sync protocol 1, push payload 1.
 
 ## 6. How the work is run
 See CLAUDE.md › Orchestration. HUMAN steps in reports are relayed in chat by the orchestrator; the owner does not

docs/decisions.md

@@ -5,4 +5,3 @@ entry and the old one a strike-through plus a pointer. The spec is updated in th
 
 | # | Date | Decision | Why | Where it lives |
 |---|---|---|---|---|
-| D-001 | YYYY-MM-DD | … | … | SPEC §… |