Repository navigation
docs(support): Document research commands and output formats - #63
Merged
Merged
Conversation
philprime
marked this pull request as ready for review
November 18, 2026 16:36
philprime
enabled auto-merge (squash)
November 18, 2026 16:36
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.
Make support research discoverable without guessing commands, identifiers, or readable page layouts. Explain the article, guide, glossary, and terms workflows, including the boundary between catalog metadata and linked legal text.
Document support JSON separately from DocC output so script authors can handle resource-specific translations, rich content, and navigation correctly. Include skill-management safety, focused verification examples, and the telemetry boundaries for support lookups.