feat: scenario inflator for 400K token eval scenarios#384
Merged
Conversation
Adds inflate.ts with 15 filler templates (feature, test, refactor, debug) that inflate existing eval scenarios to ~400K tokens. This forces all baselines to actually compress, making the comparison fair. - inflateScenario() distributes filler proportionally across sessions - Protected keyword extraction prevents filler from contaminating test questions - Deterministic seeded PRNG for reproducible inflation - Token-accurate targeting (400K ± 1%)
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.
Summary
Adds a scenario inflator that pads existing eval scenarios to ~400K tokens with realistic filler content. This forces all baselines (tail-window, compaction, Lore) to actually compress, making the comparison fair.
Problem
Current eval scenarios are ~5-20K tokens — well within the 80K tail-window budget. Tail-window sees the full conversation while Lore has distilled it, making the comparison unfair. Real coding sessions are 200-400K tokens.
Solution
inflateScenario(scenario, targetTokens)injects realistic coding conversation filler between existing key turns:Example
Files
packages/core/eval/inflate.ts(NEW, ~2000 lines — mostly template content)