forked from Blendman974/faceclaw
Silent mode is entered and exited only by long-pressing both touchpads. While it is on the firmware ignores all input and blanks the display, so from the phone the glasses look connected and simply answer nothing. The app cannot turn it off either: the communicator exposes onSilentMode and a listener set, and no setter. The status read "Connected (Silent mode enabled)", which names the state but not the way out of it, and someone who triggered the gesture by accident has no reason to know the gesture exists. It now names it. The belief can also go stale. silentMode is set by the firmware's push event and cleared only when the phase goes to disconnected, on the assumption that it is re-reported on the way back up. Toggle silent mode on the glasses without the link ever dropping and that assumption does not hold: a missed "off" leaves the phone claiming silent mode for as long as the connection lasts. Observed with the status reading silent while the glasses were granting framebuffer leases and rendering frames, which cannot happen in a mode whose whole behaviour is to blank the display and ignore input. So the belief is dropped whenever the glasses do something that mode makes impossible: input from them, since the firmware discards input while silent, or a shell render that gets past the display-target check, since silent mode does not leave a display target standing. The second matters because it self-heals without the user touching anything. Not unit-tested. Both halves are in dashboard-controller.ts, which imports 56 modules, so a test there would mostly exercise mocks, and the stale-clear is state management across events rather than a pure function. The refactor that would make it testable is moving the silent-mode belief into a small state holder taking the firmware's push events plus the two kinds of contradicting evidence; glasses-display-state.ts next door is already exactly that shape.