fix(docs): repair the /mcp redirect and unpublish the internal analytics note

[a-essawy]

Found while auditing Search Console for rendobar.com on 2026-07-21. Three defects, all from docs.json disagreeing with the file tree.

/mcp/* redirected into a dead page

{"source": "/mcp/:slug*", "destination": "/mcp"} — but the page is mcp-server.mdx. There is no /mcp. Every /docs/mcp/* URL 308'd to /docs/mcp, which returns 405:

/docs/mcp/overview      308 -> /docs/mcp   405
/docs/mcp/installation  308 -> /docs/mcp   405

/docs/mcp/overview is linked twice from the public llms.txt, and Search Console has it sitting in "Crawled - currently not indexed" with 5 impressions at position 23. Repointed the splat at /mcp-server and added an explicit bare /mcp rule (the splat does not match the bare path — verified: /docs/mcp was not redirecting).

/job-types/caption-burn took two hops

It fell through the /job-types/:slug* splat to /jobs/caption-burn, which then redirected again to /jobs/captions/burn. Added a direct rule ahead of the splat.

ANALYTICS.md was a public page

Mintlify serves every .md/.mdx in the repo whether or not it is in navigation. So an internal PostHog note was live at https://rendobar.com/docs/ANALYTICS (HTTP 200) and listed in /docs/sitemap.xml. CLAUDE.md and README.md had already been deleted from this repo for exactly this reason — this one was missed. Moved to .github/.

Guard

scripts/validate-nav-and-redirects.mjs fails CI on all three classes:

1. a page file with no navigation entry (it is still live and sitemapped)
2. a redirect whose destination is not a page in this repo
3. a navigation entry with no file behind it

Static checks against docs.json plus the file tree, no network.

Why nothing caught these before: validate-frontmatter.mjs only walks .mdx, so a stray .md was invisible to it, and the workflow's path filter only triggered on **/*.mdx, so a docs.json-only change ran no checks at all. Both now include **/*.md and docs.json.

Test plan

$ npm run validate:frontmatter   # Checked 16 MDX files. All frontmatter valid.
$ npm run validate:nav           # Checked 16 pages, 16 nav entries, 23 redirects. All consistent.
$ npm run validate:plan-limits   # Plan-limit tables match the source of truth.

Guard verified against the real bug: temporarily restoring /mcp/:slug* -> /mcp makes validate:nav fail with Redirect "/mcp/:slug*" points at "/mcp", which is not a page in this repo; reverting makes it pass.

After deploy, confirm:

curl -sI https://rendobar.com/docs/mcp/overview   # expect 308 -> /docs/mcp-server -> 200
curl -so /dev/null -w '%{http_code}' https://rendobar.com/docs/ANALYTICS   # expect 404

The /docs/ANALYTICS check is the one to actually run: it confirms that a dot-directory is outside Mintlify's content tree, which is the assumption the guard's suggested remedy rests on.