Verify

The doctor ships with the install. It is read-only: it reads the CSS entry named in components.json, follows every import it finds, and looks for the data-skin stamp.

Keep it runnable as a script, so a later session — or your agent — can check the wiring without this page:

Anything else is one of the five checks below. Errors exit non-zero and block: styling on top of them is what reads as a broken install afterwards. Warnings exit zero and are deletion offers, named file by file and token by token.

--contrast resolves the theme contract's required color pairs straight from the installed CSS — no browser, no network — and prints a per-mode tally with every failure named:

It reads the Tailwind palette, the core theme, the installed skin theme and every *.control-ui-theme.css the entry imports, in that order, so it sees exactly what the browser resolves. A pair a recipe paints is not guessed at; those live in the rendered audit at /theme-accessibility. A failure names the pair, its ratio and the threshold, and exits non-zero. A value the engine cannot model, such as color-mix(), is reported as unverified instead of passing.

--emit-css turns a theme artifact into the one derived stylesheet an app imports:

It writes midnight.control-ui-theme.css beside the artifact. Never hand-write those selectors: the emitted scope doubles the data-skin attribute to match the pack's own weight, which is what hands the win to source order.

The doctor audits wiring, never taste. It cannot see a token that is ugly, only one that is undeclared, dead, or fighting the skin.

Each deletion it offers is a change to source you own, so it names the file and the token instead of writing them: the sweep stays yours to read as one diff.

Run it after every install, update, and migration. A migration you said yes to ends clean, not hybrid.