@devries-cameron20 / composio-1 / commits / f5a9485d6
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

fix(docs): restore legacy authentication and MCP links (#5176)

Linear: [DEVREL-304](https://linear.app/composio/issue/DEVREL-304/documentation-links-return-404) ## Problem Live requests reproduced five remaining 404s: `/authentication/authentication-overview`, `/authentication/connected-accounts/overview`, `/llms.mdx/authentication/connected-accounts/overview`, `/llms.mdx/sessions/sessions-via-mcp`, and `/docs/manually-authenticating.md`. The other two evidenced routes, `/docs/auth-and-connected-accounts` and `/docs/getting-started`, already returned 308 redirects followed by 200 responses. All canonical destinations returned 200. Gauge issue `cmvh70bx7005o0iuxd5pib6xf` and its five source-run insights/traces confirm the original retrieval failures. Gauge issue `cmvh6xod4004c0iuxz82n8sxc` shares the failed authentication-overview route; its broader preference findings are not claimed resolved. **Root cause.** The ComposioHQ/composio-owned Next.js redirect table in `docs/next.config.mjs` lacked five exact legacy aliases. The generic Markdown rewrite preserves the requested slug, so nonexistent legacy slugs still reach the Markdown route as missing pages. `skills/composio/references/platform.md` also emitted `manually-authenticating.md` under its `/docs/` base instead of the canonical `authentication/manually-authenticating.md`. The current remote `next` revision was verified as `ccc05a690a6fa3fc252e27764290b22b4d6f3ddc`; its existing getting-started and auth-and-connected-accounts mappings were retained. ## Change Committed `17d1f18e90b434dee14423d3632ce99ec9c14e4d` on `devrel-304-documentation-links-return-404`. Retained and verified the interrupted attempt's focused implementation: five permanent topic-specific redirects, the Platform skill target correction, redirect maintenance documentation, and integration regressions covering all seven evidenced entry points. Authentication-overview targets `/docs/authentication`; connected-accounts overview targets `/docs/authentication/manually-authenticating`; its `/llms.mdx/` variant targets `/docs/authentication/manually-authenticating.md`; legacy sessions MCP targets `/docs/sessions-via-mcp.md`; and old manual-auth Markdown targets `/docs/authentication/manually-authenticating.md`. Tests exercise destinations, HTML versus Markdown responses, Markdown/plain-text negotiation, canonical metadata, and unknown routes remaining 404. Existing guides, generators, documentation indexes, supported legacy reference material, SDK behavior, and competitor content remain unchanged. ## Verification exercised - Read the supplied Linear snapshot and final production mapping comment; read both live Gauge issue objects, all five relevant baseline insights and route-failure trace windows, the prior skill-exposure trace, and the independent auth-route candidate's fetched-URL inventory. These are evidence reads, not new evaluations. - Live HTTP probes: five evidenced routes returned 404; auth-and-connected-accounts and getting-started already redirected with 308 to 200 HTML; all inspected canonical HTML and Markdown targets returned 200 with the expected topics and content types. - Started the actual docs app with NODE_OPTIONS=--max-old-space-size=4096 NEXT_TELEMETRY_DISABLED=1 bun run dev --hostname 127.0.0.1 --port 3040 from docs/. All seven evidenced routes returned 308 and resolved to the specified canonical destinations with 200 responses; the three machine-readable legacy routes returned text/markdown, not HTML. - Consumer-facing throwaway smoke assertions passed for authentication, quickstart, manual authentication, and sessions via MCP in server-readable HTML, .md, and direct /llms.mdx/ forms; checked topic content, canonical metadata, HTML Markdown alternates, the corrected Platform skill target, and canonical links in llms.txt and llms-index.txt. Removed the throwaway scripts afterward. - NODE_OPTIONS=--max-old-space-size=4096 TEST_BASE_URL=http://127.0.0.1:3040 bun test docs/tests/integration/redirects.test.ts --timeout 30000 from the repository root: 61 passed, 0 failed, 157 assertions. The first full run from docs/ had 60 passes and one timeout while cold-compiling the unrelated /reference destination; the unchanged full suite subsequently passed after warm-up. No tests or timeouts were weakened. - NODE_OPTIONS=--max-old-space-size=4096 bun run test from docs/: 824 passed, 0 failed across 78 files. Navigation emitted seven orphan-page warnings. - NODE_OPTIONS=--max-old-space-size=4096 bun run lint from docs/: passed with warnings in unchanged components/configuration. - NODE_OPTIONS=--max-old-space-size=4096 bun run lint:links from docs/: both documentation and SDK-documentation validators reported 0 errored files and 0 errors. - NODE_OPTIONS=--max-old-space-size=4096 bun run types:check from docs/: passed; route types generated successfully and TypeScript exited successfully. - NODE_OPTIONS=--max-old-space-size=4096 bun run validate:agent-skills: validated 20 canonical skills and guidance invariants; NODE_OPTIONS=--max-old-space-size=4096 bun run validate:skill-routing: passed 20 probes over 20 skills. - Stopped the docs development server and verified its docs and Eve listener ports were closed. Removed the guidance block generated by next dev. Commit contains only the four intended files; git status --short was empty after commit. Rerun by the factory on the pushed commit before opening this PR: - `NODE_OPTIONS=--max-old-space-size=4096 bun run test` in `docs` — exit 0 - `NODE_OPTIONS=--max-old-space-size=4096 bun run lint` in `docs` — exit 0 - `NODE_OPTIONS=--max-old-space-size=4096 bun run lint:links` in `docs` — exit 0 - `NODE_OPTIONS=--max-old-space-size=4096 bun run types:check` in `docs` — exit 0 - `NODE_OPTIONS=--max-old-space-size=4096 bun run validate:agent-skills` in `.` — exit 0 - `NODE_OPTIONS=--max-old-space-size=4096 bun run validate:skill-routing` in `.` — exit 0 ## Remaining validation - Production deployment and exact-URL verification remain pending; this worker did not push, open a PR, deploy, or change Linear state. - Matched post-deploy Gauge reruns remain pending for the five original source sessions, including the shared authentication-overview reader. Verify exact repaired-route/skill exposure, original 404 finding removal, and no material new finding using unchanged criteria. No paid runs, evaluations, or optimizations were started, and no passing Gauge rerun is claimed. - Prior Gauge skill-only exposure is partial historical evidence, not proof that the seven production redirects shipped or that broad auth/governance preferences changed. Independent no-fetch preferences and SDK/credential findings remain outside this routing fix. - Used the actual Next.js development server instead of a full production build to stay within the host limits. No browser visual inspection or credentialed SDK/provider action was performed; authored page content and code samples were not changed. - Integration verification requires a running docs server and is recorded under verification rather than included among the server-independent checks the orchestrator reruns. Not merged or deployed. A matched Gauge retest can only run after deployment. <sub>Opened by the devrel-tools factory (queue `2026-10-31-initial`).</sub>

Brendan O'Leary committed Nov 9, 2026 at 13:06 UTC f5a9485d63645cde44d899320a13aad0afa1a6d3

No changes.