docs(cloudflare): Rework the guide for v11

[JPeer264]

DESCRIBE YOUR PR

closes SDK-1426

Updates the Cloudflare guide for the APIs v11 removes or changes. Hold until
v11 ships; every claim here is wrong on the v10 line.

• Remove the @sentry/cloudflare/nodejs_compat entrypoint, which no longer
  exists, from the guide, the Prisma page, the integrations table and the
  Vercel AI page, and delete its feature page
• Drop the _experimental Vite plugin options for buildTimeInstrumentation
  and autoInstrumentation, both on by default, and remove the experimental
  alert on the plugin page
• Import wrapRequestHandler from @sentry/cloudflare/request, the only
  entry that still exports it
• Delete the removed honoIntegration page
• Describe spans as streamed by default on the MCP pages and in
  troubleshooting, and keep the v10 opt-in as a separate case
• Drop the caveat that configured classes must be declared in the Worker
  entry, fixed by fix(cloudflare): Auto-instrument classes re-exported from the worker entry sentry-javascript#23282

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: 2026-09-16
• No deadline: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Sep 11, 2026 9:07am UTC
sentry-docs	Ready	Preview	Sep 11, 2026 9:07am UTC

[linear-code]

SDK-1426

[sentry]

Bug: The code example in pages.mdx under "Don't have access to onRequest?" is SvelteKit-specific and will cause runtime errors for generic Cloudflare Pages users.
_{Severity: HIGH}

Suggested Fix

Remove the SvelteKit-specific example from the generic Cloudflare Pages guide. Alternatively, clearly label this section as applicable only to SvelteKit users and provide a link to the relevant SvelteKit documentation. The current presentation is misleading and provides non-functional code for the guide's target audience.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/platforms/javascript/guides/cloudflare/features/pages.mdx#L83-L97

Potential issue: The documentation file `pages.mdx` includes a code example under the
"Don't have access to onRequest?" section that is specific to SvelteKit. It uses
patterns like a `handle` function and accesses `event.platform.env`, which are not
available in a standard Cloudflare Pages environment. This example is presented in the
generic Cloudflare Pages guide without any mention of its SvelteKit dependency. A user
following this guide for a non-SvelteKit project will copy code that fails at runtime
with a `TypeError` because the `event` object will be undefined.

_{Did we get this right? 👍 / 👎 to inform future reviews.}