reviewlisted

# Review a PR's threads — the orchd overlay session `/orchd:review <pr>`. One session answers the whole of a PR: you read the threads, the human picks a way to resolve each one in the review overlay, you make the changes they picked, and you post. This is **overlay-driven**, not a pane you are steered from. You do not sort the threads or choose between options — you propose, the human decides in the overlay, and their decisions come back to you over the one channel that reaches them. So there is no numbered list to keep stable and no `AskUserQuestion`: the cards are the UI. ## First, ask the daemon what this is Everything below needs values only the daemon has. One call, before anything else: ```bash curl -sS "$ORCH_URL/api/pr/$PR/triage-context" -H "x-orch-token: $ORCH_POST_TOKEN" ``` ```jsonc { "pr": 35264, "owner": "…", "repo": "…", // the repo the PR is on "login": "…", // you: a thread whose last comment is yours is answered "language": "…", // what to write replies and stories in "tracker": true, // false: never propose `story+reply` "tracker_host": "…", // the host a story URL you report must be on "upstream": "…", // the ref this branch is measured against "proposals_url": "…" // where phase 1 ends } ``` `$PR` is the number you were invoked with. `$ORCH_URL`, `$ORCH_POST_TOKEN` and `$ORCH_ASK_TOKEN` are in your environment already. If they are not, you are not in a session the