v0.10.0

calibrates how much TDD ceremony a build gets to how certain the design is — without ever skipping the review.

long agentic runs were paying full per-change TDD ceremony on transcription work (re-deriving an already-validated design one failing test at a time). a real overnight run burned ~173M tokens, ~94% cache reads, ~92 Rails-booting spec invocations — and the gates returned zero must-fix every pass. the build loop was the waste, not the design.

Two tracks (new references/calibrating-rigor.md):

• Discovery — design emerging at the keyboard: strict per-change Red→Green→Refactor→Simplify→Pre-flight, with Shameless Green.
• Transcription — design already validated (verified prototype, mechanical port, trivial change): write the target shape directly, batch the build, one comprehensive spec, no micro-loop. When unsure, default to Discovery.

Wired through pair (sets the track, passes it to the builder), execute-plan, and ruby-builder.

What does NOT calibrate — the review. We check the code against our best practices every phase regardless of track. The prototype validates the design, not the port, and was never compliance-reviewed, so the verifier + compliance gates run per phase in both tracks. Transcription streamlines the build, not the review. Guarded by eval id 10.

Also: Shameless Green is now explicitly a Discovery tool (it guards against premature abstraction; on a known design it's ceremony), the ${CLAUDE_PLUGIN_ROOT} path fix is finished on ruby-builder, and there's a .gitignore for local .claude/ settings.

Created by Claude Code