Skip to content

feat: gate candidate fixtures at the supported game version floor - #42

Merged
Teakowa merged 1 commit into
mainfrom
chore/retire-pre-support-fixtures
Oct 11, 2026
Merged

Teakowa merged 1 commit into
mainfrom
chore/retire-pre-support-fixtures

Conversation

@e54-bot

@e54-bot e54-bot commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

The candidate-vs-stable comparison scored every fixture in datasets/fixtures/challenge, including 38 screenshots from 5/6 month builds that are below minimum_released_version (v26.0811.1). A candidate trained on supported builds failed per-field no-regress on those.

batch_eval.evaluate takes an optional minimum_version; compare_candidate passes the floor from configs/bastion_screenshot_compatibility.json. Fixture data and the legacy HOLDOUT_IDS flow are untouched; stable and candidate are filtered identically.

Re-evaluating the 40aff1 Kaggle checkpoint under the floor: the four version regressions disappear; the only remaining regression is viewer_player 21/22 vs 22/22 (recent_hud_17, 毁 read as 毀), a real model misread.

Fixtures from game builds below minimum_released_version in the compatibility config are no longer scored by the candidate comparison, so unsupported 5/6 month screenshots cannot fail a model that reads supported builds.
@Teakowa
Teakowa merged commit ea346ad into main Oct 11, 2026
1 check passed
@Teakowa
Teakowa deleted the chore/retire-pre-support-fixtures branch October 11, 2026 16:00
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.

2 participants