docs: clean up README and add the compatibility table - #20
Merged
Conversation
Drop the merged-main/issue progress language from the README and describe the repository as it stands. Add a capability compatibility table (Capability | Matrix scope | State) mirroring the del-rs README, generated from the machine-checked support matrix; state counts stay exactly planned 8 / frontend-supported 14 / semantic-supported 5 / lowering-dependent 8 / end-to-end-supported 0.
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
2 participants
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.
Summary
Clean up the opy-rs README: drop the merged-
main/issue progress language and describe the repository as it stands, and add a capability compatibility table (Capability | Matrix scope | State) mirroring the del-rs README.Changes
main/issue references ("What is implemented (merged main)", "issues Establish the OverPy feature inventory and compatibility corpus #2-Implement JavaScript macro and hook runtime compatibility #6 complete; issue Reach Workshop-independent OPY frontend completeness and expose tooling APIs #7 partially delivered", "Issue Reach Workshop-independent OPY frontend completeness and expose tooling APIs #7 is the active readiness gate", "Issue Integrate OPY lowering and end-to-end compatibility with workshop-rs #8 is blocked on Reach Workshop-independent OPY frontend completeness and expose tooling APIs #7 and Establish the canonical multi-locale Workshop core workshop-rs#2", the "(issue Integrate OPY lowering and end-to-end compatibility with workshop-rs #8)" in the pipeline paragraph).Validation
compatibility/support-matrix.json(all listed ids match their state; no mismatches).main/issue references remain (themain.opyCLI example filename is kept).