From 7e72578d2cfada37052dd7095dcca5e3602baf3e Mon Sep 17 00:00:00 2001
From: simoleo89 <simoleo89@gmail.com>
Date: Sun, 14 Jun 2026 13:43:52 +0200
Subject: [PATCH] docs(CLAUDE): add Runtime verification section
 (Claude-in-Chrome, not headless)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Captures the session learning: the client can't be verified headless (WebGL
hangs + SSO login); use the Claude-in-Chrome extension on the real logged-in
localhost:5173 session (shared SSO cookie auto-logs-in, real GPU). Toolbar
buttons are canvas → locate by screenshot + click by coordinate.
---
 CLAUDE.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/CLAUDE.md b/CLAUDE.md
index 4e9578a..5be8066 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -86,6 +86,17 @@ link to a sibling working tree — `../Nitro_Render_V3` (preferred) or
 the codebase — that's expected on a sandbox without the renderer, not a
 regression.
 
+## Runtime verification
+
+This client can't be driven **headless** — the room renders via PixiJS/WebGL,
+which hangs in a headless browser, and login needs an SSO session. To verify a
+change at runtime, use the **Claude-in-Chrome extension** against the user's
+real, logged-in `localhost:5173` session: it shares the browser's SSO cookie
+(auto-login) and uses the real GPU. Toolbar buttons are canvas (not in the
+accessibility tree) — locate them by screenshot/zoom, then click by coordinate.
+The `preview_*` (headless) tools can't bind 5173 here and won't get past
+login/WebGL, so they're not usable for in-game verification.
+
 ## Stack snapshot
 
 - React 19.2.5, `react-dom` 19.2.5, `@types/react` 19.2.x.