Repository navigation
feat(ci): wire the F2.4 compression budget-gate ratchet - #4232
Merged
Merged
Conversation
budgetGate.ts (tokensPerTask / checkTokensPerTaskGate) existed but had no baseline, no runner and no CI job — a "ratchet in name only" (audit finding). This makes it a real gate. - check-compression-budget.ts: runs the deterministic engines over BENCHMARK_CORPUS and fails if any engine's mean compressed-tokens-per-task RISES beyond 2% vs the frozen baseline (better compression always passes; refresh with --update). Deterministic + API-free → portable to CI. - compression-budget-baseline.json: the committed per-engine per-task baseline. - npm run check:compression-budget + a "Compression budget ratchet" step in the quality-gate job. A unit test asserts the committed baseline is not stale (matches the current benchmark) and that a tightened baseline is flagged as a regression — so a future change that worsens compression is caught both in the test suite and in CI. Part of the compression "100% functional" program (audit long-tail).
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Jun 19, 2026
Merged
tkgo11
pushed a commit
to tkgo11/OmniRoute
that referenced
this pull request
Sep 23, 2026
…rence#4232) Integrated into release/v3.8.29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contexto
Programa compressão 100% funcional — cauda longa, item de maior valor. O
budgetGate.ts(tokensPerTask/checkTokensPerTaskGate) existia mas sem baseline, sem runner, sem CI — um "ratchet só no nome" (achado da auditoria). Este PR o torna um gate real.O que muda
scripts/check/check-compression-budget.ts: roda os engines determinísticos sobre oBENCHMARK_CORPUSe falha se otokens-per-taskmédio de qualquer engine subir > 2% vs a baseline congelada (melhor compressão sempre passa; refresh com--update). Determinístico + API-free → portável local↔CI.compression-budget-baseline.json: baseline commitada (por engine × por task: prose/tool-output/json).npm run check:compression-budget+ step "Compression budget ratchet" no jobquality-gatedo ci.yml.Saída real
Validação
typecheck:core✅ ·eslint✅ · YAML do ci.yml válido (step presente).Agora uma mudança futura que piora a compressão é pega na suíte de testes E na CI.
🤖 Generated with Claude Code