radin-recordlisted

# Record to Backlog This captures what a human said; `radin-review` logs what a diff revealed. Every downstream reader -- `radin-plan`, `radin-execute`, the execution sub-agent it dispatches -- is a **cold start**: it sees the entry and nothing of this conversation. Every step below exists to make an entry survive that. ## 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. 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, sized as a **vertical slice**: - It cuts a narrow but COMPLETE path through every layer it touches -- vertical, not a horizontal slice of one layer. - Landed, it is demoable or verifiable on its own. - It fits one fresh context window, the cold start it gets. - A **prefactor** -- the restructuring that makes the real change easy -- is its own entry, which every entry needing it depends on. Make the change easy, then make the easy change. One mechanical change whose blast radius fans