docs(agent): park #94/#98/#99 with findings and in-flight state

Session wrap-up: progress notes so the next iteration resumes without
re-deriving — #94 installed-chromium path proven at V1 (live posture is
the gap, #103 covers it), #98 ruled out palette-level causes, #99
root-caused (live seed lacks git init) with the fix drafted but held on
the open live offline theme-switch failure; a serial-log VM run is in
flight. V0 (notes only); two deliberate working-tree drafts documented
in the entries.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

agent/BACKLOG.md

@@ -32,6 +32,16 @@ copy, and post-install desktop failures have different verification paths.
 
 ### 94. Live ISO/install: no default browser observed
 
+**Progress 2026-07-13:** installed path VERIFIED at V1 — the exact HM
+generation the ISO pins for offline installs contains the chromium binary,
+`chromium-browser.desktop`, and all three HTTP/HTML handlers
+(mime.nix sets them; template ships the package). The Acer sighting is the
+LIVE session, which ships NO browser by design (mime defaults name chromium,
+GIO skips it while absent) — #103 adds live baseline apps. Remains: a
+test-install VM run proving chromium launches post-install (chain #97's
+Bluetooth-click V2 into the same run), + make the live posture explicit in
+the flake comment (edit drafted, uncommitted).
+
 Chromium is the resolved default-browser decision and is present in the
 downstream template, but this hardware pass found no usable default browser.
 Trace the live-to-installed Home Manager path rather than merely checking the
@@ -52,8 +62,30 @@ installer surface where it was observed. Follow THEME-DESIGN's two-theme
 visual protocol. Pass = normal, hover, focused, and disabled button labels
 remain legible and palette-consistent.
 
+**Progress 2026-07-13:** scripted checks pass all 24 themes — not
+palette-level. Stylix gtk.css for Boreal audited: fg roles are light
+(#d3dae0); the near-black values are `accent/warning/error_fg_color`
+(#21272f) on their pastel bgs (deliberate, ~4.4:1). Candidate surfaces:
+adw-gtk3 (light base) + dark recolor edge cases, or gum's TUI confirm
+buttons in the installer (VM gum screens under Boreal look legible —
+artifacts in `/tmp/nomarchy-v2-swap-93/`). Needs Bernardo's screenshot or
+an Acer repro to pin the actual widget before fixing.
+
 ### 99. Doctor/Waybar reports `theme.json` is not git-tracked
 
+**Progress 2026-07-13:** root-caused — the message is doctor's
+"`theme-state.json` is NOT git-tracked": the live seed (hosts/live.nix
+`nomarchy-seed-flake`) does `cp -r` with no `git init`, so `~/.nomarchy`
+isn't a repo in the LIVE session (installed systems commit at
+nomarchy-install.sh:654 and are fine). Fix drafted in the working tree
+(seed does init+add+commit like the installer). Held for one open
+question: the same evidence run saw the live offline
+`nomarchy-theme-sync apply gruvbox` rebuild fail ("Build failed due to
+failed dependency") — determine whether that predates the git-seed (the
+git+file eval flips untracked-file visibility) before committing; a
+focused VM run capturing the full rebuild log over serial is in flight
+(`/tmp/nomarchy-v2-theme-99/`).
+
 The live-installed checkout shows a doctor/Waybar warning that `theme.json`
 is not tracked. Determine whether the warning targets the generated alias or
 the canonical `theme-state.json`, then align the check with the in-flake state