fix(docs): redirect legacy instrumentation pages

[dalaoyang]

What changed

• Add a permanent redirect from /docs/sdk/python/instrumentation to the current SDK instrumentation page.
• Add a permanent redirect from /docs/opentelemetry/introduction to the current native OpenTelemetry integration page.
• Keep both entries in a new dated, append-only redirect group so Next.js and the Cloudflare redirect generator share the same configuration.

Why

Both legacy URLs currently return 404 responses even though their canonical replacement pages exist. Exact redirects preserve old external links without changing current routes or adding broad wildcard behavior.

Closes #3222
Closes #3167

Validation

• Direct permanentRedirects export assertion: 2 passed
• pnpm run format:check: All matched files use Prettier code style!
• node scripts/generate-cloudflare-redirects.js: generated 538 redirects
• Generated _redirects output contains both source/destination mappings

The full Next.js build was not run locally, following the repository guidance for small redirect-only changes. CI will run the build and link checks on the declared Node.js 22 environment.

Greptile Summary

This PR adds two permanent redirects in lib/redirects.js to fix 404 responses on legacy documentation URLs that were previously live but lost their mappings during restructuring. The changes follow the established append-only, dated-group convention already used throughout the file.

• Adds /docs/sdk/python/instrumentation → /docs/observability/sdk/instrumentation, consistent with the adjacent sibling redirects at lines 753–757 that cover other /docs/sdk/python/* sub-paths but previously missed the instrumentation leaf.
• Adds /docs/opentelemetry/introduction → /integrations/native/opentelemetry, consistent with the existing /docs/opentelemetry/get-started and /docs/integrations/opentelemetry redirects pointing to the same destination.

Confidence Score: 5/5

Two minimal, targeted redirect entries that fill known 404 gaps; no existing routes or logic are altered.

Both source paths are absent from all other redirect arrays in the file, so there is no risk of redirect loops or duplicate-source conflicts. The destination paths are already used as redirect targets elsewhere in the file, confirming they are live pages. The change strictly follows the established dated-group pattern and does not touch any other logic.

No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["/docs/sdk/python/instrumentation\n(legacy, 404)"] -->|301 Permanent Redirect| B["/docs/observability/sdk/instrumentation\n(current page)"]
    C["/docs/opentelemetry/introduction\n(legacy, 404)"] -->|301 Permanent Redirect| D["/integrations/native/opentelemetry\n(current page)"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["/docs/sdk/python/instrumentation\n(legacy, 404)"] -->|301 Permanent Redirect| B["/docs/observability/sdk/instrumentation\n(current page)"]
    C["/docs/opentelemetry/introduction\n(legacy, 404)"] -->|301 Permanent Redirect| D["/integrations/native/opentelemetry\n(current page)"]

Loading

_{Reviews (1): Last reviewed commit: "fix(docs): redirect legacy instrumentati..." | Re-trigger Greptile}

[vercel]

@dalaoyang is attempting to deploy a commit to the langfuse Team on Vercel.

A member of the Team first needs to authorize it.

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.