mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-14 02:42:24 +03:00
d0f69e4c70
* chore(quality): re-freeze the ESLint suppressions on release/v3.8.51 from a clean-room run `No new ESLint warnings` failed on every PR against release/v3.8.51 with exit 2: "There are suppressions left that do not occur anymore". Measured in a depth-1 clone with `npm ci` from the branch's own lockfile and the job's exact command (`npm run lint:json -- --max-warnings 0`): 56 errors — 55 `no-explicit-any` in six files that landed while the base was red (#11843 isFree tests: 22;b7102140d5socks connect timeout: 33) plus one `no-unused-vars` — and stale entries for files that no longer violate. The devbox figure previously quoted in #11924 (280, with 224 react-hooks/*) does not reproduce on the lockfile install and is withdrawn. - config/quality/eslint-suppressions.json: `--prune-suppressions` (two stale file entries removed) and the 55 pre-existing `any` frozen at their exact counts — the file is a ratchet, counts only go down; the debt stays tracked in #11924. - open-sse/services/adobeFireflyCatalog.ts: remove `GPT_SIZE_MAP`, a constant thef3d9279b44split left behind with no reader (the real violation, fixed not frozen). Verification in the clean room after both changes, same command as CI: exit 0, 0 errors, 0 warnings (1238 files / 5487 suppressions). * chore(quality): tighten openapiCoverage.pct to the measured 39 (require-tighten) With ESLint back to 0/0 on this PR, the job's next step (check-quality-ratchet --require-tighten) started failing: openapiCoverage.pct improved from 38.4 to 39 (delta 0.6 > slack 0.5) and the baseline must be tightened in the same PR. 39 is the value CI collect-metrics measured on run 33213844112 and a clean-room checkout of777d9d1629reproduces it; the cycle's new routes landed documented in docs/openapi.yaml. Only this metric moves; annotation follows the file's convention.