docs(agent): #117 is an input to #110, not work — Control Center is being retired

Bernardo's triage: the Control Center is going away (#110), so making its
toggles rebuild would be building on a condemned surface. #117 stays filed
because the observation outlives the tool — whatever menu inherits those rows
must not reprint "requires rebuild" — but it is marked not-standalone so no
agent picks it up as work. The previous entry's "next suggestion: #117" was
wrong and the correction is appended rather than rewritten.

#110's migration matrix gets what #116 turned up, which changes its shape:
its Bluetooth and Printing rows write settings.{bluetooth,printing}.enable,
and those keys only became live bridges in a9f3a64 — so those two toggles
never worked for any user. There is therefore no behavior to preserve, but
the keys and their bridges are real now and outlive the TUI: dropping the
rows must not drop the keys, or a machine whose theme-state.json already says
bluetooth.enable = false silently flips back on at its next rebuild.
checks.state-bridges covers exactly that and fails loudly if the bridges go
with the tool. Updates (settings.updates.enable) is read in
modules/home/options.nix — the HM side, where nomarchy.settings genuinely
exists — so it needs none of this; verified, not assumed.

V0: nix flake check --no-build passes. Backlog/journal only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

agent/JOURNAL.md

@@ -19,7 +19,23 @@ Template:
 
 ---
 
-## 2026-07-14 — #116: the state bridges that never were (this commit)
+## 2026-07-14 — triage: #117 is not work, it's an input to #110 (this commit)
+- **Task:** Bernardo's call on #117 (filed by the previous entry, which
+  suggested it as the next item — it is not; that suggestion is stale).
+- **Did:** Control Center is being retired (#110, NEXT, `[big]`), so fixing
+  its toggles builds on a condemned surface. #117 stays filed as a *record*
+  feeding #110's migration matrix, marked not-standalone. Gave #110 the facts
+  #116 turned up: its Bluetooth/Printing rows write state keys that only
+  became live in a9f3a64, so those two toggles never worked for anyone —
+  meaning there is no behavior to preserve, but the keys and their bridges are
+  real now and must not be dropped with the rows, or a machine whose state
+  says `bluetooth.enable = false` silently flips back on at the next rebuild.
+  `checks.state-bridges` will fail loudly if that happens.
+- **Verified:** V0 — `nix flake check --no-build`. Backlog/journal only.
+- **Next suggestion:** #110 (the retirement itself, needs splitting first) or
+  #115 suspend-then-hibernate — both `[human]`-gated on a design question.
+
+## 2026-07-14 — #116: the state bridges that never were (a9f3a64)
 - **Task:** BACKLOG #116 — NixOS options defaulting from
   `config.nomarchy.settings`, an attribute that exists only on the HM side.
 - **Did:** `nomarchy.settings` is declared in exactly ONE place