Release v7.125.0

Added

• Decision records 150 (specifications never see runtime concerns; the idiomatic decision shape) and 151 (fast feedback is a product requirement).

Changed

• Application specification guidance now has specs supply read-model state and assert outcomes, and never configure decision reads or simulate competing appends. Arc's and Chronicle's own specifications prove those guarantees. AppendConcurrently is described as an advanced framework-verification API for explicit needs only.
• Command guidance recommends taking the read model as a Handle parameter, with [ReadProtection(On)] where a rule must hold under concurrency, instead of reading through IDecisionReads in Handle.
• Cratis code, documentation and examples always use and recommend the most idiomatic Cratis way unless something else is explicitly needed.
• Fast feedback is a stated requirement. Specs share setup where safe and run in parallel. Analyzers and generators are written for speed, and CI builds the specification path without analyzers while a parallel required job enforces every analyzer.
• A repository's accepted decision records and project rules are binding for AI work in that repository.