Add a per-version compatibility page to the API reference

[cb1kenobi]

Adds a Compatibility link beside "Release notes" on every Titanium API entry page (/docs/sdk, /docs/sdk/13.4.0, ...), pointing at a generated /docs/sdk/<version>/compatibility.

Closes TI-94.

Why

/docs/reference/compatibility (TI-75) already generates this data, but across every release at once. That is the right shape for "when did Java 17 become the floor" and the wrong one for a reader already standing on /docs/sdk/13.4.0 — they picked a release and want its column. Until now the reference linked to the compatibility data not at all.

tidev/titanium-docs#269 is the argument for generating it rather than writing it: that PR hand-patched the legacy matrix to say Android API 36 for 13.4.0+, a fact registry/sdk/13.4.0/toolchain.json already recorded. Every number the old matrix carries by hand is captured per release by scripts/capture-toolchain.ts.

What the page shows

Per release, read out of its own toolchain.json:

Section	Rows
Your machine	Node.js, Titanium CLI
Android	Java, Android SDK, build tools, platform tools, tools, NDK
iOS	Xcode, iOS SDK
What it builds for	min Android API, compiles against API, min iOS, min watchOS

Ranges are printed as the SDK declares them, which is the string ti info prints beside "Supported:". ti info is offered at the top of the page, ahead of the tables: it reads the same declarations and reports them against the machine the reader is actually sitting at.

Notes on the shape

• Nothing restates a range. compat.ts turns one toolchain.json into rows, and minimumCli decides the CLI floor for this page and the cross-release one alike. The generated partials are byte-identical (pnpm docs:compat:check passes untouched).
• Three sections, not one table. The old matrix ran Node, Java, Xcode and the Android SDK down a single column, which reads as one checklist when it is really three — a Linux reader has no Xcode to compare against. An empty section is dropped rather than rendering a heading over nothing.
• Java leads the Android section rather than trailing it, where the SDK's own package.json authoring order would put it.
• An unknown vendor key still gets a row. ToolchainSchema keeps vendor loose because the key set is the SDK's to change; a release adding a component appears rather than vanishing until someone edits a list.
• Every compiled version has a capture, main included, so the pages prerender with dynamicParams = false and the link is unconditional where the release-notes link is gated.
• Served but not indexed outside the reference's own cutoff (isIndexedVersion): twenty near-identical tables are twenty ways to land on the wrong one. The sitemap lists only the indexed set, so it cannot contradict the page's own noindex.

Wiring

links.ts resolves the new segment (so a post or guide linking to it is checked rather than reported dead), sitemap.ts lists the indexed ones, and ia.test.ts now holds both release-notes and compatibility reserved against type names.

Checks

pnpm check, pnpm lint, pnpm test (638 pass), pnpm check:docs, pnpm check:em-dash, pnpm docs:compat:check all pass. Pages verified rendering at 13.4.1, 13.4.0, 12.5.0 and main; uncaptured versions 404.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
titaniumsdk.com	Ready	Preview	Sep 17, 2026 4:12pm UTC