[andrescera]

Affected repo & language: modem-stack; Bun workspace toolchain and TypeScript declarations.

What

Move the workspace runtime, CI/release inputs and current toolchain documentation from Bun 1.4.2 to 1.4.3. Move the exact @types/bun pin from 1.4.1 to 1.4.3 and regenerate only its lockfile subtree. The cross-compile verification comment now reflects the successful 1.4.3 build smoke.

Why

Adopt the requested Bun patch release consistently across local development and CI. This supersedes the Bun-typing bump in dependabot #27; that PR is left untouched. Package versions, published source, Debian recipes and the frozen APT closure are unchanged.

How to verify

From the repository root, run bun install --frozen-lockfile, bun run lint, bun run typecheck, bun test, bun run --cwd control verify:consumers, and bash cli/smoke/build-binaries.sh. Keep Node 26 on PATH for the standalone Node consumer.

All six commands exited 0 under both Bun 1.4.2 and 1.4.3 on the same change based on 7254c595. Each test run passed 1,492 tests across 129 files with 0 failures and 0 skips. Each consumer run exercised all seven exports under Node 26.10.0 and Bun; each compile run emitted CLI and harness ELFs for amd64 and arm64. Independent lock regeneration under both runtimes produced identical files with only the workspace typing specifier, @types/bun, and bun-types entries changed.

Risks

Cross-compilation proves ELF production, not execution on an arm64 board. No Docker, board, release or deployment validation was performed. The existing Biome 2.5.10 CLI versus 2.5.9 schema informational diagnostic appears under both runtimes and is outside this pin-only change. LSP is unavailable for JSON/YAML/docs/lock pins on this host; the shell script has clean LSP diagnostics and the executable lint/typecheck gates passed. Revert the pin commit to roll back.

---

Checklist

• Current toolchain README and routed docs updated; no structure or runtime-feature change
• No user-visible feature change; no user-site copy affected
• Started from fetched canonical main in a private worktree
• No tracked references to local scratch paths or sibling dependencies added
• Dual-runtime local gates passed; hosted checks recorded separately