Add fixed navigation task benchmark (#384) - #497
Merged
Merged
Conversation
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
1 participant
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.
Closes #384.\n\nAdds a graph-pinned fixed navigation benchmark driven through the real Quake engine and NetQuake puppet. Suites declare fixed starts, goals, skill, budgets, and train/held-out splits; reports preserve per-task failures and summarize completion rate and median game time without mixing the held-out partition into tuning.\n\nThe developer-only QuakeC control path is inert unless explicitly armed through the scratch/impulse protocol. The committed dm4 suite completed 3/4 tasks in its full smoke, including both held-out routes.\n\nVerified with modern FTEQCC (no new diagnostics), a live one-task and full-suite engine smoke, 255 Rust unit tests, strict clippy, CLI checks, and ship/EOL/tape/nav invariants.