trial-runlisted

# /trial-run, trial planner and logger Two modes. Ask which applies if it isn't obvious from the conversation. A trial run is the only thing that produces a real score. Impressions of how a run looked are not data, and the report's results section needs the numbers. See the test rungs in `.claude/rules/workflow.md`. ## The discipline this skill exists to enforce **One run proves almost nothing.** The marker digits, the colour-to-row mapping, the book's horizontal position and the robot's starting orientation all re-randomise on every world load. A single successful run may only mean the seed was favourable. So every plan states a reload count, and every log states which seed conditions applied. ## Mode 1: plan, before the run 1. **Ask what's being tested and what would count as passing.** A test without a pre-declared numeric criterion is a demo, not a test. 2. Write the procedure: - Which subsystem or which full-run stage - **How many world reloads.** 20 for anything perception-related, 10 for grasp attempts. Not 3 - Which requested column and colour on each run, varied across the set - What gets measured and how it's recorded - What gets changed between runs, one variable at a time 3. State the pass criterion numerically. Starting points, from `.claude/agents/qa.md`: - Column detection: *correct digit on 20 of 20 world reloads* - Book detection: *correct colour and row on 20 of 20 reloads, all four colours and all four rows represented* - An