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

CURRENT_STATE.md

@@ -23,19 +23,19 @@ installable on 1 macOS + 2 Ubuntu systems with one `curl | bash` line.
   exit 0; `colorMode: ansi` passes ANSI through; intervalSeconds ≥10, timeoutMs 500–30000.
   Evidence: bundle reads in `docs/DECISIONS.md` (release digests recorded).
 - `confirmed` — Pushed to `git@git.itsaygea.com:admin/mcode-sl.git` (port 2222 SSH).
+- `confirmed` (user acceptance) — Rendered segment works in the live TUI, and the
+  installer succeeded on all target machines: 2× Ubuntu + 1× macOS (2026-10-19,
+  "installed and works perfectly"). Human acceptance, distinct from agent-run checks.
 
 ## Active work
 
-None in flight. Last stage (initial install + push) completed 2026-10-19.
+None. Initial release shipped and deployed to all target machines (2026-10-19).
 
 ## Blockers
 
-- Visual confirmation of the rendered segment in the live TUI requires the user to
-  restart MiniMax Code. Until then, ANSI/emoji rendering in the statusline is
-  `inferred` (config accepted by the parser; passthrough path verified in code, not on screen).
+None.
 
 ## Exact next action
 
-User restarts the MiniMax Code TUI and confirms the segment renders (colors, emoji, no
-misalignment). Then roll out to the two Ubuntu machines + macOS via the curl one-liner
-and record results in `TODO.md` / `docs/FEATURE-MATRIX.md`.
+Nothing pending. Only standing task: re-verify the bundle facts (`docs/DECISIONS.md` D2)
+after the next mcode release — see `TODO.md`.