draft-and-picklisted

# Draft and pick Some decisions are settled by looking rather than by reasoning, and no draft is wrong until one is picked. Every step here puts several candidates in front of the operator and keeps the real surface untouched until they have chosen. ## Guards - If the request names one answer and asks for it to be built, stop: `❌ This names one answer, so there is nothing to pick between. Use /canon:plan-feature.` - If the decision has no visible form, stop: `❌ Nothing to look at. Drafting candidates needs a decision a render can show.` - Draft no candidate for a decision the operator has not asked to make. A run offering options everywhere spends their attention rather than saving it. ## Step 1: name the decision and the arms 1. State the decision in one sentence, naming what changes between arms and what stays fixed. 2. Emit the design read in the run's own output, in the form `design-taste` fixes. The layer comes from that skill's ordered catalog rather than from a word invented here, and the arms differ at it rather than somewhere cheaper to change. A run emitting no read has not decided what it is drafting, and a missing line is visible where an unstated layer is not. 3. Derive a kebab slug from that sentence. Call the folder every file this run writes to `<dest>` below. `<dest>` is `.canon/tmp/<slug>/`, a nested `<slug>/` folder rather than a flat `<slug>-<file>.md`, which is the shape every temporary write in this project takes. Running inside a live `plan-groundw