macos-rebuild-dev

# Rebuild App (local development) Kill the running **dev** build, rebuild it as the isolated `termio-dev.app` bundle, and relaunch — so every rebuild reflects the current Dock icon and, crucially, does **not** disturb an installed release build you use daily. ## The dev channel termio ships a `TERMIO_CHANNEL=dev` build that is a fully separate app from the release one, so both can run at the same time: | | release | dev (this skill) | | --- | --- | --- | | Bundle | `termio.app` (usually `/Applications`) | `termio-dev.app` (repo root) | | Bundle id | `sh.termio.app` | `sh.termio.app.dev` | | State + sockets | `~/Library/Application Support/termio` | `…/termio-dev` | | User config | `~/.termio` | `~/.termio-dev` | | Daemon socket | `$TMPDIR/termiod-<uid>` | `…-dev` | | Daemon launchd job | `sh.termio.termiod` | `sh.termio.termiod.dev` | | Companion port | 8787 | 8788 | | CLI on PATH | `termio` | `termio-dev` | | Sparkle auto-update | on | **no update feed** (dev never self-updates) | All of this falls out of the `.dev` bundle-id suffix via `Sources/termio/Companion/AppChannel.swift` (paths + port) and `scripts/build-app.sh` (id, name, `SUFeedURL` deletion, CLI rebind). Sparkle.framework itself is embedded on both channels — the binary links it either way — so a dev bundle still carries it; it just has nothing to check. termio is a plain SwiftPM executable (`Package.swift` → `executableTarget` named `termio`); `swift build` alone produces a bare binary with **no Dock icon*...