Shipping a Chirp app to production, or staring at a swap that won't fire? This
section is the safety net. Chirp validates your hypermedia wiring — routes,
fragments, OOB regions,
SSE payloads — at
startup, so broken UI fails loudly in CI instead of silently in front of users.
Start with Debugging Swaps if something is already broken; start with the
Route Directory Contract to see whatapp.check()enforces before you ship.
chirp check, DevTools, debug headers, and swap failure modes
Fix htmx, OOB, Suspense, SSE, and boosted navigation updates that won't fire.
Reserved files, route metadata, sections, and shell contracts
See exactly what fails CI before you ship filesystem routes and app shells.
Categories, default severity, and fix targets
Look up any contract failure by name and dial its severity up or down.
Fail-loud region validation
Catch empty OOB swaps that would silently wipe live DOM before users hit them.