Found during the bluetooth-ui-api review (pre-existing, from the active/auto scanner work in PR #52 — not introduced by PR #56).
UniversalProxy.Bluez.Client.start_transition/3 spawns the passive↔active mode-transition Task with a bare Task.start/1. The inner try/rescue/catch covers raises and throws, but an external :kill (or OOM termination) bypasses it: the completion message never arrives, state.transition stays non-nil, and every subsequent set_mode/1 parks until the 32 s call timeout.
Fix: run it under a Task.Supervisor (the pattern Bluez.Gatt already uses for its BlueZ calls), or monitor the Task and treat a :DOWN without a completion message as a failed transition.
Same bare-Task.start pattern also pre-exists in uart/server.ex and uart/store.ex (lower stakes — fire-and-forget restarts, no state machine to wedge).
🤖 Generated with Claude Code
Found during the bluetooth-ui-api review (pre-existing, from the active/auto scanner work in PR #52 — not introduced by PR #56).
UniversalProxy.Bluez.Client.start_transition/3spawns the passive↔active mode-transition Task with a bareTask.start/1. The innertry/rescue/catchcovers raises and throws, but an external:kill(or OOM termination) bypasses it: the completion message never arrives,state.transitionstays non-nil, and every subsequentset_mode/1parks until the 32 s call timeout.Fix: run it under a
Task.Supervisor(the patternBluez.Gattalready uses for its BlueZ calls), or monitor the Task and treat a:DOWNwithout a completion message as a failed transition.Same bare-
Task.startpattern also pre-exists inuart/server.exanduart/store.ex(lower stakes — fire-and-forget restarts, no state machine to wedge).🤖 Generated with Claude Code