docs(adr): nine, in all three places — finish the hex-count correction

The previous commit corrected clause 4's count from six to nine and left the
migration step and the Consequences section saying six, so the ADR contradicted
itself twice. Found by the third Codex review, and it is the same class as the
stale count that review round caught in context/code/tui.md: when a number is
stated in more than one place, changing it is a grep, not an edit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FC2jVn8Au7E9JPkw6bwXXH

context/adr/004-faces-and-themes.md

@@ -292,7 +292,7 @@ The order that foreclosed nothing, cheapest first:
 3. `PanelContent::active_color()` and `field_kind_fg` are lifted into faces — they are
    already the right shape and only lack a home.
 4. `MinibufColor` is retired in favour of a face per text-entry mode (see below).
-5. The browser's 16-slot table replaces `style.css`'s six stray hex values, and the
+5. The browser's 16-slot table replaces `style.css`'s nine stray hex values, and the
    `--` tokens become that theme's surface faces.
 6. Everything else, as files are touched.
 
@@ -478,7 +478,7 @@ is known, which is the wrong order.
 
 **Good.** The browser and the TUI stop diverging, which is a fork that would otherwise widen
 every release. improvise-pcje becomes a matter of resolving faces the browser already has
-names for. `MinibufColor`'s doc comment becomes true. The six stray hex values in
+names for. `MinibufColor`'s doc comment becomes true. The nine stray hex values in
 `style.css` rejoin the token system. `context/code/tui.md`'s "the one that is wrong" section
 gets to be deleted rather than maintained. And a Swift or Qt front end starts from a
 vocabulary rather than from reading 125 literals.