4 Commits (dev)

Author	SHA1	Message	Date
Strycher	31c0674330	fix(#81): stop the observer config feature from slowing the channel sync ... Three observer-delta fixes (per the #80 sync diagnosis / G2): - A: settings screen gates the Observer category via context.select on the supported flag, not a connector-wide context.watch -- the watch rebuilt the whole settings screen on every sync frame, thrashing the UI thread. - B: a flat Save re-reads only the flat settings (refresh includeBrokers:false), never the 84-frame broker pool -- no BLE re-flood for a display toggle. - C: the initial observer read is deferred until the device's channel/contact sync settles, so it never competes with that sync for BLE. TDD: B (no OCFG_BROKERS on a flat refresh) + C (refresh deferred while syncing, fires once idle). Full observer suite green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
Strycher	f56a6ac58f	fix(#79): degrade gracefully when the broker dump fails (G2 finding) ... The G2 BLE log showed the config protocol works (GETs return values; the broker dump starts) but the firmware's broker dump stalls without BROKERS_END, so getBrokers() times out. The client was treating that as a TOTAL failure -- discarding the 7 flat settings it read cleanly and blanking the pane. Now the broker pool loads independently: refresh() builds + shows the flat config even when getBrokers fails, flags brokersUnavailable, and the pane shows the broker section as "unavailable" instead of going stale. Flat settings stay usable. TDD red->green; full observer suite (39) green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
Strycher	7825225e73	fix(#78): surface partial-refresh failures + validate status_interval (G1 follow-up) ... Closes the 2 MINOR findings from the G1 re-review (#76): - MINOR-A: ObserverConfigService.refresh() no longer wipes lastError / clears stale on a PARTIAL read. A null from any getFlat is a failed read; the snapshot is marked stale and the error kept (error-visibility). - MINOR-B: the settings pane validates status_interval against the firmware range (10-3600) before sending; an out-of-range value is not put on the wire and the user is told. TDD: both tests RED first (current sent '5'; refresh wiped the error), GREEN after. Full observer suite (37 tests) green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
Strycher	708f168d45	feat(#75): harden observer settings UI + lock behavior (U1) ... Hardened the staged-save pane (settings_screen capability gate already correct): - Normalize an unexpected device rotation to a valid SegmentedButton segment {0,180} so the control always has a valid selection and never echoes an out-of-range value back on save. - Disable Save during a refresh (no save/refresh race on the controllers). - digitsOnly formatter on status-interval (firmware still range-checks). - Keys on the SSID/password fields for robust widget-test targeting. 4 widget tests pin the security-sensitive behavior: saves send ONLY changed keys, a blank password keeps the stored secret, an entered password is sent as wifi.pwd then the field clears, rotation is normalized, stale/error surfaced (SAFELANE §6). Full observer suite (33 tests) green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago