Wire the docs → cockpit handoff for deep-agents and runtimes - #938
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 1, 2026 22:30
blove
force-pushed
the
blove/deep-agents-reverse-links
branch
from
September 1, 2026 22:32
15d7bf4 to
fc6056b
Compare
Contributor
blove
force-pushed
the
blove/deep-agents-reverse-links
branch
from
September 1, 2026 22:38
fc6056b to
8e9441b
Compare
Contributor
…untimes The cockpit -> docs direction shipped with both libraries (COCKPIT_DOCS_LINKS covers all six deep-agents entries and all four runtimes entries), but the reverse table only knew the five first-iteration pages. Every deep-agents page (#937) and every runtimes page (#913) sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes. Add the 16 missing entries: - deep-agents: the five capability pages map to their core-capabilities topic; the introduction maps to deep-agents/getting-started/overview. - runtimes: all three pages of each runtime section (overview, quickstart, how-it-connects) map to that runtime's one demo, since a single demo serves them equally well; the introduction maps to runtimes/getting-started/overview. Also add deep-agents and runtimes to AnalyticsLibrary. Without it every handoff from these two libraries would have been attributed to 'unknown', so the new links would be invisible in the funnel they exist to feed. Each of the ten destination URLs was checked against production and returns a hard 200. The check discriminates: an unknown topic 307s to the fallback and an unknown product 500s, so the 200s are real pages rather than SPA soft-200s. Tests: the exact pin is updated, plus four guards — every key names a page that exists in docs-config (a typo'd key is otherwise invisible: the page just keeps the Cockpit-home fallback), the deep-agents/runtimes links round-trip against COCKPIT_DOCS_LINKS, the analytics library is no longer 'unknown', and each runtime section's three pages resolve to the same demo. All four were mutation-tested to confirm they fail when the mapping is wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
force-pushed
the
blove/deep-agents-reverse-links
branch
from
September 1, 2026 22:43
8e9441b to
91488ee
Compare
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #937 (deep-agents docs) and #913 (runtimes docs).
The cockpit → docs direction was already wired for both libraries:
COCKPIT_DOCS_LINKScovers all six deep-agents entries and all four runtimes entries, so every one of those demos has a working "Read docs" button. The reverse table,docsCockpitMappings, still only knew the five first-iteration pages — so every deep-agents and runtimes docs page sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes.Runtimes lacked reverse links too, so they are fixed here in the same PR.
The 16 new entries
deep-agents/getting-started/introductiondeep-agents/getting-started/overviewdeep-agents/capabilities/{planning,filesystem,subagents,memory,skills}deep-agents/core-capabilities/<topic>runtimes/getting-started/introductionruntimes/getting-started/overviewruntimes/{aws-strands,microsoft-agent-framework,mastra}/{overview,quickstart,how-it-connects}runtimes/core-capabilities/<runtime>Two judgment calls worth a look:
overviewwould leave two-thirds of the runtimes library on the Cockpit-home fallback.introductionpages map to their product'sgetting-started/overview. Those manifest entries areentryKind: 'docs-only', so Run mode lands on the product's Cockpit overview rather than a live demo — still a better destination than Cockpit home, and it keeps the Capability row truthful. This is the exact inverse of whatCOCKPIT_DOCS_LINKSalready does.Analytics
AnalyticsLibrarydid not includedeep-agentsorruntimes, so every handoff from these two libraries would have been logged aslibrary: 'unknown'— the new links would have been invisible in the funnel they exist to feed. Both are added to the type and totoAnalyticsLibrary.Verification
Production URLs — all ten destinations return a hard
200. The check discriminates rather than rubber-stamping: an unknown topic307s to the fallback, an unknown product500s, and an unknown language307s, so these are real pages and not SPA soft-200s.Render check (website dev server, accessibility tree):
/docs/deep-agents/capabilities/planning→…/deep-agents/core-capabilities/planning/overview/python?mode=run|code|api/docs/runtimes/mastra/quickstart→…/runtimes/core-capabilities/mastra/overview/python?mode=run/docs/deep-agents/getting-started/introduction→…/deep-agents/getting-started/overview/overview/python?mode=run/docs/chat/guides/theming(still unmapped, negative control) →…/?mode=runThe negative control is what proves the mapping is driving the difference. The rendered result is identical in shape to an already-mapped page (
/docs/langgraph/guides/streaming). No console errors.Tests — the exact pin is updated, plus four new guards:
docs-config(a typo'd key is otherwise invisible — the page silently keeps the Cockpit-home fallback);COCKPIT_DOCS_LINKS, so the two tables in two packages cannot drift apart;deep-agents/runtimesrather thanunknown;All four were mutation-tested — a typo'd key, a wrong topic, a dropped allowlist case, and a deleted entry each fail the suite.
nx test website: 59 files, 452 tests passing.nx lint website: 0 errors (27 pre-existing warnings). No lockfile changes.🤖 Generated with Claude Code