Define selected creation in inference-only collections - #52
Merged
Merged
Conversation
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
1 participant
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.
Clarifies that request-level type selection is not a mandatory frontmatter representation. Empty explicit keys must permit selected creation when final persisted data matches, with all applicable schemas validated and lifecycle/matching safeguards retained.
Adds nine shared fixtures: selected tag matching; ordinary type metadata; nonmatch rejection; auxiliary validation and successful multi-membership; derived/supplied paths; serialization-policy membership loss.
Based on 5aa34fd, the spec revision already pinned by current Rust releases. Consequently this PR also contains the existing rename-reference fixture prerequisite from #51; it does not invent another rename policy. Both engines pass the nine new fixtures locally. TypeScript has one existing legacy rename discrepancy against that pinned Rust prerequisite, tracked separately from membership semantics.