feat: patch Cloudflare browser engine support

[onmax]

Summary

• patch @vite-hub/browser 0.0.3 with the upstream Cloudflare engine support from feat(browser): default Cloudflare to Kitesurf vitehub#915
• pin @cloudflare/playwright 1.3.5 so Kitesurf is available to Browser Definitions on Cloudflare
• keep Drop’s existing Ray.so renderer and public API unchanged
• select Chromium for Drop’s Ray definition because Ray.so currently does not hydrate in Kitesurf

Verification

• pnpm typecheck
• generated Worker contains the patched Kitesurf provider and the explicit Chromium runtime selection
• deployed end-to-end flow against https://vitehub-drop-preview.maximogarciamtnez.workers.dev
• both Cloudflare Workers Builds checks pass

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	vitehub-drop	ab2635b	Aug 19 2026, 11:33 AM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	vitehub-drop-preview	ab2635b	Aug 19 2026, 11:33 AM

[onmax]

Kitesurf reproduction

1. Open the Kitesurf playground.
2. Load https://ray.so/.
3. Click Export Image to export a PNG.
4. Ray remains stuck on Exporting PNG.
5. The console reports a Kitesurf engine panic:

called `Option::unwrap()` on a `None` value
blitz_dom::net::collect_font_faces

This reproduces from a clean Ray.so load and persisted across reloads. The DROP integration is available in commit aeccfaf; the current PR head temporarily selects Chromium because Kitesurf cannot complete the PNG export.