[clabonte]

Pins generator 0.24.0 (sha256 85d1496e…c088902e7, checked against the release's .sha256 asset) and bumps the kit to 0.32.0. Record: compatibility.md §60. Reader notes: docs/generator-releases.md.

⚠ Before release

Do not register mcpHost or mcpEvalHarness on a real manifest at this pin. The generator's known issues say a preview tool commits instead of rolling back, and generated tools do not compile on a real manifest. The handbooks and release notes carry this warning.

What changes for projects

This is breaking for:

• every C# consumer of eventRuntime, which must author EF migrations
• an x-entity with no aiAccess
• AsyncAPI messages whose headers bind no eventId or tenant
• clients filtering outside filterableProperties, or sending an enum in another case
• outboxDialect: postgres

Kit changes

• Spectral: admits fieldSets and untrusted, with fixtures in both directions. Three Arazzo x-mcp shape rules become one warning, and their ids move to retired in rule-renames.yaml.
• Gate fix: check-extension-vocabulary.py dropped to its heuristic scan and blamed the jar when a surface had no keyed entries. The new mcp-manifest surface triggered this.
• x-mcp removal: gone from the scenario agents and skills, which called it required and added it automatically, and from hello-orders, the samples and validate-arazzo.sh.
• Handbooks and C# guide: document the contract changes. x-trigger-when is now scoped to the paths that enforce it, and x-effects and untrusted gain author guidance.
• Also included: the 0.23.0 release-notes entry flips to published, the same line as docs(generator-releases): mark 0.23.0 published #196, which can be closed.

Verification

Run on the released jar, against 0.23.0:

• hello-orders, fresh bundle: validate passes with 0 errors and 19 warnings, and generate exits 0
• Fresh scaffold: validate passes with 0 errors and 2 warnings, same findings as 0.23.0
• add-component csharp seed on regenerated output: dotnet build succeeds with 0 errors
• check-extension-vocabulary.py --require-jar is green
• Fixtures fire and stay silent as intended; rule coverage is 25/25 Arazzo and 122/122 OpenAPI
• Probe specs for the new validation codes, listed in §60

Not measured:

• runtime behaviour, including migrations, AggregateVersion ordering, the job lock and the filter and enum refusals
• MCP artifacts on a manifest
• a project with tenancy or a dbColumn override
• Python output
• scripts/test-csharp-contract-template.sh, because specfuse-loop is not installed locally; example-regen.yml runs the contract in CI

Those runtime claims rest on the generator CHANGELOG.

For review

• The handbooks still name PROJECT_BROKER_DIALECT_UNKNOWN and UNKNOWN_WORKER_HOST from the notes, but the jar's printed failures do not show those codes.
• MCP server is a closed list of six names in the jar, which looks like one consumer's vocabulary. Not yet raised upstream.
• The two-trait YAML in AsyncAPI_Handbook.md §2.1 is illustrative and was not run through the jar.

🤖 Generated with Claude Code