docs: record rollout acceptance on all machines (2x ubuntu, macOS, TUI render)

TODO.md

@@ -2,19 +2,13 @@
 
 ## Now
 
-- [ ] **Visual TUI verification** — user restarts MiniMax Code; confirm the
-  `custom-command` segment renders with Aygea colors, emoji, and no width misalignment.
-  Acceptance: screenshot or user confirmation; move rendering from `inferred` to
-  `confirmed` in `docs/FEATURE-MATRIX.md`.
-- [ ] **Ubuntu rollout ×2** — run the curl one-liner on both Ubuntu boxes; each needs the
-  `zai_api_key` SecretVault secret (or credential.json). Acceptance: `printf '{}' | mcode-zai-usage`
-  prints a segment on both; entry recorded in FEATURE-MATRIX.
+- [x] **Visual TUI verification** — confirmed by user acceptance 2026-10-19
+  ("installed and works perfectly" across machines). See FEATURE-MATRIX.
+- [x] **Ubuntu rollout ×2** — done (user-reported 2026-10-19).
+- [x] **macOS rollout** — done (user-reported 2026-10-19).
 
 ## Next
 
-- [ ] **macOS rollout** — same one-liner on the Mac. Script is written portable
-  (`date -r` fallback, no-`flock`/no-`setsid` degrade, `vm_stat` memory) but has never
-  run on macOS: treat as `unknown` until tested. Acceptance: install + segment on macOS.
 - [ ] **mcode-update resilience check** — after the next mcode release, re-grep the new
   bundle for `customStatusLine`/`statusLineItems` handling and re-check the clamps
   documented in `docs/DECISIONS.md` D2; update digests there.
@@ -22,6 +16,6 @@
 ## Deferred
 
 - Optional `AYGEA_SL_MEM` memory-segment polish on macOS (page-size assumptions in
-  `vm_stat` parsing are untested there).
+  `vm_stat` parsing are untested there — segment is opt-in and off by default).
 - Consider a `--json` inspection mode for debugging cache state. Rejected for now:
   scope creep against "little self-contained tool".