df-ui-verifylisted

# Dark Factory — Authed UI Verification (df-ui-verify) ## Overview `df-ui-verify` drives and verifies a **Clerk-protected web UI end-to-end with no human login**. It is a **feeder to `df-qa`**: the mechanism by which QA gets "eyes on" an authed front-end. Two phases (the df convention): a deterministic auth **script** mints a real Clerk session and writes a Playwright `storageState`; then the agent **drives** the live UI per PO scenarios, capturing browser-surface evidence and a verdict. The auth breakthrough that makes this universal: the backend **`dev_browser` handshake** mints the `__clerk_db_jwt` that the old "headed-login → capture storageState" flow could only get from a real browser. With it, the whole flow runs headless from a backend secret key. ## Scope — the kernel, not your drivers This skill ships the **portable half**: session minting, storageState assembly, evidence layout, and the verdict rule. It ships **no application drivers**. The per-app click-through scripts — the ones that know your routes, your selectors and your host — belong in the layer that owns the app, not in a generic method repo. Keep them beside the app or in your org's layer, and treat this skill as what they call. ## When to use - Verifying a deployed, Clerk-gated UI against PO requirements / test scenarios. - "Look at the website and click through it" — agent-driven exploratory verification. - Capturing per-scenario UI evidence for a df-qa verdict. ## Phase 1 — Authenticate (run the s