Comment on: [Feature]: Locked Gherkin DSL -- Bridging Shannon-Kolmogorov Gap for ~~Proven~~ Demonstrated Accuracy Gains

The main issue is VISION.md alignment. The project is extension-first: if it can be an extension, it should be. Nothing here requires core integration. GSD-2 already has an extension registration system, custom workflow definitions with pluggable verification policies, and a step-based engine that handles sequencing and artifact production. Gherkin generation, hash locking, and BDD enforcement all fit on top of that without touching core. As proposed, this would cut across state management, the verification gate, auto-mode, preferences, and the planning pipeline — deep core changes for an opt-in workflow preference. That bumps into "complexity without user value" territory per VISION.md, especially with config flags like `shannon_kolmogorov_bias` that require reading a paper to understand. The path forward would be to build this as an extension. Prove the value there across different providers and project types. If it demonstrates clear improvement, then there's a conversation about ...