feat(opy): clarify semantic ownership boundary - #32
Merged
Conversation
Teakowa
marked this pull request as ready for review
August 18, 2026 03:40
This was referenced Aug 18, 2026
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.
Completes the architecture and semantic-ownership track from #30. Splits OPY-owned manifest overlay support from Workshop-owned catalog/member/domain/settings/locale work, adds explicit catalog-link reasons for non-canonical entries, pins provenance, and documents the #8 adapter cross-check contract. Keeps the bare playervar receiver as an explicit genuine OPY residual instead of hiding it in Workshop breadth. No workshop-rs dependency or copied catalog data.\n\nAcceptance evidence: compatibility unittest suite, cargo fmt, clippy, workspace all-targets/all-features tests, and manifest/support-matrix tests pass locally.\n\nFixes #30