feat: add docs command for browsing Prismic documentation

[angeloashmore]

Resolves:

Description

Adds a docs command with list and view subcommands so users can browse Prismic documentation directly from the CLI. docs list fetches a page index (optionally listing anchors within a page), and docs view renders a documentation page as Markdown with optional anchor filtering.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA ¹

---

Note

Medium Risk
Adds a new top-level CLI command that performs network requests and parses Markdown anchors, which could introduce new failure modes (HTTP errors, output parsing) but does not touch auth or data mutation paths.

Overview
Adds a new prismic docs top-level command with list and view subcommands to browse Prismic documentation from the CLI.

The command fetches a docs index and per-page anchor index, supports JSON output, and docs view can optionally extract a single section via #anchor using GitHub-compatible slug generation while ignoring headings inside code fences.

Introduces a PRISMIC_DOCS_HOST env override for the docs base URL and adds github-slugger as a dev dependency; registers docs in the main command router and excludes it from segment tracking.

^{Reviewed by Cursor Bugbot for commit d89c484. Bugbot is set up for automated code reviews on this repo. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d89c484. Configure here.}

[cursor]

Fence closing check ignores trailing content on line

Medium Severity

The fence-closing check on line 79 only verifies the line starts with the same fence characters via startsWith, but doesn't verify the rest of the line is empty (or whitespace-only). Per CommonMark, closing code fences cannot have info strings — a line like ```python inside a ``` block is content, not a closing fence. The current regex /^(?<fence>\{3,}|~{3,})/matches the fence prefix, andstartsWithsucceeds, so the code incorrectly exits the fenced block. This causes subsequent lines still inside the code block to be scanned for headings, potentially producing wrong anchor matches or corrupting theGithubSlugger` state — likely in documentation about code that nests fenced examples.

 

^{Reviewed by Cursor Bugbot for commit d89c484. Configure here.}