feat(lifeboard): calendar, Gmail and first-class mail triage

[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

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 nineteen 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: 8 of 10. Base: lifeboard/06-provenance.

The connective tissue: the family calendar, mail read and sent, and triage as a first-class subsystem.

This resolves audit finding B1 by moving triage into the client. Gmail is signed in from the browser with PKCE and the token lives on the device that signed in, so a nightly pass on the bridge could not authenticate. Triage runs here and catches up on what it missed; the bridge may ask for a pass while a client is open but never holds the credentials. Handing a long-lived refresh token to a separate local process was rejected: it is the difference between "this app can read my mail while I am looking at it" and "this machine can read my mail forever". The cost — an iPad closed for a week triages nothing until it opens — is written into the audit rather than hidden.

Reconciliation gets the care the roadmap asked for. A rescheduled appointment updates the event already on the calendar; a second dentist appointment is the one that gets missed. Matching is deliberately conservative: the provider's id first, then the same title on the same local day, then the same title within a fortnight. A cancellation is always proposed and never applied, whatever the sender's trust rung, because being wrong there means someone does not turn up — and it marks the event cancelled rather than deleting it, so nobody wonders where it went.

The trust ladder defaults to the middle rung. Nothing is applied on its own until you have accepted three things from that sender, and even then it appears in the inbox with an undo. The promotion is offered, never taken.

Structured data is parsed by code and prose by the model, and which one ran is recorded. An ICS attachment needs no confidence score and never varies; a model-derived fact is marked as such so a human correction always wins.

Sending mail cannot happen without an approval that names the exact draft, so forgetting the confirmation is a type error rather than a missing check.

Weeks are stepped by calendar day, not by adding 24 hours — on the days the clocks change a day is 23 or 25 hours long, and the arithmetic version silently loses a Sunday. Recurring events are expanded by Google rather than interpreted here.

Verified: 301 unit tests, covering a week that spans the DST boundary, reschedule-not-duplicate, cancellation-always-proposed, and send-refuses-unapproved.

🤖 Generated with Claude Code