Migrate Component Model to the vNext plugin system - #11
Merged
Conversation
Why: - the ecosystem must use Wago's explicit, authority-scoped provider and contract model What: - replace legacy registration with canonical provider catalogs - declare strict configuration, authorities, lifecycle, and reviewed graph metadata - pin the exact Wago vNext revision and remove local filesystem overrides Proof: - race tests, vet, and catalog check pass Docs: - README and plugin metadata updated for vNext
Jairus (JairusSW)
marked this pull request as ready for review
August 12, 2026 16:26
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.
Summary
Depends on wago-org/wago#428. Reworks runtime integration around explicit providers, bounded authority, typed contracts, strict config, and lifecycle-safe callbacks.
Validation
Repository tests, vet, canonical catalog checks, and diff checks pass on the supported platform matrix. Local filesystem module replacements were removed before publication.
This remains a draft until the coordinated stack is reviewed. No tag, release, registry publication, or deployment is included.