You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci(workflows): enforce 4 drift checks in CI that only ran locally
miner:env-reference:check, manifest:drift-check, engine-parity:drift-check,
and branding-drift:check were all part of the local `npm run test:ci`
aggregate but never wired into .github/workflows/ci.yml -- the exact same
gap class the "Selfhost env-reference drift check" comment already
documents having bitten twice before. Confirmed harmful live: the
miner:env-reference gap let a stale generated doc merge to main with green
CI, then block an unrelated MCP npm release days later, since the release
workflow (before being scoped down) was the only place that check ever
actually ran.
Also adds .loopover.yml to the `backend` path filter so an edit to just
that file still re-triggers manifest:drift-check, which reads it directly.
0 commit comments