[Help wanted] Investigate Bun + Deno compatibility for npx @nhonh/react-debugger mcp bridge

[hoainho]

🌟 Before claiming this issue

Two quick steps before you open a PR:

1. ⭐ Star the repository — low-friction signal that you'll follow through
2. 💬 Comment I'll take this (or similar) below — prevents two contributors racing on the same issue

Full policy: CONTRIBUTING.md → How to claim. If a claim is older than 7 days with no PR, you can reclaim it politely.

---

Context

The MCP bridge process (built in openspec/changes/mcp-server-v1/specs/mcp-bridge/spec.md) currently targets Node 18 or newer per cli/package.json. Bun and Deno are gaining adoption and may run the bridge with minimal changes — or may reveal API gaps worth fixing.

Where to look

• File: cli/package.json and cli/bin/cli.js
• File: cli/src/mcp.ts (the bridge implementation)
• Bun: https://bun.sh/docs/runtime/nodejs-apis
• Deno: https://docs.deno.com/runtime/manual/node/compatibility

Expected outcome

• Document in cli/docs/RUNTIME_COMPATIBILITY.md the outcome for each runtime
• For each runtime: pass / fail / pass-with-flags plus the exact command tried
• If pass: add the recommendation to cli/docs/MCP_USAGE.md
• If fail: open a follow-up issue with the specific API gap

Estimated effort

M (3 to 6h)

How to claim

Comment "@hoainho I will take this" to claim. PR within 10 days or unclaimed.

Acceptance criteria

• cli/docs/RUNTIME_COMPATIBILITY.md exists with Node, Bun, Deno columns
• At least one tool call (get_fiber_node) succeeds end-to-end via the bridge on whichever runtimes pass
• No changes to cli/package.json engines field unless explicitly opening compatibility