Skip to content

fix(compression): rank codex-responses engine in adaptive ladder maps (base-red slice 2) - #8256

Closed
diegosouzapw wants to merge 0 commit into
release/v3.8.49from
fix/comp-engine-catalog
Closed

diegosouzapw wants to merge 0 commit into
release/v3.8.49from
fix/comp-engine-catalog

Conversation

@diegosouzapw

Copy link
Copy Markdown
Owner

Cluster: compression-engine catalog (base-red slice 2)

Segundo slice da reconciliação de base-reds da release/v3.8.49 (o primeiro é #8254).

Causa-raiz

O engine codex-responses ("Responses Tool Output", stackPriority 12), adicionado junto com o catálogo de 12 engines, nunca foi incluído nos mapas AGGRESSIVENESS e REDUCTION_FACTOR de open-sse/services/compression/adaptiveCompression/ladder.ts. Resultado:

  • aggressivenessOf("codex-responses") retornava 0 (== "off")
  • expectedReductionFactor("codex-responses") caía no default genérico 0.9

Isso quebra o ranking de escalonamento em floor-mode (guard #6533: todo engine registrado precisa rankear acima de "off" e ter um fator não-genérico).

Fix

Adicionado codex-responses aos dois mapas, entre rtk (20) e ionizer (25), com fator conservador lossless-first 0.85 (mesmo tier do rtk, ambos são tool/command-output). Segue single-mode — não entra no DEFAULT_LADDER automático (como ionizer / relevance / omniglyph).

Validação

  • ladder-engine-maps-6533: 3/3 (era 2 fail)
  • Sweep dos 5 arquivos de teste de compressão/adaptive-ladder: 24/0
  • Pre-commit (docs-sync, any-budget, tracked-artifacts) verde

Os demais base-reds (handleChat, provider candidate transparency, sidebar UI, i18n, etc.) são clusters de causa-raiz distintos, cada um em seu próprio slice.

diegosouzapw added a commit to fenix007/OmniRoute that referenced this pull request Jul 23, 2026
…8306

The complexity/cognitive-complexity baseline bumps (2130->2168, 951->956)
reconcile pre-existing release-branch drift unrelated to this PR's
image-generation API-key auth fix. Ratchet rebaselines are reserved for
the release captain (owner-approved, see prior _rebaseline_* entries in
these files) and are out of scope for a contributor branch. Reverting to
the recorded baseline; the underlying drift is real (measured 2167/956 on
origin/release/v3.8.49) and already tracked by the owner's open base-red
slice PRs (diegosouzapw#8254, diegosouzapw#8256).

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
@diegosouzapw
diegosouzapw force-pushed the fix/comp-engine-catalog branch from eb0e92b to d4b9ce6 Compare July 26, 2026 14:05
@mergify

mergify Bot commented Jul 26, 2026

Copy link
Copy Markdown

⚠️ The sha of the head commit of this PR conflicts with #7076. Mergify cannot evaluate rules on this PR. Once #7076 is merged or closed, Mergify will resume processing this PR. ⚠️

@diegosouzapw
diegosouzapw deleted the fix/comp-engine-catalog branch July 28, 2026 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant