Skip to content

Bound G11 subprocess interpreter operand attribution - #810

Merged
d6g8k5htny-coder merged 9 commits into
mainfrom
codex/cbz-g11-subprocess-options-20261110
Nov 10, 2026
Merged

d6g8k5htny-coder merged 9 commits into
mainfrom
codex/cbz-g11-subprocess-options-20261110

Conversation

@d6g8k5htny-coder

@d6g8k5htny-coder d6g8k5htny-coder commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

An invalid interpreter option inside a Python test subprocess could be counted as a static tool reference even when the interpreter exited before running the tool. Marker-bearing controls on Main 1a6acb192f0946900c4d445ee36febec27540da0 exposed invalid Python --check-hash-based-pycs, attached -Xutf8=2, and Bash -o operands. Local Python 3.12 and hosted Python 3.11 run 42770128530 each produced three selected assertion failures per mode, with a passing supported-option control. The hosted adverse job intentionally failed; its original artifact was independently checked and retained. This synthetic-fixture finding does not establish that a particular production tool failed to run.

The repair accepts a bounded Python operand set and declines unvalidated shell operands. Static references do not establish execution. The expanded tests execute all 17 supported separated or attached Python option combinations and add separate invalid -X and sh -o controls. Two older mutation definitions became redundant after the central guard; their actual 17/19 outcomes and prior bytes remain, their names are retained, and three new subprocess mutations make 22.

Main #807 merged during the work. Current head d72365a1701a05d0e6abb990fc38d6e4407fe763, tree 079d00619890da57b438b223b6be42732b044998, preserves the complete #807 decision prefix and all 15 non-decision peer changes. Its 6,099-leaf mode/type/blob map was independently compared with the peer tree and intended edits. The PR synthetic merge d79881f383b82f675f7b597761462c529371bf13 has the same tree and parents cff23146a56949e03cad4b15bdc4f07feba665ae and the current head.

Fresh push and PR component runs 42771684679 and 42771692209 each passed 265 census, 12 origin and 24 format controls per mode. Each run's 7 origin, 22 format and 328 original mutations per mode were individually checked for clean baselines, designated failures and authorized origin (714 records/run); both original archives were independently verified and read back. A separate exact-head census run 42771962121 passed both modes with 1,511 scanned files, 6,099 tracked leaves and no reported findings or skips; its two original reports and archive were verified and read back. These are bounded G11 component observations, not final G11 or a complete Layer A audit.

The earlier required workflow first failed on an unsafe/private daemon observation. Its retry completed architecture but the aggregate correctly failed because the formal receipt belonged to attempt 1; both failures remain preserved. The fresh required workflow 42771692289 succeeded on synthetic merge d79881f..., with current-run attempt 1 identities; the separate navigation run 42771691980 succeeded, but its independently checked original artifact reports 2,774 normal-discovery tests with 23 skips. Those skipped cases remain outstanding for a no-skip final regression; the selected history-reader and optimized graph-binding checks passed without skips. No claim is made about its eventual result.

Workspace #74 subsequently merged the tested pin tree as d26907ad9e60894b2904c2600aed3b0c02db7a91, pointing at Main #807; post-merge jobs are running. The later authenticated Pages deployment status was empty and does not establish cancellation or recovery. The original prepared Pages archive was independently checked against its receipt but has not been republished. All observations are time-bound and separately sourced. No mathematical statement, authorship, kernel outcome or scientific status is changed; CBZ-0 is not established.

@d6g8k5htny-coder
d6g8k5htny-coder marked this pull request as ready for review November 10, 2026 07:10
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T07:12:12.846205Z d72365a Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@d6g8k5htny-coder
d6g8k5htny-coder merged commit d1819f0 into main Nov 10, 2026
21 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the codex/cbz-g11-subprocess-options-20261110 branch November 10, 2026 07:11
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.

1 participant