ss-verify

# Verify (look at it, don't just read it) First resolve the effective rule set from `PRODUCT-PRINCIPLES.md`, `RULESETS.md`, the selected built-in or reference-compiled grammar, `ADAPTERS.md`, domain/page, optional `PRESETS.md` profile, and `STYLESEED.md`. Judge pixels against that composed method. A lock value cannot excuse a core failure, and a profile cannot replace the output grammar. `/ss-score` reads the **code** and scores it. But some of the worst "AI-made" tells never appear in source — they only exist in **pixels**: a hero that doesn't actually dominate, a lower third of dead whitespace, cramped cards, a web font that silently failed to load and fell back to Times, two colors that *look* like two accents once rendered, text that's unreadable on its real background. A human sees these in half a second; a code-reading gate misses all of them. `/ss-verify` closes that gap: it **renders the UI, screenshots it, and you look at the image** — then score the same StyleSeed gate against what you see, fix, and re-render. This is the gate that most predicts whether a real user will say "this looks designed." Run it as the **final** gate after `/ss-score` passes — code-clean is necessary but not sufficient; pixel-clean is the real bar. ## When NOT to use - Nothing renderable yet (pure logic/config, or a component with no host page) → use `/ss-score`. - No way to render at all (no browser, no Playwright, headless blocked) → say so, fall back to `/ss-score`, and tell the u...