radin-recordlisted

# Record to Backlog Turn feedback, bugs, follow-ups, and ideas from the live session into backlog entries that survive past the conversation. This captures what a human said. `radin-review` logs what a diff revealed, and `radin-plan` and `radin-execute` consume the backlog afterward. All writes go through the shared CLI at the `RADIN_CLI backlog` CLI. It owns the index's schema and resolves the per-project namespace, so never hand-edit a backlog file or compute its path yourself. ## Step 1: Decide what to log The instruction after `/radin-record` sets the scope: - **Specific** ("add the auth timeout bug"): log exactly that item, nothing else. - **Generic** ("add the findings", bare `/radin-record`): scan the whole session for anything a reasonable person calls a bug, follow-up, idea, or feedback, including "we should probably..." asides nobody wrote down. Each distinct item becomes its own entry. Stay faithful to what was actually said. This is a capture tool: log only what the conversation raised, worded close to how it was raised. One raised thing can be several sequential pieces of work ("add rate limiting on top of new auth middleware" needs the middleware first). Log each piece as its own entry, split by the work's shape rather than the user's phrasing. When scope or split is genuinely unclear, invoke `/mattpocock-skills:grilling` on that point and let the user settle it before logging, mid-scan too. Distinguish that from an item that is *real but not yet