ring-testlisted

# /ring-test, ring test planner and logger Two modes. Ask which applies if it isn't obvious from the conversation. Ring testing is the only verification that counts for traction, edge detection and blade geometry, because none of those exist on a bench. See the test-rung ladder in `.claude/rules/workflow.md`. ## Mode 1: plan, before the test 1. **Ask what's being tested and what would count as passing.** A test without a pre-declared pass criterion is a demo, not a test. 2. Write the procedure: - What gets driven, from what starting position, at what speed - How many repetitions. Enough for a real pass rate, so 20 runs rather than 3 - What gets measured, and how it's recorded - What gets changed between runs, one variable at a time 3. State the pass criterion numerically. Examples: - Edge sensing: *20/20 stops before the white border from full speed, from four approach angles* - Edge discrimination: *0 false triggers while crossing the brown centre lines, over 20 passes* - Traction: *measured push force against a known resistance, compared across wheel compounds* - Blade: *lifts a test opponent's front wheels off the ring in 8/10 head-on approaches* - Battery: *three full 3-minute matches without regulator sag or reset* 4. Pre-test safety checklist, mandatory, from `.claude/rules/workflow.md`: - [ ] Kill switch tested and working - [ ] Battery charged and secured - [ ] Blade checked for bend, ride height verified - [ ] Wheels clea