Repository navigation
Migrate visual primitives to VP CLI and Skill Set - #1
Merged
Merged
Conversation
Squashed from locally reviewed branch feature/vp-cli-skill-set-release. Final local review accepted VPREL-001 through VPREL-012.
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.
Summary
@mapleluvr/visual-primitiveswith thevpandvisual-primitivesaliasespi.skills, without a Pi extension runtimemasked-oracle-diffowned by the frontend replication workflow with package-local launchersVerification
vp, and package-local masked diffRelease boundary
This PR does not rename the repository, publish npm packages, configure Trusted Publishing, create a tag, or create a GitHub Release. Those live bootstrap steps remain separately authorized and are documented in
RELEASE.md.Transport note
The remote branch is a squash commit whose tree is byte-identical to the fully reviewed local implementation. GitHub smart-HTTP was unreachable from the implementation host, so the branch was created through GitHub's Git Data API after verifying the returned tree SHA against local
HEAD^{tree}.