Separate portable skill routers and reversible interface delivery - #88
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
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.
Session-memory skill routing can evolve independently of the active capture kernel. This change makes the two advertised routers consumer-neutral, migrates their home port to v3, and adds an owner installer for the complete selected skill interface.
The overlay validates a clean source and explicit shared contract, requires parity for unselected graph packages, preserves the existing kernel install profile, and supports bounded rollback from a verified receipt and backup even if source validators become unavailable. It leaves runtime data and user links with their existing owners. Decision D-0102 records this boundary.
Validation: 39 focused installer, skill system and behavioral sandbox tests passed; all 11 installer tests passed again after the stale forced-receipt regression fix. Capability/decision generated parity, source and exported-bundle validation passed; both public audits have zero blocking findings. Real read-only preflight against the existing runtime profile passed. A manual checkpoint review is bound to e0a2f68 and the originating session. CI and actual delivery/rollback are separate acceptance steps.