Release v4.68.0

Added

• Generated command values are admitted as ESM v7, selected only by generated properties, responses, generation fixtures or return expectations; unchanged models retain their ESM version, bytes and revision. Reference execution uses deterministic fixtures and reports Unsupported(IdentityAllocation) when reached generation has no fixture. Consumers must explicitly admit or reject v7 separately for reading, reference execution, rendering and reverse recovery; a package upgrade does not grant admission. (part of #300)
• Scalar and authored-order record command responses are available only on acceptance, with then returns assertions, paged MCP export, editor guidance and Invoicing examples. Operations, streams, handlers and exact mode remain independently unadmitted; UI response-name continuations and end-to-end navigation require downstream support. (part of #303)
• Generated values do not exist yet when a command is authorized or validated: policies, the implicit subject, rules and requirements that reference one report PLAY0273, and a generated property on a concept with validation rules reports PLAY0268. (part of #300)
• SemanticExecutionRequest.GeneratedValues supplies deterministic generated fixtures, and SemanticAccepted.Response exposes the accepted command response. RegisterProjectCorpus.V7 provides source-backed v7 conformance vectors, with expected responses in CanonicalCorpusSpecificationExpectation.Response. (part of #309)

Changed

• MCP execution readiness now names command handlers and exact numbers for any model that uses them, and reports generated properties on concepts with validation rules as not executable. (part of #309)