The suite runner moves into the package

[robertblust]

This site's verify/check.mjs now holds its SITE, its PAGES, and the checks that are genuinely its own. Everything else — the runner — comes from @robertblust/design v0.12.2.

What moved. 60 significant lines were identical in all three sites and sat outside the CHECKS object, which is the only reason the earlier consolidation missed them: the tool that measured duplication only ever looked inside that object, so "no check body exists in more than one repository" was true of the object and false of the file. They are not check bodies — they are the runner: the PAGES opt-in guards, the page loop and its result printing, and the site-wide sitemap.xml, robots.txt and favicon blocks. One of them documented its own triplication in a comment.

runSuite({ browser, SITE, BASE, PAGES, CHECKS, systemFaces }) returns a failure count. It takes a browser rather than launching one, because the package has zero dependencies and cannot import Playwright, and it returns rather than exiting, because a library that terminates its caller's process is untestable.

What this site gains. Every site ends up with the union rather than its own subset:

• the site-identity guard — fails unless /sitemap.xml names this site. One static server on port 8000 can serve the wrong repository, and a run once reported six failures belonging to a site nobody was testing.
• the favicon check — the favicon is the only place the brand mark exists outside a page, so no DOM check reaches it.
• failed-request detection and a font-readiness wait on blust.ch, which never had them.

A defect worth recording, because it nearly shipped inverted. v0.12.0 built the shared runner from blust.ch's copy, on the premise that all three were identical. They were not: companygraph and guestgraph each carried a requestfailed listener and a document.fonts.ready wait that blust.ch lacked. The premise came from a measurement that found the lines common to all three and mistook the common part for the whole — so adopting the runner silently removed a check from the two sites that had it. v0.12.1 restored all three lines verbatim, making runSuite a strict superset of every site's previous runner rather than their intersection.

And the guarantee itself was described wrongly, twice. The listener catches whatever the network stack or the resource's own loader aborts: DNS failure, a refused or blocked connection, and a 404 on a stylesheet, a script or an @font-face font. It does not catch a 404 on an <img>, which completes as an ordinary response and fails later at decode. The rule is not "404 versus network failure" — it is whether the thing consuming the resource aborts the load. v0.12.2 puts that in the code comment, along with the counter-argument it has to survive: read the guarantee narrowly and the listener looks like dead weight against a localhost server.

Output is unchanged on blust.ch and gains exactly one line — ✓ /favicon.svg — on the other two. design:check is a fixed point; no card moved.

🤖 Generated with Claude Code