v0.0.68

A reliability release: accurate reports on large crawls, honest failure reporting, and faster repeat audits.

Added

• New --fresh-ua flag on audit and crawl to re-roll the browser identity the crawler uses for a project.

Changed

• The crawler now picks its random browser identity once per project and reuses it on every run. Repeat audits hit the render and analysis caches far more often, making re-runs faster and cheaper.
• JSON reports now include status and statusReason, so a failed or blocked audit no longer reads as a clean pass to scripts and agents consuming JSON output.

Fixed

• Large crawls keep every affected page in the report. On audits of hundreds of pages, a rule that flagged many of them could have its list of affected pages silently cut off past an internal limit, dropping pages from the published report and skewing the score. Those pages now fold into one accurate finding, so big audits report and score every page they should.
• Quick-coverage audits on paid plans no longer blame a cloud outage for checks that quick mode intentionally skips. The report explains it was a quick scan, shows how to run the full set, and renders the Agents score as locked instead of silently missing.
• Sites behind Cloudflare and similar bot protection that answer with a 503 challenge page are now reported as blocked with actionable advice, instead of a generic "site unreachable".
• Audits started with a bare domain (squirrel audit example.com) now reliably appear in your dashboard run history. They ran fine before but could be invisible to run tracking.
• Debug logs print real error details instead of [object Object].
• The crawl command docs now describe the --coverage flag and the real default page budget.