docs: make the compatibility section readable for humans - #21
Merged
Conversation
Add a plain-language legend for the five support states (frontend-supported, semantic-supported, planned, lowering-dependent, end-to-end-supported) and explain what observable semantic compatibility means in practice, so the README reads without needing the machine matrix as a glossary. Keep the machine-scoped table and the four stable-contract statements verbatim; no state data changed.
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.
Humanize the README Compatibility section: add a one-line plain-language legend for the five support states and a concrete explanation of observable semantic compatibility, so the section reads without the machine matrix as a glossary. The machine-scoped table, state counts, and the four stable-contract statements are unchanged.