radin-reviewlisted

# Review to Backlog Review a caller-specified scope on two axes, and persist every finding the user keeps as a backlog entry instead of terminal output. That leaves a durable backlog `radin-execute` (or a human) works through later. - **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? The axes stay separate end to end, for the reason `/mattpocock-skills:code-review` states under *Why two axes*. radin supplies the spec that skill has to hunt for: the backlog entry, or the plan `radin-plan` wrote from it. **Sub-agent caller** — `radin-execute`'s Phase 6 dispatches this skill that way, and a sub-agent reaches neither the user nor a spawned agent's result: run every step inline, Standards axis first, skip each `AskUserQuestion`, log every in-scope finding, and say in Step 6's report that no triage happened. ## Step 1: Resolve the scope ```bash RADIN_CLI scope [<arg>] ``` It prints `type`/`scope`/`command`/`passes` lines, and Step 3 invokes exactly the skills the `passes` line names. Route on its exit code: - **1**: not a commit, PR, directory, range, or `since <date>`. Report it and stop. - **2**: ambiguous, candidates on stderr (e.g. both a PR number and a directory). Ask which one; a sub-agent caller reports both readings and stops. State the resolved scope in one line — `Scope: commit a1b2c3d`, `Scope: directory src/auth/` — then capture both inputs the