chore(content): add check:library-content audit for content posts

[waleedlatif1]

Summary

• Adds check:library-content (scripts/check-library-content.ts), picked up automatically by bun run check:audits. It validates every apps/sim/content/{blog,library,customers}/<slug>/index.mdx, or a single post with --slug <section>/<slug> / --slug <slug> / a bare <slug> for local agent runs. Each rule is exact, so nothing needs an override:
  • frontmatter: gray-matter parses it and it passes the real strict ContentFrontmatterSchema (imported, not duplicated), so canonical and other unknown keys fail; every author id has a profile in content/authors.
  • slug: slug equals the folder name.
  • og-image: ogImage is a local path to a file under apps/sim/public.
  • mdx: the body compiles with @mdx-js/mdx + remark-gfm (the compiler next-mdx-remote runs for the registry). The error line maps back to the line in the file.
  • faq: no FAQ/FAQs heading in the body, and no Markdown link syntax inside a frontmatter FAQ question or answer (it renders as literal text).
  • internal-link: every https://www.sim.ai/<section>/<slug> link, and every relative /<section>/<slug> link target, resolves to an existing post folder. A retired library slug fails and names the surviving slug; a blog slug that moved to /library fails and names its new path. Asset paths (/library/<slug>/cover.jpg), static sub-routes (tags, authors, rss.xml, read from the app router tree), and fenced code are skipped. Apex https://sim.ai links stay with check:site-urls.
  • On a full run, it also checks that every LIBRARY_MERGED_SLUGS target still exists.
• Moves LIBRARY_MOVED_BLOG_SLUGS and LIBRARY_MERGED_SLUGS from next.config.ts into apps/sim/lib/library/retired-slugs.ts, so the redirects and the audit read the same map.
• Fixes the only findings on current content: two FAQ answers in library/ai-agent-vs-chatbot showed [Sim](...) and [Chat interface](...) as literal Markdown. They now use plain text.
• Adds @mdx-js/mdx@3.1.1 to the root devDependencies. It is the version already in the lockfile, so the script no longer depends on a hoisted transitive package.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: CI audit

Testing

• bun run check:library-content passes on 80 posts in about 1s, and about 328 internal post links are validated.
• scripts/check-library-content.test.ts writes fixture posts to a temp dir and covers one failure mode per rule, with exact file lines. I removed each guard in turn (12 mutations) and every one turned the suite red.
• I copied a real post into the tree and corrupted it (canonical key, slug mismatch, missing ogImage, FAQ link, ## FAQ heading, retired/moved/typo links, an unclosed tag). The CLI reported all 9 problems with file:line and a fix hint, then the copy was removed.
• bun run lint, bun run check:audits (54 audits), and apps/sim bun run type-check all pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 1, 2026 6:09pm UTC

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Adds content validation script and refactors slug configuration.

The PR appears safe to merge; no outstanding findings remain.

Summary

The PR adds a content audit for frontmatter, MDX, assets, FAQs, links, and redirect targets.

• It shares retired-slug maps with the Next.js redirects and adds focused audit tests.
• The latest changes align draft, customer-story, author-profile, and reserved-route checks with the serving routes.

_{Reviews (2) · Last reviewed commit: "fix(content): tighten check:library-cont..."}

[cubic-dev-ai]

All reported issues were addressed across 7 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 7 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}