docs: convert bold cross-references into links, link SEP and RFC mentions#3017
Conversation
…ions The book's bold chapter names were placeholder cross-references from the initial rewrite. Convert the genuine chapter pointers into bold-wrapped page-relative links (**[Title](path.md)**); bold that names a concept, UI tab, or the page's own topic stays plain. Also link external references: SEP-N mentions point at the spec-repo proposal (issue or PR, whichever the number canonically is), RFCs point at their datatracker pages, and the few unlinked third-party deps on the installation page get their PyPI links. Existing SEP links that relied on GitHub's issue-to-PR redirect now use the canonical URL.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 33 files
Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more
Re-trigger cubic
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — docs-only mechanical link substitutions; all internal link targets exist and the SEP/RFC URLs match the canonical forms already used elsewhere in the docs.
Extended reasoning...
Overview
This PR touches 33 Markdown files under docs/ only, converting bold chapter cross-references into bold-wrapped relative Markdown links, linking SEP mentions to their spec-repo issue/PR, linking RFC mentions to datatracker pages, and adding PyPI links for three dependencies on the installation page. There are no changes to source code, examples, tested snippets (docs_src/), or configuration.
Security risks
None. The changes are documentation hyperlinks. The added external URLs point to well-known canonical destinations (github.com/modelcontextprotocol, datatracker.ietf.org, pypi.org) consistent with existing links in the same files; no scripts, redirects, or untrusted domains are introduced.
Level of scrutiny
Low. The diff is purely mechanical single-line substitutions with no prose rewording. I verified that every relative link target referenced in the diff (e.g. multi-round-trip.md, ../tutorial/logging.md, ../run/index.md, ../advanced/low-level-server.md) corresponds to an existing file in docs/, and the relative path direction (tutorial → ../advanced, advanced → ../tutorial, etc.) is correct in each case I checked. mkdocs build --strict (reported green by the author) would also fail on any broken internal link. SEP-number-to-issue/PR mapping matches the conventions already established by pre-existing links in these files (e.g. SEP-2577 → pull/2577, SEP-990 → issues/990).
Other factors
The bug-hunting system found no issues, and the PR timeline has no outstanding reviewer comments. The only stated leftover (the unlinked Advanced User Guide reference in docs/tutorial/index.md) is explicitly out of scope and untouched. Risk of regression is negligible.
Same policy as the previous commit, applied to the newly added MCP Apps, Extensions, and Dependencies chapters and the new migration/elicitation sections: chapter cross-references in the Dependencies and Elicitation pages become bold-wrapped links, and SEP-2133 mentions link to the proposal PR (prose first-mention and the migration section heading).
There was a problem hiding this comment.
LGTM — docs-only change converting bold cross-references into relative links and linking RFC/SEP mentions; all link targets exist.
Extended reasoning...
Overview
This PR touches only Markdown files under docs/ (35 files). Every change is a single-line substitution that wraps an existing bold cross-reference in a Markdown link (e.g. **Multi-round-trip requests** → **[Multi-round-trip requests](../advanced/multi-round-trip.md)**), links RFC mentions to their datatracker pages, links SEP mentions to the canonical issue/PR in the spec repo, and adds PyPI links for three dependencies on the installation page. No prose is reworded and no code, examples, or configuration is modified.
Security risks
None. The change introduces no executable code and only adds hyperlinks to well-known destinations (datatracker.ietf.org, github.com/modelcontextprotocol, pypi.org) and page-relative doc paths. There is no surface for injection, auth, or data-exposure issues.
Level of scrutiny
Low. This is a mechanical documentation cleanup with no behavioral impact. I verified that every internal link target file referenced in the diff exists in the repository, and the relative paths (../advanced/..., ../tutorial/..., same-directory links) are consistent with the directory layout. The author also reports mkdocs build --strict passing, which would catch broken internal links.
Other factors
The bug-hunting system found no issues, and there are no outstanding reviewer comments on the PR. The RFC numbers linked match the surrounding text (7662, 9728, 8693, 7523, 8414, 6570, 7591, 9207, 6749, 3986, 5424), and SEP link targets follow the convention already established by pre-existing links in these files (e.g. SEP-2577 → pull/2577, SEP-990 → issues/990).
2 participants
The book's bold chapter names (Multi-round-trip requests, The Context, ...) were placeholder cross-references from the docs rewrite (#2978), deliberately left unlinked and listed there as a follow-up. This converts the genuine chapter pointers into real links and makes external references clickable.
What changed (33 files, 158 lines — all single-line link substitutions, no prose rewording):
**[Multi-round-trip requests](../advanced/multi-round-trip.md)**. Bold that names a concept rather than a chapter (the tools/resources/prompts primitives, Inspector tab names, a page's own topic) stays plain bold — judged per occurrence, leaning toward under-linking over mislinking.Verification:
mkdocs build --strictgreen, markdownlint/pre-commit pass,tests/docs_src/unaffected (562 passed). Every added internal link was checked against the destination page's H1, and every SEP link target was verified against the actual issue/PR title via the GitHub API.One known leftover, deliberately untouched:
docs/tutorial/index.mdreferences an Advanced User Guide chapter that doesn't exist under any name (the advanced section has no index page) — fixing that needs a wording decision, not a link.AI Disclaimer