Studio firmware (v2.5.0): hardware test + release

[rdlu]

Tracking the remaining steps to ship DYA Studio support as v2.5.0. All code is done and build-verified on PR #28 (feat/dya-studio); only the on-hardware test + release remain.

Status

• ✅ PR feat(dya): DYA Studio support (USB + BLE keymap editing) → v2.5.0 #28 open — cormoran ZMK fork + 5 modules, board→shield migration, encoder → runtime-sensor-rotate, mise run studio (bun + bun audit + Chromium app window).
• ✅ Both halves + reset build clean locally (left 401 KB/50.6%, right 270 KB/34.2%); left has CONFIG_ZMK_BLE_MANAGEMENT_STUDIO_RPC=y (BLE editing), right is a clean peripheral.
• ⏳ CI build dispatched on the branch (check PR feat(dya): DYA Studio support (USB + BLE keymap editing) → v2.5.0 #28 → Actions).
• ⏳ Not merged — waiting on hardware verification.

1. Hardware test

mise run flash-reset    # LEFT first — clears the old ZMK Studio overlay + BT bonds
mise run build-flash    # flash both halves; they re-pair over BT
mise run studio         # opens DYA Studio as a Chromium app window (localhost:5173)

• Keymap loads + an edit persists over USB (WebSerial)
• Disconnect USB → connect over Bluetooth; edit persists over BLE (the headline feature)
• Encoder works (volume default; try live-reconfiguring it in the app)
• Smoke-test: all 8 layers, pointing/trackball, RGB, gaming layers
• Rollback if needed: mise run flash-release (reflashes v2.0.0)

2. Release v2.5.0 (only if the test passes)

• Merge PR feat(dya): DYA Studio support (USB + BLE keymap editing) → v2.5.0 #28 → main
• Wait for the [Draw] auto-commit on main, then git pull --ff-only
• Annotated tag v2.5.0 on the [Draw] commit; push
• Notes-only GitHub release for v2.5.0, marked latest

Notes / gotchas

• bun audit flags 32 advisories (1 critical/16 high/13 moderate/2 low) — all in dya-studio's dev/build deps (vite/jest/eslint: picomatch ReDoS, js-yaml DoS). Upstream's to fix; not in the runtime app.
• DYA Studio needs cormoran's fork (v0.3 base) — no Zephyr 4.1 / HWMv2 jump (issues Upgrade ZMK to v0.4 / Zephyr 4.1 #2/Canary: test ZMK main / Zephyr 4.1 with spare nice_nano #3/Canary: test ZMK main / Zephyr 4.1 with nice_nano #4 stay parked).
• Central-only studio/RPC/BLE Kconfig lives in the module's eyelash_sofle_left.conf — keep it out of the shared config/eyelash_sofle.conf.
• Plan: .claude/plans/quiet-munching-dahl.md (local).

Refs: PR #28.

[rdlu]

✅ Branch CI build passed (run) — both halves + reset build clean in a clean environment. Downloadable .uf2 artifacts are on that run if you'd rather flash those than build locally.

[rdlu]

Update: PR is now #31 (branch feat/studio-firmware; #28 closed on the rename). Scope is firmware-only — the Studio web app moved to a separate fork project (see #30, ~/Projects/sofle-studio). Hardware test + release steps unchanged; verify BLE editing using that fork (or the hosted app).

[rdlu]

✅ Shipped as v2.5.0.

• Hardware test — Studio connects + edit persists over USB (/dev/ttyACM0, CDC-ACM) and BLE (GATT, the headline feature). Encoder, all 8 layers, pointing, RGB, gaming layers all good.
• Merged PR feat: ZMK Studio over USB + Bluetooth (cormoran fork) — firmware → v2.5.0 #31 → main
• Waited for the [Draw] auto-commit (212706f), pulled --ff-only
• Annotated tag v2.5.0 on the [Draw] commit, pushed
• Notes-only GitHub release, marked latest

Bug caught during verification: mise run build-left passed -Dsnippet= (lowercase) which Zephyr's snippet system ignores (it reads the case-sensitive SNIPPET var), so locally-built left firmware was BLE-only with no USB CDC-ACM. Fixed in faa34f0 → -DSNIPPET=. CI's build.yaml snippet: key was always correct, so released artifacts were never affected.

Linux BLE note: Chrome ships Web Bluetooth disabled on Linux — enable chrome://flags/#enable-experimental-web-platform-features and relaunch for BLE editing.

Closing — the firmware side is done. Web app tracked in #30.