Two Releases, One Day: IntentCAD v0.6.0 and v0.7.0

You don't ship two releases in one day by working twice as fast. You ship them because the architecture lets you. March 7th: 22 commits, 2 version bumps, 5 completed EPICs, and a fundamental shift in what IntentCAD actually is. Here's how it happened and why the architecture made it possible. Why Two Releases v0.6.0 was infrastructure. Session durability, workflow packs, evaluation harness, architecture review. The kind of work that doesn't change what users see — it changes what the system can handle. v0.7.0 was the payoff. Objective-driven intents, document families, persistent storage. The features that only work because the infrastructure is solid. Shipping them separately matters. If v0.6.0 breaks something, you know it's infrastructure. If v0.7.0 breaks something, you know it's the new intent layer. Clean boundaries make clean debugging. v0.6.0: Workflow Packs as Composable Units The biggest idea in v0.6.0 is workflow packs. Not "features." Packs. A construction drawing and a des