[mldangelo-oai]

Summary

scan --patch could omit the scan's resolved service tier when launching remediation. Inline patch executions now retain this setting alongside the existing model and reasoning effort.

Changes

• Resolve the tier through the existing scan profile configuration and carry it into the remediation child process.
• Retain the scan’s native default when the ambient Codex home requests a different tier, using the existing native default override.
• Add subprocess regressions for explicit and selected-profile tiers, ambient tier settings, overlapping scans, and standalone patch compatibility.

Testing

• A synthetic ambient-tier regression reproduced the native-default mismatch before the fix; 77 affected inline-patch, skill, and configuration tests passed afterward.
• Full SDK suites with seed 12345 and randomized order each passed 3,576 tests with zero failures on the pinned alpha.14 dependency graph before the subsequent C++ preview and export-decoding updates and the native-default follow-up.
• After the main merge to 1345ea3f, 195 export, configuration, and authentication tests passed, including all six export tests; 212 rank-preview and rank-input tests passed.
• Python Ruff lint and formatting, SDK build:ci, plugin bundle build, plugin source compatibility and its tests, SDK types, and formatting passed.
• Three fresh native review passes and independent verification passed for the exact final commit.

Risk and rollout

This preserves an existing scan setting through remediation. Public flags, accepted values, and defaults are unchanged. Standalone skill override restrictions, authentication, and sandbox behavior are preserved; tier selection remains isolated per scan.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-05T16:09:26.208018Z	bc90ff7	New commits
🔒 Security Review	✅ Completed 2026-10-05T16:09:25.197969Z	bc90ff7	New commits

ℹ️ 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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 08135ebec0

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[alandelong-oai]

Reviewed the full contribution at bc90ff7df6e38358fcb641542cb8815239dce7a8 with selected base 1345ea3fa48021ef54ecc2dcc948fde43fec8d0c, including changed tests and touched context, using three independent reviews followed by root synthesis.

No supported introduced finding.

Static source review; tests were inspected but not executed. CI, mergeability and integration are separate.