Repair PR

Goal

Repair only problems within the scope of the current or specified GitHub PR once, then stop. Handle merge conflicts, unresolved review feedback from chatgpt-codex-connector[bot] and the authenticated GitHub user (@me), and CI failures in that order. Correct actionable findings, assess incorrect findings with concrete evidence, and resolve handled threads. Create a separate commit for each distinct repair problem that changes files, but publish only after all local changes are complete. Ordinary PRs push once; stacked PRs use the scoped final pushes owned by $manage-stacked-prs.

Repair scope

• Before fixing a review finding or CI failure, establish its relationship to the PR's purpose and diff using the relevant implementation, logs, and tests. A failure outside the changed files is in scope when the PR changes caused it; file location alone does not determine scope.
• Do not fix unrelated pre-existing bugs or CI/infrastructure failures. Report them with supporting evidence in the current chat. If the relationship to the PR is unclear, do not make a speculative fix; report what evidence is missing.
• Record out-of-scope review findings as blocked and leave their threads unresolved. Being outside the PR scope does not make a finding incorrect.
• Record required validation failures accurately, even when their causes are outside the PR scope. Failed or skipped validation does not block the final push or handling fixed and incorrect review threads; preserve those results in the repair record and final report.

Comment policy

• By default, report repair results, progress, and supporting evidence in the current chat. Do not post top-level PR comments, repair summaries, new reviews, or inline replies to actionable findings.
• An objectively incorrect bot finding is the exception: a concise English explanation with concrete evidence may be posted in its original inline thread without a separate human request. This exception does not apply to findings authored by @me. This reply is optional; resolving the incorrect-finding thread is required under Finish once, even when the reply is omitted or fails.
• Other PR comments require an explicit human request. Preserve that request and its scope when supplied directly or through an authorized handoff. A repair or maintenance invocation alone is not a request to post comments.