gh-fixlisted

# Fix a GitHub Issue Through Merge Treat `/gh-fix ISSUENUMBER` as authorization to implement, publish, continuously repair, and merge the fix for that issue. Work autonomously until the PR merges or a genuine external blocker requires the user. Never alter the user's existing checkout; perform all changes in a separate clone. ## Validate the request 1. Require exactly one positive integer issue number; accept an optional leading `#`. 2. Identify the GitHub repository from the user's explicit repository or the current checkout's GitHub remote. 3. Require `git`, `gh`, and an authenticated `gh` session with repository and workflow access. 4. Read the issue title, body, labels, comments, state, and linked context. Stop if it does not exist or is not actionable. If it is already closed, explain that and do not mutate the repository unless the user explicitly requested follow-up work. 5. Read repository instructions, including applicable `AGENTS.md`, contribution guidance, branch/PR rules, CI configuration, and changelog conventions. ## Create an isolated clone and branch 1. Resolve the canonical `OWNER/REPO`, clone URL, and default branch. 2. Create a uniquely named sibling or temporary directory outside the current checkout, such as `<repo>-gh-fix-<N>`. Never reuse or modify the user's current working tree, and do not substitute a worktree for the separate clone. 3. Clone the repository normally and verify that the clone's default-branch HEAD matches the remote. 4. Immediate