[laurelthorburn]

Old /apis/<name> links (and a couple of other stale URLs) render as 404s on
shopify.dev's checkout UI extensions reference. This repoints them to the current
/target-apis/... URLs. Link targets only, no prose or type changes.

Target branch: 2026-04 (this PR only) Links fixed: 27 Files: ui-extensions/src/surfaces/checkout/api/address-autocomplete/standard.ts, ui-extensions/src/surfaces/checkout/api/checkout/checkout.ts, ui-extensions/src/surfaces/checkout/api/standard/standard.ts, ui-extensions/src/surfaces/checkout/preact/api.ts
Sibling PRs for the other versions: #4797 (2026-10), #4798 (2027-01-rc), #4799 (2026-07), #4801 (2026-01), #4802 (2025-10), #4803 (2025-07), #4804 (2026-10-rc), #4805 (unstable)
Unresolved: none

Anchors are rewritten to the new #docsstandard<api>api-propertydetail-<prop> ids, and #examples becomes #use-cases. The metafields property is no longer documented on this version, so that link goes to metafields-api#properties. Versionless links in address-autocomplete/standard.ts and preact/api.ts now use {API_VERSION}, like the rest of the surface. I checked each new URL on shopify.dev: every page loads, and every fragment exists as an element id on that version's page.

Generated docs: I changed only the links in the committed JSON. Each file is the base branch version with the same link rewrite as the source. A full rebuild on this branch also picks up large unrelated docs changes (source changes that were never regenerated). I did not include those, so this PR does not republish them. They need a separate, owner-reviewed regeneration.

Context: shopify.dev link audit for the checkout and customer account UI extensions
references. The shop/world side (MDX links and redirects) is handled in a separate
shopify-dev PR.

🤖 Generated with Claude Code

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.