How do you guarantee Lighthouse Mobile 95+?

Three CI gates plus one launch-night gate: (1) every PR runs Lighthouse against staging, below 95 fails the build; (2) Tailwind JIT purge runs in CI to ensure unused classes don’t bloat CSS; (3) Alpine.js tree-shaking + critical-CSS inlining are enforced; (4) launch night, we run Lighthouse against the production URL across PDP, PLP, cart, checkout and CMS, if any page drops below 95, we hold cutover. Once live, we run a daily Lighthouse drift check during the 14-day stabilisation window so regressions never make it past day 1.