Green CI after an agent PR used to make me relax. Then I merged a “small” fix that renamed a shared prop, skipped an a11y lint because the rule was warn-only, and shipped a modal that trapped focus forever — all while every check stayed green.
The suite wasn’t lying. It was answering the wrong questions. Agents are great at satisfying whatever your pipeline actually enforces. If the gates are soft, the diffs look confident and the regressions still land.
So I stopped treating CI as a vibe check and started treating it as a blast-radius fence for AI-touched frontend work.
What AI regressions actually look like
The failures I care about rarely show up as “test file missing.” They look like:
Contract drift — export renamed, optional prop made required, event payload shape quietly changed
A11y regressions — interactive div , missing label, broken focus order, live region that never announces
Dependency sprawl — new package for a one-liner the repo already has a util for
Token / theme leaks — hardcoded…