Guide first capability-map inputs through command help - #109
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.
Summary
audit_from_codeandcode_baselineexamples tocapability-map-admission --help, with an on-demand pointer from adoption guidance.Verification
npm run checkpassed on committed head643742248384e354b4689795318057ae0e4a2fda, including 315 browser tests, package artifacts, self-hosting and local release closeout.Boundaries
No caller input schema or admission policy is weakened. No consumer repository, native consumer witness, registry, provider setting or installed skill is modified by this PR. Pilot notes and working plans remain outside the package source. Merge requires all applicable checks at the exact head; publication and phase completion are separate.