checkoutlisted

# checkout Get a teammate's branch into a local worktree so you can read or test it -- this is a review checkout, not the start of your own work. ## 1. Resolve the target Detect what was given and resolve it to one remote branch: - A branch name: use it verbatim. - An MR/PR link, `!iid`, or bare number: `glab mr view <ref>` or `gh pr view <ref>`, then read the source branch from the result. - A ticket id: search open MRs/PRs whose source branch or title carries it (`glab mr list --search <id>` / `gh pr list --search <id>`). If resolution is ambiguous or turns up nothing, gate `clarify`: one sentence naming the candidates, then the structured-question tool with one option per candidate, their text, and **Hold** (under a run, `rt runs field set gate clarify --stage <run.current_stage>` before and `rt runs decision record --contract gate@1 --scope clarify --selection '{"branch":"<picked>"}' --decided-by checkout` after). Never a guess. ## 2. Acquire the worktree Before creating anything, check `git worktree list`: if the branch is already checked out somewhere, point there instead of making a duplicate and stop here. Otherwise, prefer `rt` when it's available: ``` rt worktree provision --repo <repo> --branch <branch> --json ``` `<repo>` is discovered from the current checkout's origin remote (for example `git remote get-url origin`), never hardcoded. Pass `--title "<ticket title>"` when a title came out of the step 1 lookup (the MR/PR view or ticket search) -- with