One headless browser: ps-qa drives chuzz, and qa-inspect-host goes

[pathscale]

There were two headless browsers. ps-qa drove qa-inspect-host, chuzz is what ships, and the web platform existed in only one of them.

URLSearchParams, matchMedia, storage, the observers and performance.getEntriesByType come from chuzz's document loader. A host without them blanks every routed page before its first render — @solidjs/router destructures the result of performance.getEntriesByType during setup — so this harness could not reach a single site in the fleet, and every gap closed for the browser had to be closed a second time here, by hand.

The host is a mode of the browser now: chuzz-headless, in pathscale/chuzz#37. It loads through the same loader and the same engine a tab uses and serves this protocol over the same socket. ps-qa still links no renderer, and the core job's dependency-tree gate still proves it: that constraint was about the socket, never about which repository the host lives in.

--host was always a path, so nothing in ps-qa needed changing to point at it.

Also here

ps-qa click could not be used against a headless host. It read frame metrics either side of the action, as context, and failed outright when the host said it had none:

inspector returned unsupported: the headless page serves diagnostics Capture, Snapshot and WindowComposition only

A host that owns a document and no compositor is telling the truth there, and the one thing that could drive a built site could not be clicked. The numbers are optional where they are only context now, and the command says the host has none rather than printing zeroes. Where they are the point — idle, frames, drift, blink — nothing changes and the refusal still fails the command, because a zeroed reading from a host that never painted would pass every one of those while proving nothing.

Four earlier commits on this branch that had never been pushed, all from driving the @pathscale/ui sweep:

• feat(ps-qa)! type before pressing, and target a control the renderer laid out but did not paint.
• fix(ps-qa) the descriptor is the line that looks like one. The page shares the host's stdout, so one console.log at startup was read as a path and the component was reported as never having started — wrong about the host and about the component. Found on ThemeColorPicker.
• Two qa-inspect-host commits that the deletion supersedes. The substance of one, replacing a field's text by byte arithmetic rather than by a selection that needs a font catalogue, is carried into the new host in feat(headless): ps-qa drives chuzz, so there is one browser chuzz#37.

What this costs

The host CI job goes with the crate. It was the one place ps-qa drove a live page end to end, and it cannot be rebuilt here: this workspace may not link an engine. That coverage moves to chuzz, where both halves exist; pathscale/chuzz#37 carries the fixture and the socket test.

The published qa-inspect-host 0.1.12 stays on the registry, so the @pathscale/ui component sweep keeps working until it is pointed at the new host.

Verified

chuzz-headless serving support.cafe's built dist, driven by this ps-qa over the socket: find reports 4 buttons and 9 links with real geometry, audit reports 3 audited and 0 faults, clicking "Switch to light mode" renames the control to "Switch to dark mode", and clicking "Log in" leaves the home page and loads /login.

🤖 Generated with Claude Code