dsh-shipcheck

Frontend readiness has too often come down to an agent replying looks good in a chat window. A gut feeling without evidence expires the instant something changes.

dsh-shipcheck hands the verdict back to a real browser. Through dsh-pilot it opens the actual page and runs deterministic checks: page availability, visible body and primary heading, missing image alt text and unnamed controls, horizontal overflow at the captured viewport, required and forbidden text, required CSS selectors, structural regression against a named baseline, and runtime signals such as console errors and 4xx-5xx requests. Every run produces a screenshot and a JSON report; every failure carries a concrete evidence path. Ship single-page inspection with shipcheck_run, a release gate of up to 20 routes in one browser session with shipcheck_matrix (sequential, per-route reports, aggregated summary), or a bounded user journey of up to 30 real steps with shipcheck_flow (step screenshots, redacted inputs, stop at first failure). Baselines are written only by the explicit shipcheck_baseline tool; a normal run never mutates a stored snapshot.

No API key, cloud dashboard, or automatic project writes required. It fits frontend teams wiring agent workflows into their delivery pipeline: matrix the core routes before a release, flow the critical login-to-checkout path after each iteration, and layer dsh-palate design judgment on top in a future phase. Evidence first, opinions second.