Keep artifact trust loop copies on owner install route - #418
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
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.
Problem
The local
os-abyss-artifact-trust-loopskill copies needed an explicit owner managed install route so they are not interpreted as portable release artifacts. This PR records that boundary and refreshes the generated companions from the exact source.Changes
os-user-defaultmanaged-copy path as an owner source projection;generated/contract_abi_signatures.min.json;aoa-kagsource;Validation
--check, sentinel, full parity, family contract, and compatibility assembly: passed;aoa-sdkandaoa-stats, using a shortTMPDIR: passed;1963 passed;453d3494,7e06d8c5,3d61c9f3, and4f66c21a.Skips and limits
aoa-skills validate_skillswas not applicable because this owner tree has noschemas/skill-frontmatter.schema.json.+9,528,914bytes across 107 changed files and a tracked family size of30,393,580bytes versus the27,262,976standing budget; no standing budget policy change is included.