hono-4 already runs on Node, Bun, Deno and Cloudflare through RUNTIME, the pattern #24598 now applies to the other libraries. Its suite asserts errors, route patterns and concurrent requests, but not incoming trace continuation, outgoing fetch spans or logs. Add those on all four runtimes.

Apps

• Base: hono-4

Add assertions

• Incoming trace continuation
• Outgoing fetch with sentry-trace and baggage
• Logs

Findings to confirm (runtime audit, September 2026, develop 6f2da7483d; database spans were measured with mysql or mysql2):

• Bun: everything measured worked.
• Deno: outgoing fetch: broken. deno: Outgoing fetch gets no span and no trace propagation #23891 has added outgoing fetch spans to @sentry/deno since.
• Cloudflare: everything measured worked.

Setups the audit ran: Bun, Deno, Cloudflare

Done when

• The three assertions pass on Node, Bun, Deno and Cloudflare, or this issue records why a runtime cannot meet one
• SDK defects the variants surface are fixed here, or split into their own issue when the fix is large or shared with other libraries