Design 59: milestones 2 to 4 confirmed with their issues, and the mail modules' as-is design

+203 -14

4 Commits

Author	SHA1	Message	Date
jochen	d2dccddc27	Say the notifier's bundle is its own process under its own account, as main.go says mesh/merge-gate head d2dccddc2726 merged into trunk 0738fa1405dd — pass: the change touches no module of the mesh's graph Details mesh/repo-check head d2dccddc2726 merged into trunk 0738fa1405dd — pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-20 19:12:04 +02:00
jochen	dcc6f185d4	Answer the review: the mail modules are separate modules, the notifier has no process, nothing future in the as-is; 1433 depends on none	2026-10-20 19:11:06 +02:00
jochen	e925a843ce	Write the mail modules' as-is design, so what design 59's milestone 2 replaces is recorded before it is built Playbook 04 step 3: the one grants list that gives reading and sending at once, and mesh-mail-notifier's pop-up for every new mail, read from mesh-catalog main a67f0196 and the live mesh.	2026-10-20 19:08:13 +02:00
jochen	66bb013b85	Write milestones 2 to 4's issues into design 59, as the operator confirmed them Playbook 04 step 6. Also names ADR 0378 §5 beside ADR 0440 §4 for the page's use of mail-reading, its writes with correct and undo, and issue 1419 in §8's last sentence, as the graduation's review noted.	2026-10-20 19:02:56 +02:00

Design 59: milestones 2 to 4 confirmed with their issues, and the mail modules' as-is design #443