Turning CI back on found rotted tests
Re-enabling CI after a pause surfaced 28 lint errors and four suites written against interfaces that no longer existed — drift, not regression.
The safety net had a hole
The test, the audit log, the scanner, the CI run — covering less than I assumed it did.
With the pipeline re-enabled, main immediately failed on 28 lint errors and four unit suites written against interfaces that no longer existed. None of it was a regression, just drift from the period CI was off.
The intuition is backwards: the cost of disabling CI isn't mainly that bugs ship, it's that the test suite quietly stops describing the system and you find out at the moment you need to trust it.