feat(lifeboard): draft a message, approve it, then send

[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: 16 of 19. Base: lifeboard/14-backup.

The design has said from the start that every outbound message names its recipient and waits for a confirmation. The type existed and nothing used it — sendMail and its approval had no screen. Now the assistant can propose a message and only a person can send it.

The envelope gains send, which is a proposal and never an action. It becomes a pending item in the Inbox showing the recipient and the whole body — not a preview, because approving something you have only seen half of is not approving it.

Every failure says what is missing. No permission to send email names the setting to change and leaves the draft unsent. No bridge for a text opens the phone's own composer with the message already written — not a failure, but the phone doing what it is best at.

Sending email is a separate, sensitive scope, off unless ticked, and the Google section says what it means rather than bundling it with reading.

Verified: lifeboard 399 (+10), including that a discard sends nothing and a missing permission leaves the draft pending.