feat(lifeboard): the offline foundation — fact log, boards, service worker

[ivanmkc]

The stack

#	PR	What it adds	Tests at this point
1	#311	A real localStorage for the test suite on Node 25	viewer 747
2	#312	@ivanmkc/termchart-canvas; injectable interact transport	canvas 473 · viewer 278
3	#313	lifeboard PWA: fact log, boards, service worker	lifeboard 36
4	#314	Shell, family profiles, tap layer	lifeboard 82
5	#315	The agent turn, four providers, Connections	lifeboard 142
6	#316	Packs, recipes, shopping-list arithmetic	lifeboard 231
7	#317	Provenance and lineage	lifeboard 257
8	#318	Calendar, Gmail, mail triage	lifeboard 301
9	#319	The bridge and long jobs	cli 314 · lifeboard 320
10	#310	Proactivity, scheduled boards, Google sign-in	cli 320 · lifeboard 343
11	#320	Persistence audit fixes: multi-tab, stale builds, no-storage boot	lifeboard 350
12	#321	User guide, bridge setup, QA guide, persistence audit	lifeboard 350
13	#322	A plan for third-party integrations (docs only)	unchanged
14	#323	A practice drill a board can define: audio + Q&A	canvas 485 · lifeboard 372
15	#325	Export and restore	lifeboard 389
16	#326	Draft a message, approve it, then send	lifeboard 399
17	#327	Hand long work to the Mac	lifeboard 406
18	#328	A Packs screen, and authoring one by describing it	lifeboard 418
19	#329	Activity — what changed, who changed it, undo	lifeboard 428
20	#330	Four defects found reviewing the stack	cli 323 · lifeboard 431

Every branch in the stack was checked out on its own and verified independently: npm install, tsc --noEmit for every package, npm test across the workspace, and the offline e2e where it exists. All twenty are green — no branch depends on a later one to build or pass. Full viewer e2e (11 suites, 106 assertions) was run on #312 as the behaviour-preservation evidence for the extraction.

---

Stack position: 3 of 10. Base: lifeboard/01-canvas.

The lifeboard PWA: a static bundle over a local log that renders on the canvas and works with the network switched off.

Two departures from the written plan, both deliberate.

The store is an append-only fact log, not a table of rows. The plan specified applyMutation(items, m) -> Item[]. The design doc requires provenance and undo (§8b, decisions 27–28) and neither can be recovered once a row has been overwritten in place. So the durable artefact is a log of assert / correct / retract entries and the list is a fold over it. Every entry records its author as human, code or model — a distinction that matters later, when deterministic steps may be re-derived automatically while model-authored facts must never be silently recomputed.

There is a service worker, which the plan did not call for. Its own acceptance criterion — "works with the network switched off" — cannot hold without one: Chromium will not serve the document from disk cache when offline, so an offline reload fails at the document request no matter what is in IndexedDB.

es2022 rather than the viewer's es2020, because the entry point uses top-level await.

Verified: e2e/offline.e2e.mjs runs the whole claim with the network off — first render, service worker takes control, offline reload, switch board, tick a box, reload, tick survived — with zero console errors. Unit tests: 40.

🤖 Generated with Claude Code