mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-14 02:42:24 +03:00
091589089c
ee24799e7cfroze 215 'pre-existing' errors measured on this devbox. The CI artifact from run 32968510623 shows what actually happens on a clean npm ci: ZERO unsuppressed errors and 150 suppressions that match nothing. The react-hooks findings those entries described do not fire in CI at all — they are an artifact of this machine's node_modules, the same phantom-count problem that once produced a fabricated '925 errors' locally. So the Lint job was not red because the repo had 215 hidden errors. It was red because I froze errors that only exist on my machine, and ESLint exits 2 on a suppression that no longer matches anything. Rebuilt from the CI artifact (messages + suppressedMessages, which is where a suppressed violation still shows up) instead of from a local lint: every count is now the value CI observes. 150 rules removed, 102 files emptied and dropped, back to the 1249 entries that predate the freeze. RequestLoggerV2's exhaustive-deps keeps the committed 6 rather than the 7 I derived — 6 is the value the artifact run demonstrably accepted, and a count above the real one is exactly what turns this gate red. The 9->6 prune in7afacf6c21stays: those three were genuinely dead, freed by restoring the manual-model block, and CI agrees.