greenlisted

# Get a PR green `/orchd:green <pr-url|number>`, or no argument for the current branch's PR. Mechanical only. Never posts a comment, never re-requests a review, never opens or merges a PR. Review threads are a different job. **Two lines here are a repo's convention rather than a rule**, and they are marked where they appear: which task runner runs the checks, and which remote the base branch is fetched from. Read the repo's own `CLAUDE.md` before assuming either. ## Steps 1. `gh pr view <n> --json headRefName,baseRefName,headRepositoryOwner,url,title,mergeable,statusCheckRollup`. Head owner is not `gh api user --jq .login` → stop, it is someone else's branch to force-push. 2. On the branch already? Stay. Otherwise `git fetch origin <headRefName> && git switch <headRefName>`. Dirty tree → stop and show it. 3. Rebase onto the PR's own base: `git fetch <remote> <baseRefName> && git rebase <remote>/<baseRefName>`. Conflicts: resolve them, never `git merge`. A conflict whose resolution picks a behaviour is a judgement call, see [Easy or a judgement call](#easy-or-a-judgement-call). *This repo's convention:* the base lives on `upstream`, and the daemon's `upstream_ref` setting is the same answer where a session cannot ask GitHub. 4. Fix what is red, easy ones only: - Failed checks from step 1 → fetch each log. A repo with a `github` skill of its own says how; otherwise `gh run view <id> --log-failed`. - A failure naming a test absent from the