Feature request: Add RTK equivalents for bun/bunx commands

Summary

rtk discover flagged a large number of unhandled bun/bunx commands that could benefit from RTK equivalents. These are the most-missed savings opportunities after the already-handled npm/npx commands.

Top unhandled bun commands (last 30 days)

Command	Count	Example
bunx tsc	588	bunx tsc --noEmit > /tmp/...
bun run	524	bun run lib/render.cjs ...
bun install	98	bun install 2>&1
bunx oxlint	74	bunx oxlint --deny-warnings 2>&1
bun x	73	bun x oxfmt src/...
bunx oxfmt	65	bunx oxfmt . 2>&1
bun test	40	bun test src/...
bunx	36	bunx @expo/fingerprint . 2>&1
bun add	32	bun add sharp 2>&1

Suggested mappings

RTK already handles the npm/npx equivalents:

• npm run → rtk npm
• npx tsc → rtk tsc
• npx jest → rtk jest

Similar mappings for bun would be straightforward:

• bun run → rtk bun (or reuse rtk npm)
• bunx tsc → rtk tsc (same tool, different runner)
• bun test → rtk jest / rtk bun test
• bun install / bun add → rtk bun
• bunx → rtk bunx or fold into rtk npx

Impact

Based on the discover output, these commands represent a significant portion of unhandled sessions. Adding bun support would extend RTK's token savings to projects using Bun as their JS runtime/package manager.

Environment

• Reported via rtk discover
• macOS (darwin)