[utsav-oai]

Summary

When patch preparation is blocked, users need to know whether any files changed and what has to happen next. This is especially important when a required change belongs outside the writable checkout.

Changes

The shared CLI prompt asks blocked results to explain what stopped the fix and what needs to happen next. When a fix depends on work outside the checkout, the explanation describes what the external component does, why it matters to the fix, and where the change belongs when known. It assumes the reader only knows the current repository.

Testing

• SDK type checks, formatting, and all 77 hosted remediation and CLI patch result tests passed.
• The earlier run that also included the broader CLI patch suite had 174 passes and 10 failures. The same 10 failures reproduced on unmodified main.
• The full SDK suite stopped after fixture ownership checks failed in the test environment.

Risk and rollout

This changes the instructions used to write blocked-result summaries. Hosted runs pick up the prompt with a CLI release. Model output has yet to be evaluated in a live run.

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: ✅ Completed

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

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-11-11T18:46:48.334541Z	41e9299	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.

[mluck-openai]

lgtm!

one thing to clarify - does this change anything about the schema between CLI and CSC? I don't recall if reason is a strict or an unstructured field

[utsav-oai]

lgtm!

one thing to clarify - does this change anything about the schema between CLI and CSC? I don't recall if reason is a strict or an unstructured field

this change doesn't have any schema changes, only prompt changes, so we should be fine. the reason field already exists.