Add docs manifest fetch

[Joshalphonse]

Added the ability to fetch a Docs manifest from the mux.com repo. This way agents can access docs without pulling the entire mux.com repo or any files other than an index.json with all of the docs content.

---

Note

Medium Risk
Adds a new docs subsystem that fetches and caches documentation indexes from docs.mux.com (network + local cache), introducing new I/O paths and CLI surface area that could affect reliability and error handling.

Overview
Adds a new mux docs command group (search, read, update, source) and wires it into the root CLI.

Docs can now be indexed from a local mux.com checkout or pulled as published manifest.json/index.json artifacts from docs.mux.com and cached under the XDG cache dir, enabling search/read without cloning the full repo. Includes new search/query normalization logic, JSON-friendly outputs for agents, and comprehensive Bun tests for indexing, caching, and command wiring.

Package publishing is updated to include a new skills/mux-cli skill definition in npm artifacts.

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

[cursor]

--force option is declared but never used

Medium Severity

The --force option is defined and documented as "Refresh cached docs artifacts," but options.force is never read in the action handler or in either updateFromLocalSource or updateFromPublishedArtifacts. The update always runs unconditionally, making the flag completely inert. Users passing --force get no different behavior than without it.

Additional Locations (1)

• src/commands/docs/update.ts#L35-L40

 

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

[cursor]

Frontmatter parser inconsistently handles CRLF line endings

Low Severity

parseFrontmatter checks for '---\n' (LF only) on line 473 and uses '\n---' on line 477, so it silently fails to extract metadata from files with CRLF line endings. In contrast, stripFrontmatterBlock on line 689 correctly handles both via \r?\n. This means files with CRLF endings would get wrong titles (falling back to titleFromId) and missing descriptions during indexing, while formatDocContent would still correctly strip the frontmatter block.

Additional Locations (1)

• src/lib/docs.ts#L687-L689

 

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

[cursor]

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

There are 3 total unresolved issues (including 2 from previous reviews).

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

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

[cursor]

Identical error handler duplicated across command files

Low Severity

printDocsError is defined identically in read.ts and search.ts, and the same error-handling pattern is also inlined in source.ts and update.ts. All four implementations format and print errors the same way based on a json option. This duplicated logic risks inconsistent future fixes and could be a single shared utility.

Additional Locations (1)

• src/commands/docs/search.ts#L72-L83

 

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