kvitt/docs/HANDOFF.md

Handoff: state of the work

Living document, rewritten in place (never a second copy). A new orchestrator session reads CLAUDE.md, then this.

1. Where things stand

• main at 90505a8 (M12e launcher icon) plus the SPEC v0.13 docs commit from agent-docs-v013 once it lands. History: 5e1be38 plans and prompts, c885aba M2c-dev, 76ee957 SPEC v0.3, fad6fc9 M2b, fdf2093 M2a, 040bf41 SPEC v0.4, 503cee5 M3, c28c52b M5, 982451d SPEC v0.5, bd6f10a M4, 23a2f1e SPEC v0.6, ab298ab M9, e8ee518 SPEC v0.7, 6b60ef7 M12a, 7fb9f6f SPEC v0.8, e499107 M12c, 2e2ebe7 M12b, d452fa6 UX Kalas categories and tokens, 16c4d01 UX sprint U2, 45eecd1 SPEC v0.9, bdba9d3 M12d, 3080804 M6, 7bd0aa1 SPEC v0.10, 72f21b2 app debug fakes bindings (temporary, deleted by M8), e6ad858 app release wiring of :data (pre-M8), b9b061a M7a, 6ac711d M7e, 082b8dc M7d, 31760f9 M7b, 1e42f76 M7c, a54eb7c M7f, 3a1bd14 M6b, d504004 SPEC v0.11, 34a2590 M7g, 369e516 and 00a14a3 M8, cf8ef45 SPEC v0.12, 1470a2f M12e contract pass, 90505a8 M12e launcher icon.
• Landed: M0 spec, M1 contracts and vectors (c6df2ab), M2a (fdf2093), M2b (fad6fc9), M2c-dev (c885aba), M3 (503cee5), M4 (bd6f10a), M5 (c28c52b), M9 (ab298ab), M12a (6b60ef7), M12b (2e2ebe7), M12c (e499107), U1 and U2 (16c4d01, owner approved), M12d (bdba9d3), M6 (3080804), M7a to M7f, M6b (3a1bd14), SPEC v0.11 (d504004, D-069 to D-080), M7g feature cleanups (34a2590), M8 app integration (369e516 + 00a14a3, landed 2026-10-18, gate green: BUILD SUCCESSFUL, 710 actionable tasks), SPEC v0.12 (cf8ef45, D-081 to D-085), M12e contract pass (1470a2f + 90505a8, landed 2026-10-18; gates green: Android BUILD SUCCESSFUL, 710 actionable tasks, 906 tests; cargo 253 tests, OpenAPI equality, vectors and migration byte-identity green).
• M8 outcome (recorded in SPEC v0.12 as D-081 to D-085): both variants bind :data through di/AppDataModule.kt, debug fakes module gone (D-081, revises D-041); debug network security config allows cleartext everywhere, the AC-2.8 limit is enforced in SessionRepositoryImpl.normaliseServerUrl, pinned-root config behind kvitt.tls.pinnedRoot (D-082); FCM registration by Firebase Installation ID, firebase-messaging 26.0.0, no server change (D-083); invite links ignored while paired (D-084); generic-notification, deletion and sync_batch taps open Home, push in an expedited WorkManager job (D-085). Not yet run: the end-to-end pairing, offline and push test on the phone and the design-spec §2.7 typeface check (phone was not attached; §3 item 1).
• M12e outcome (recorded in SPEC v0.13 as D-086 to D-095): E-3 invite_kind and Pairing, S-2 only after a partner pairing (D-086); admin name in E-12 links via ?from=, passed on by E-4, S-1 help line names the admin (D-087); SyncSummary.lastAttemptFailed (D-088); Rejection.actor (D-089); X-Kvitt-App-Version-Name, migration 0003, server schema 3, S-20 "Kvitt 1.1" (D-090); NewRecurringTemplate (D-091); UpdateCheck (D-092, revises D-073); SettleState.untouched (D-093, revises D-074); D-027 re-stamp in :data (D-094); PushEvent in :core:model, six screen-hosted snackbar hosts, snackbar resource ids, adaptive vector launcher icon (D-095, revises D-071). 128 px picture size left unchanged by assumption (owner question open, §3 item 5).
• Compatibility: the M12e APK cannot pair or list devices against a pre-M12e server (DTOs without defaults, by design), so the server is rebuilt and redeployed before the new APK is installed (SPEC §14.8). Old phones on the new server work.
• In flight: agent-docs-v013 (this docs change: SPEC v0.13).
• Both gates exist: Android tools/gradle-serial.sh check (from android/), server cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo test (from server/). Both green on main as far as reported.
• The UX sprint (owner's session in ~/orca/workspaces/kvitt/UX-sprint, branch UX-sprint) has landed; nothing is in flight there.
• Importer: the dry run of 2026-10-18 with M12b's mapping reconciled on both real files (Vardag 1746 rows, 0 unmapped; Hemma 37 rows, 0 unmapped). The CSV files stay in export/ (git-ignored).
• Development stack (M2c-dev): running on the Mac, reachable at http://192.168.1.210:8080; already rebuilt from main 90505a8 on 2026-10-18 (M12e server), database at schema 3, data kept, bootstrap code unchanged. Backups infra/dev/backups/kvitt-20261018T093143Z.sqlite.gz (before schema 2) and infra/dev/backups/kvitt-20261018T130443Z.sqlite.gz (before schema 3) exist (git-ignored). On this Podman setup infra/dev/up.sh alone does not swap in a rebuilt image: run infra/dev/up.sh --down, then infra/dev/up.sh. Its bootstrap pairing code is held by the orchestrator outside the repo and expires 2026-10-21T12:28Z. No scripted partner device exists yet (it needs the admin token, available only after the owner pairs). Firebase project kvitt-1337 with apps se.hagstedt.kvitt and se.hagstedt.kvitt.debug; service account kvitt-fcm; infra/secrets/fcm-service-account.json and infra/secrets/google-services.json in the main checkout (git-ignored).
• Installed on the owner's phone (SM-S942B): the debug app se.hagstedt.kvitt.debug built from c28c52b, as of the last report; the M8 and M12e builds are not installed yet (phone not attached); the dev server is already at M12e, so the M12e debug build can be installed.

2. Open work (one line each, with who owns it: agent or owner)

• Land agent-docs-v013 (orchestrator): SPEC v0.13, D-086 to D-095, HANDOFF, prompts/README.md.
• On-phone test (orchestrator with the owner, §3 item 1): install the debug build from main (M12e; the dev server already runs M12e), pair against the dev server, script a partner device with the admin token, run the offline and push checks; then the design-spec §2.7 typeface check (One UI font styles on the S26).
• Remaining contract requests (SPEC §11.3, no plan yet): S-22 licences screen (OQ-5, default not in v1); the server sends the FCM installation id in fid instead of token (D-083).
• Image build for the Pi (M2c-pi or M10): since M4 the arm64 server image needs a C toolchain in the build stage (aws-lc-rs) and CA roots in the distroless image (§10.3); confirm both and one FCM send from the shipped image.
• Later cleanup (any Android plan that owns android/gradle/**): remove the unused Vico entries from libs.versions.toml (D-063).
• Plans (SPEC §11.2 v0.13), in dependency order; prompt prompts/<id>.md:
  • M1, M2a, M2b, M2c-dev, M3, M4, M5, M6, M6b, M7a to M7g, M8, M9, M12a, M12b, M12c, M12d, M12e, U1, U2: landed.
  • Now: the on-phone test (§3 item 1).
  • Next: M2c-pi Infra on the Pi (blocked on OQ-3; owner: answer OQ-3, grant the Pi, Home Assistant Pi, Gitea and Drive allowances at the start, D-023); M10 First release after M2c-pi (owner: keystore per §10.6, D-024); M11 Import history after M9 and M10 (procedure §10.8 "Production run", D-025; each run must reconcile, D-045).

3. HUMAN steps pending (relay in chat)

1. M8 pairing, offline and push test on the phone (the owner does it with the orchestrator; dev server at http://192.168.1.210:8080; the orchestrator holds the bootstrap code, valid until 2026-10-21T12:28Z):
   1. Connect the phone to home Wi-Fi, plug it in over USB, open Kvitt (debug).
   2. On "Para ihop", open "Serveradress" and enter http://192.168.1.210:8080.
   3. Enter the code, enter "Ditt namn", tap "Para ihop".
   4. Land on "Väntar på din partner"; an agent pairs a scripted partner and creates an account. Yes/no: does Home show the account?
   5. If Android asks to allow notifications, tap Allow.
   6. Airplane mode on. Tap "Lägg till utgift", amount, description, "Spara". Yes/no: does the row show "Väntar på synk"?
   7. Airplane mode off, wait about 10 seconds. Yes/no: marker gone?
   8. Agent posts an expense as the partner. Yes/no: did a notification appear?
2. Look through the M6 component screenshots (android/core/design/src/test/screenshots/); approved in advance, nothing blocks on it.
3. Answer OQ-3 for M2c-pi (§4).
4. Release keystore per SPEC §10.6 for M10, or allow an agent to generate one.
5. Yes/no: the keyword "boende" maps to travel. Yes/no: is the 128 px picture size needed? Yes/no: is an open-source licences screen wanted in v1 (OQ-5, default no)?

4. Owner questions (asked, unanswered)

• OQ-3 LAN addresses and SSH users of the Kvitt Pi and the Home Assistant Pi; SSH port of the HA Pi; certificate directory there; which SSH add-on (SPEC §12). Needed by M2c-pi only.
• OQ-5 open-source licences screen on S-22 in v1 (SPEC §12; default not in v1).
• "boende" keyword → travel (yes/no); 128 px picture size needed (yes/no) (§3 item 5).

5. Paused (waiting on something outside the repo)

• M2c-pi: OQ-3.

6. Numbering

• Decisions: D-001 to D-095 used (D-008 and D-009 unused). Next free: D-096.
• Spec version: v0.13 written; next v0.14.
• Server schema version 3 (migration 0003, landed with M12e); next 4. Room schema version 1 (android/data/schemas/se.hagstedt.kvitt.data.db.KvittDatabase/1.json); next 2.
• Sync protocol 1, push payload 1.

7. How the work is run

See CLAUDE.md › Orchestration. HUMAN steps in reports are relayed in chat by the orchestrator; the owner does not read them in files.