Repository navigation
docs: clarify query execution and permission boundaries - #33
Merged
Merged
Conversation
Contributor
Author
|
Added in commit |
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.
What changes
Availability boundary
The committed manifest and current npm release are both CLI 0.6.45 and do not expose a structured
querycommand group. This PR deliberately adds no unreleased command invocation, invented endpoint, or replacement manifest. Existing released commands stay usable. Concrete new command help/schema should arrive through the existing publish → manifest → reviewed skill-sync workflow when that CLI capability is released; backend route activation is a separate prerequisite.This is the public consumer skill, not a repository-local coding skill or managed-sandbox instruction.
Verification
node scripts/validate-cli-docs.mjs: 90 invocations across 38 Markdown files match the CLI 0.6.45 manifest.No credential changes, backend deployment, CLI publication, or generated API-reference mirror edits.