Repository navigation
Pin generator 0.16.0; bump kit to 0.25.0 - #155
Merged
Merged
Conversation
- generator.lock pins 0.16.0 (sha256 dcd77128…7e8151); kit 0.25.0 in all four places. - x-ai.dataHandling (#153): AsyncAPI_Handbook §4.3, AI policy framework, create-worker skill; Spectral specfuse-async-ai-shape (warn), specfuse-async-ai-data-handling-shape (error), specfuse-async-ai-personal-data-region (warn); fixture + CI both directions. - Rules widened to match the jar: unavailable-properties-required covers an encrypted flattened value object (required since 0.14.0); no-inline-enums catches an allOf-wrapped inline enum (#2579). - Documents the 0.16.0 findings and breaking changes (eventRuntime, enum storage, encrypted enums, ENTITY_MISSING_ID, Arazzo payload checks, x-emits coverage, testGrants, tenancy column) and re-measures every claim tied to 0.15.0. Closes compat §19, §44 item 8 and all §49 items. - Corrects §2.1 / compat §51: the generated C# exceptions type Error.code as an integer, so the kit's Error does not compile with domainExceptions. - compatibility.md: v0.25.0 row and §52. Closes #153 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins generator
0.16.0(generator-distv0.16.0, sha256dcd7712870042b52cd5221e0f4d272aa67e28352b8cb456f5ff2cee92c7e8151, verified against the downloaded jar) and bumps the kit to0.25.0.compatibility.md§52 records the measurement in full.Measured on the released jar, against
0.15.0hello-orders, freshly bundled, gives the same validate report on both jars. Its 14 generated files differ only by the namespace fix (hello-orders.DomainbecomesHelloOrders.Domain, #2564).templatesis unchanged for all four languages.x-ai.dataHandling(closes #153; RestoManager handoff)create-workerskill.specfuse-async-ai-shape(warn): closesx-aiover the 4 parser keys plus the 6 documented informational keys, which go invocabulary-exceptions.yamlaskit_only.specfuse-async-ai-data-handling-shape(error).specfuse-async-ai-personal-data-region(warn).ai-data-handling.yaml, asserted in CI in both directions.Kit rules widened to match the jar
specfuse-xprotection-unavailable-properties-requirednow fires on an encrypted value object declaredstorage: flatten. The jar has requiredunavailablePropertiesthere since0.14.0. TheValueObjectOnlyEncryptioncontrol becomes an expected finding, and two new silent controls are added.specfuse-no-inline-enumscatches an inline enum wrapped inallOf,oneOforanyOf(#2579). New fixture and CI step.Documented
PROJECT_EVENT_RUNTIME_REQUIRED;ENTITY_MISSING_IDandENTITY_MISSING_AUDIT_FIELD;ARAZZO_STEP_PAYLOAD_*;ASYNC_EMITS_NO_EMIT_OPERATIONandASYNC_WORKER_SELF_TRIGGER;FUNCTIONAL_TEST_TAG_UNGROUPED, together withfunctionalTests, which was undocumented until now;TEST_GRANTS_GRANT_INVALID;TENANT_REMOTE_REFERENCE_FOREIGN_KEY_MISMATCH.0.15.0was re-measured and updated.Correction to #154. The generated C#
domainExceptionssetError.Codeto an integer andError.Idto a string, so the kit'sError(codea string,ida uuid) failsCS0029with that artifact. API_Handbook §2.1 and compat §51 now say so. Which side should change is an open decision, recorded in compat §52.Not filed (§52): a domain-filtered C# group with
eventandserviceemits no{Message}Eventclasses (CS0246, at both0.15.0and0.16.0).🤖 Generated with Claude Code