Name design 59's milestone issues, confirmed by the operator

03-DESIGN/01-to-be/59-the-mail-web-client.md

@@ -136,7 +136,12 @@ test 5 is `mesh-mail`'s own; test 6 is read before the module is assigned; test
 | 1 | In a browser on the laptop and the workstation, the operator signs in and browses, searches and reads every account's mail with its attachments, and writes a mail that goes out on their Approve | tests 1 to 7 | mesh-catalog: `mesh-mail`'s account bucket (issue 1255, ADR 0439 §2); the module `mesh-mail-web` (manifest, sign-in, the pages, the send, the seat's verbs, the integration test) | — |
 | 2 | Betterbird is gone from the laptop and the workstation, its profile and mail kept in the home | ADR 0379 §2 | mesh-catalog: Betterbird unassigned on the operator's Approve, then the `betterbird` module removed from the catalogue (issue 806) | 1 |
 
+**Confirmed by the operator on 2026-10-19.** Milestone 1's issues, one repository part each, in their order:
+1255 (`mesh-mail`'s account bucket), 1261 (`mail_send_status` answers only its caller), 1262 (the module), 1263
+(sign-in), 1264 (accounts, folders and mails), 1265 (search), 1266 (a mail and its attachments), 1267 (writing a
+mail), 1268 (the integration test). Milestone 2 is issue 806. The status stays `designed` until milestone 1 starts:
+one design is built at a time (playbook 07), and milestone 1 waits for the design whose release is in `fixing`.
+
 After milestone 1's delivery and before its live proof, four values are set, each on the operator's Approve:
 `mesh-mail-web`'s `reach` on its machine (`internal`), then its assignment there, its `operators`, and its caller in
-`mesh-mail`'s `grants` for every account. Milestone 1's prepare step (playbook 07 step 0) opens its issues and writes
-their numbers here.
+`mesh-mail`'s `grants` for every account.