chore(mise): declare bun 1.4.0 and node 24 as text, pin CI to the same

[developerz-ai]

What

• Add mise.toml with [tools] bun = "1.4.0" and node = "24", paired copy
  note pointing at .github/workflows/ci.yml.
• Pin ci.yml oven-sh/setup-bun to bun-version: "1.4.0".
• Add actions/setup-node@v4 with node-version: "24" before the install step
  so the chromium-install script's node resolves on bare runners, not just
  ubuntu-latest.

Acceptance

• mise.toml exists at the repo root with a [tools] section declaring bun = "1.4.0" and node = "24", and a comment naming .github/workflows/ci.yml as the paired copy.
• .github/workflows/ci.yml pins oven-sh/setup-bun to bun-version: "1.4.0" (no longer "latest").
• .github/workflows/ci.yml contains an actions/setup-node step with node-version: "24" placed BEFORE the "install" (bun install) step.
• No change to bin/setup, bin/check, package.json, or anything under src/ (verified by git status showing only the two declared paths).
• bun run lint, bun run typecheck and bun test all pass locally against the pinned versions (full gate, run by the harness after the editor finishes).

Changes

• mise.toml (create) — Create the file at the repo root with [tools] bun = "1.4.0" and node = "24", and a comment naming .github/workflows/ci.yml as the paired copy so future edits change both in lockstep. Format: TOML, the filename and section the brief specifies.
• .github/workflows/ci.yml (edit) — Pin oven-sh/setup-bun bun-version from "latest" to "1.4.0", and insert a uses: actions/setup-node@v4 step with node-version: "24" placed BEFORE the "install" step (between checkout and bun install). Keep every other step, comment, env, timeout and cache key unchanged.

Verification

./bin/check passed (exit 0) in 23s.

---

🤖 Opened by developerz.ai for task tsk_1a734bc528ba4836bfc0a1eb2ade6a64 on developerz-ai/ui-debugger-mcp.

Raised automatically by the issue-triage lane, from a GitHub issue on this repository.

Closes #85

🤖 developerz.ai maintainer bot — this PR was opened by a developerz.ai fleet run.
Dispatched automatically by the issue-triage lane
Model MiniMax-M3 on router.ai.developerz.ai via native, funded by box_env
Ran on box sebby-ovh-3
Cost unknown: no list price on record for MiniMax-M3 on router.ai.developerz.ai
Run timeline run_d73bcfa42907473a9551b85a7bf4c487

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: d824b575-2ccf-46df-90fd-9b70abd1c9f2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[developerz-ai]

✅ Reviewed — nothing blocking

0 actionable comment(s) · grounded on your code

_{⚠️ 1 config note(s): test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against}

_{⏱ 20s wall clock · MiniMax-M2 via minimax · 5 model call(s) · 2,951 output token(s) · 83 tok/s observed (slowest call 8s)}

_{🤖 developerz.ai — automated review, running on your model and your box.}

[developerz-ai]

Review summary — 2 file(s), 0 finding(s).

Add mise.toml with bun 1.4.0 and node 24, pin CI to same versions. Clean implementation that meets all acceptance criteria.

Config notes

• test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against

---

🤖 developerz.ai review — automated, running on your model and your box. What is this?
Reviewed by minimax/MiniMax-M2 on box sebby-ovh-3 — 64.4k in / 2.95k out over 5 calls, ~$0.02 on your key (estimate: list price x reported tokens).