v0.10.1

v0.10.0 introduced the Discovery/Transcription tracks but explained them in three separate places — the calibrating-rigor reference, the ruby-programming Quality Loop intro, and pair's build step. Thats token weight every session pays, and three copies that can drift. This collapses calibrating-rigor.md to a single 13-line source (down from 39) and turns the inline copies into pointers at it.

No behaviour change — and I checked rather than assumed. Both tracks re-verified against the leaner guidance:

• Transcription still batches the build while running the review every phase (eval 10, still green).
• On genuinely open design the skill still goes concrete-first (Shameless Green) and defers the abstraction — the "skip it on Transcription" line didn't over-rotate into skipping it everywhere. Verified two-arm (no-skill baseline vs skill arm, no spoon-feeding): the skill arm writes the one-agency version first, the baseline over-abstracts into a registry off a single example.

Created by Claude Code