docs(redirects): add /api-reference/latest/* → current dated version

[riveign]

Summary

Adds a wildcard redirect from /api-reference/latest/:slug* to the latest stable dated API version (2026-02-18 today), and teaches scripts/generate-specs.mjs to derive that redirect from the live /versions endpoint on every generate run.

External consumers (merchant dashboard CTAs, support links, partner docs, ad-hoc bookmarks) can deep-link into the API reference using a stable, version-agnostic URL. On each future stable version cut, no docs.json hand-edit is needed — running pnpm generate picks up the new destination automatically.

Why a generator-derived redirect, not a hardcoded one?

The 24 dated nav entries in docs.json are already auto-generated from /versions. The redirect destination is the same kind of derived value, so it belongs in the generator alongside the nav. A hand-edit would have been a quiet drift risk: at the next version cut, the generator regenerates the nav, but the redirect would silently keep pointing at the old version unless someone remembered.

Changes

• docs.json — adds the redirect entry (also reproducible by running pnpm generate against current /versions).
• scripts/generate-specs.mjs — adds buildManagedRedirects(latestStableVersion), MANAGED_REDIRECT_SOURCES, and mergeRedirects(existing, latestStable). User-authored redirects (e.g. /guides/**) are preserved by source-key; only redirects in the managed set get re-derived. Wired into main() immediately after buildNavigation.

Test plan

• Mintlify preview deployment builds.
• https://<preview-url>/api-reference/latest/post-v1-merchants 301/302s to https://<preview-url>/api-reference/2026-02-18/post-v1-merchants (200).
• https://<preview-url>/api-reference/latest/get-v1-merchants redirects similarly.
• Existing /guides/** → /custodians/** redirect still works (regression check).
• Existing 2026-02-18/* direct URLs still resolve.
• pnpm generate on main after merge produces zero diff against the merged docs.json redirect block (deterministic).

Follow-up

Companion dashboard PR in pay-merchant-experience swaps the /merchants empty-state "Read the Docs" CTA to https://docs.walletconnect.com/api-reference/latest/post-v1-merchants (tracked under WCPM-385). That PR is held until this one is merged + deployed.

Notes

• mint dev does NOT process the redirects block locally. Verified existing /guides/** rule also 404s in dev. Verification only happens on the Mintlify hosted preview / production.
• Verified locally that pnpm generate against current /versions (stable=[2026-02-18]) produces a zero-diff docs.json vs. the prior commit on this branch — proving the generator output matches the hand-edited redirect.
• The next time the docs team runs pnpm generate for unrelated reasons, it will also pick up upstream OpenAPI spec drift in api/*.json. That drift was intentionally not included here (kept separate from the redirect prototype).

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
wc-pay-docs	🟢 Ready	View Preview	May 18, 2026, 1:27 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.