Make C12 qualification deterministic - #16
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
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
Replaces the model-planned C12 setup with a deterministic runtime probe so
project_doc_max_bytesis tested independently of planner behavior.C12 automatic-loading probe
AGENTS.mdwith a secret head marker inside the first 1,024 bytes and a secret tail marker at byte 3,072;project_doc_max_bytes = 1024in project config and redundantly passes-c project_doc_max_bytes=1024tocodex exec;FAILEDif the secret tail marker beyond the budget is actually visible.PlanAnvil explicit-read assertion
map_instructions.pyimplementation outside the model;full_read=true, andtruncation_risk=trueat the same 1,024-byte automatic budget;Scope / safety
danger-full-access;workflow_dispatch-only frommain;