thalarch-browser-qalisted

# Thalarch Browser QA Use a **real browser/runtime capability that actually exists in the current host/session**. Antigravity may expose a Browser Subagent/Chrome integration; Codex or Claude Code may expose browser/MCP/Playwright/Chrome tooling differently; some environments may expose none. Never invent browser evidence, screenshots, console state, network traces, or a browser agent/tool name because another host supports it. Do not install a competing automation stack merely for ritual QA when an existing trusted browser path can prove the requirement. Do not silently install browser dependencies without authorization. If no usable browser capability is available, perform source/build checks that are still meaningful and keep browser/visual/interaction claims `UNVERIFIED`. ## QA path When browser tooling is available: 1. Start or locate the application using repository-native instructions. 2. Use the browser on the real running page, not a generated mockup. 3. Navigate the primary user flow. 4. Verify visible acceptance criteria. 5. Inspect console errors/warnings relevant to the change. 6. Inspect relevant network requests and failures. 7. Capture at least: - a compact/mobile viewport; - a normal desktop viewport; - any specific breakpoint named by the requirement. 8. Capture screenshots for load-bearing visual claims. 9. Exercise changed interactions, not only the initial screen. 10. When useful and supported, preserve a recording/trace artifact showing t