Add Codex runner diagnostic variant matrix - #23
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
Adds a diagnostic-only self-hosted runner matrix to observe Codex CLI 0.152 behavior across multiple runtime variants without changing C01-C16 capability results or the release gate.
Hook variants
hooks.json, canonical^Bash$, hook-trust bypass;^exec_command$;Compaction variants
body_after_prefix, TokenBudget disabled, one-tool control;body_after_prefix, TokenBudget disabled, forced second tool call;totalscope with TokenBudget disabled and forced follow-up.Subagent variants
agent_type=fixture_agent;agent_type;agent_typecontrol;Each variant records only structural event counts, sanitized error strings, diagnostic markers, hook records, and repository/auth/cleanup invariants. Raw transcripts are not persisted.
A separate
PlanAnvil Codex runner diagnosticsworkflow runs only byworkflow_dispatchonmainusing the existing controlled self-hosted labels. Variant outcomes are intentionally non-gating; only diagnostic harness execution and artifact creation are enforced.