Repository navigation
Define versioned diagnostic identities and compatibility - #618
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
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.
Defines distinct diagnostic identities for canonical ACTIONs, schema shapes and assertion-gap reports while preserving published schedule meanings and retired codes. Documents the unreleased 7.0.0 numeric compatibility boundary without changing release pins.
Corrects the action-card ID predicate, separates DGCA collection shape from nonempty requirements, places PMAP-002 with process maps, and distinguishes historical inline scenario diagnostics from projection validation. The migration guide explicitly records revision-bound validator gaps, including products and schedule code collisions, instead of claiming runtime conformance.
Validation: 136 notation, release-obligation and vocabulary tests passed; documentation lint passed with four existing warnings; whitespace checks passed. Both independently added regression tests are retained after merging current main. No release or installed-validator conformance is claimed.