radin-reviewlisted

# Review to Backlog Run the strict review passes against a caller-specified scope and persist every finding the user agrees to as a backlog entry instead of terminal output. That leaves a durable backlog `radin-execute` (or a human) works through later. Two **axes** carry the review, and they stay separate end to end: - **Standards** — does the scope follow the rubrics this repo documents? - **Spec** — does the scope do what the originating backlog entry or its plan asked for? A non-interactive caller cannot be reached and has no `AskUserQuestion`. Each step below names its own arm only where the two arms differ. ## Step 1: Resolve scope argument Resolve the argument (or its absence) via the shared CLI. Don't probe git/gh by hand: ```bash radin scope [<arg>] ``` Route on exit code: - **0**: resolved. It prints `type`/`scope`/`command`/`passes` lines. - **1**: not a commit, PR, directory, or range. A date phrase (`since yesterday`, `last week`) is the one exit 1 worth a second try: turn it into a revision with `git log --since="<phrase>" --format=%H | tail -1` (not `log -1 ... --reverse`: `-1` applies before `--reverse`, so it returns the newest commit in the window, not the oldest) and re-run `radin scope "<that hash>~1..HEAD"`, so the diff command still comes from the CLI. Every other exit 1 is unresolvable: report it and stop. - **2**: ambiguous (candidates on stderr, e.g. both a PR number and a directory). Interactive: ask which one. Non-interact