docs(claude): note Claude-in-Chrome browser automation for live validation

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -42,6 +42,11 @@ The planning/architecture assistant ("project Claude", in claude.ai) writes spec
 - **`TASK.md` / `TASK-*.md`** — a spec for you to implement. Then push and update this repo's changelog (`hub/CHANGELOG.md`) and root `REPORT.md` per the convention below.
 - **`RUNBOOK-*.md`** — an operational procedure. CC executes the steps it has access and capability for, including live validation on the demo nodes and the demo Proxmox host (CC has root@felhom-pve SSH + the felhom-agent token). A step is human-only only when it genuinely needs physical presence, a real-world decision, or credentials CC truly lacks — mark those steps HUMAN. Do not decline a whole procedure because it touches a live host or a privileged token. (Judgment still applies: confirm before irreversible ops on real customer data — but demo scratch guests are fair game.)
 - Validation of a push against a spec's criteria is project Claude's job, not yours, unless asked.
+- **Browser automation available** (`claude-in-chrome` bridge installed): CC can drive the hub
+  dashboard (`hub.felhom.eu`), the website, or any `*.demo-felhom.eu` UI in a real browser for live
+  validation + screenshots. Caveat: the browser tools attach only to a session STARTED AFTER the bridge
+  connected — if missing, open a fresh task (don't assume it's broken); `/mcp` should show
+  `claude-in-chrome · connected`, else `/chrome` → reconnect.
 
 > **In every repository where you make a change, update both files in that repo:**
 > - **`CHANGELOG.md`** — a cumulative log of **all** changes; newest entry on top.