Validate and canonicalize generated toolkit routes

[jottakka]

Summary

• validate every generated toolkit slug before it becomes a route
• make integration cards, static parameters, and the sitemap share that contract
• sort and deduplicate generated routes deterministically

Test plan

• pnpm test

---

Note

Medium Risk
Changes affect SEO surfaces (sitemap, canonical paths) and which integration pages/routes exist; invalid catalog entries are dropped rather than linked, which is intentional but could hide data issues until tests fail.

Overview
Toolkit slugs are validated before they become URLs: getToolkitSlug can return null, rejects unsafe docsLink path segments (e.g. encoded slashes, __proto__), and only accepts slugs matching a safe pattern. Integration links, canonical paths, static params, and slug-based data lookup skip or error when no valid slug exists instead of emitting bad routes.

One shared route list drives the integrations index, static generation, and sitemap: listToolkitRoutes returns routes sorted by category then slug; the sitemap merges those toolkit URLs with authored page.mdx paths and deduplicates by URL.

Stricter index.json parsing rejects malformed toolkit index entries instead of casting loosely typed JSON.

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 18, 2026 12:49pm

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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