6 gates that catch what your test suite can't

Running live Astro sites taught me that production breaks in ways tests can't catch — stale cached HTML after a deploy, an outdated claim, a broken internal link, a third-party font CDN injecting a tracking pixel.

The fixes are now a reusable engine: @acsaven/astro-ops.

The 6 gates:

1. Build ID — Content-hashed build identifier so edge caches can't serve stale HTML after deploy

2. Freshness watchdogs — Flags claims that reference external facts (pricing, dates) and warns when they're stale

3. Lighthouse budgets — Automated performance budgets that fail the build if you regress

4. Generated sitemaps + schema + llms.txt — SEO artifacts built from your content, not hand-maintained

5. Links gate — Catches broken internal/external links before deploy

6. Third-party tripwire — Alerts if a new external asset appears that you didn't explicitly allow

Not a theme. Not a UI kit.

It's opinionated about what happens after your site looks right. The gates are extracted from real failures on live Try sites.

Free. MIT. No paid tier.

→ https://github.com/acsavenhq/astro-ops