Publish scoped guidance and repair release dependencies - #24
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.
Prototype guidance now uses available source inspection instead of a missing get-context skill. The release also repairs the compatible dependency tree that blocked CI: Vitest and coverage-v8 4.1.11, patched fast-uri/js-yaml overrides, and compatible transitive security updates.
Validation: normal npm10.9.8 clean install and all local CI-equivalent gates passed: zero-vulnerability audit, lint, typecheck, coverage tests, production build, UI bundle budget and smoke, bundle/dead-export checks, source provenance verification and artifact assertions. No peer-resolution bypass or audit exception was added. GitHub Node22/24 CI is required before merge.