operating-github-ci-fixer

# operating-github-ci-fixer Use `fix_github_pr_ci` for GitHub CI remediation requests, not `github_cli` or `shell_run`. Rules: - Pass `pr_url` when the user provides a GitHub pull request URL. - Pass `owner`, `repo`, and `pr_number` when the user names a repo and PR number. - Pass `branch` (e.g. `branch="main"`) when the user asks to fix a branch's failing CI itself; never combine it with a PR selector. Merged or closed PRs are refused — use `branch` for failures already on the base branch. - Omit `workspace` for a named repository or PR URL; the tool creates an isolated checkout. Pass a path only to edit that specific matching checkout. - If no repo is named, omit `owner` and `repo`; the tool uses the current checkout's GitHub origin. - The tool inspects failing GitHub Actions checks, fixes the local checkout or a temporary linked git worktree, commits, pushes the PR branch or fresh repair branch, and waits for the checks triggered by that push. It does not open a new PR. - Fork PR branches are refused by the tool because OpenSRE only pushes to branches in the same repository. - Branch targets such as `main` are never pushed directly; OpenSRE pushes a fresh `opensre/ci-fix-*` repair branch. - When the PR branch is behind its base branch, or GitHub reports it as conflicted (checks never start), the tool merges the base branch into the PR branch first, resolves the conflicts, regenerates lockfiles, and pushes. If the pushed fix itself turns out to conflict, it merges the base once more and re-verifies. A conflict it cannot resolve safely is reported with the exact files and what a person must decide. Do not run `git merge` around it. - The tool owns CI log inspection, fix execution, branch checkout, commit, and push plus post-push check verification. Do not run a raw `gh` workflow around it. - If the tool returns `response_text`, output exactly that text and stop. - If no fix is produced, keep the reply to one short line from `error`; do not say "next steps", add numbered options, list example commands, or ask a broad follow-up question.