Compare commits

...

1 Commits

Author SHA1 Message Date
Probe Test
eb0e92bc88 fix(compression): rank the codex-responses engine in the adaptive ladder maps
#6533 guard: every registered catalog engine must have an aggressivenessOf()
rank above "off" and a non-generic expectedReductionFactor(), or floor-mode
escalation ranking silently treats it as inert.

The `codex-responses` engine (Responses Tool Output, stackPriority 12, added with
the 12-engine catalog) was never added to AGGRESSIVENESS / REDUCTION_FACTOR in
adaptiveCompression/ladder.ts, so aggressivenessOf() returned 0 (== off) and
expectedReductionFactor() fell back to the generic 0.9. Placed it between rtk (20)
and ionizer (25) with a conservative, lossless-first reduction factor of 0.85 — it
stays a single-mode engine, not part of the automatic DEFAULT_LADDER (like ionizer
/ relevance / omniglyph).

Validated: ladder-engine-maps-6533 now 3/3; the compression/adaptive ladder test
files stay green (24/0).
2026-07-23 03:34:23 -03:00

View File

@@ -36,6 +36,7 @@ const AGGRESSIVENESS: Record<string, number> = {
"session-dedup": 10, // stackPriority 3 — lossless cross-turn dedup
ccr: 15, // stackPriority 4 — reversible retrieval marker, only if it shrinks
rtk: 20, // stackPriority 10 — command-output filtering
"codex-responses": 22, // stackPriority 12 — conservative Responses tool-output compaction (single-mode)
ionizer: 25, // stackPriority 13 — tabular row sampling (lighter than headroom)
headroom: 30, // stackPriority 15 — tabular JSON compaction
lite: 40, // pri 5, but cheap prose pass (pre-existing reorder, kept as-is)
@@ -64,6 +65,7 @@ const REDUCTION_FACTOR: Record<string, number> = {
"session-dedup": 0.95,
ccr: 0.9, // conservative: only replaces a block when the marker is shorter than it
rtk: 0.85,
"codex-responses": 0.85, // conservative, lossless-first tool-output compaction (Responses API)
ionizer: 0.83, // row sampling, lighter than headroom's full tabular compaction
headroom: 0.8,
lite: 0.92,