5 Commits (f6ebeef4f7b4dbc4077a32609f83a230848ecf56)

Author	SHA1	Message	Date
Strycher	37d2ca9fb1	feat(#93): render broker runtime-state + resolved-default placeholders ... Consume the additive OCFG_BROKERS dump fields from firmware #172/#173 (backward-compatible — absent fields read as today's enabled/disabled): - BrokerRuntimeState (`state`) + BrokerLastError (`last_error`) + a pure BrokerConfig.status mapping -> Connected / Connecting / Failed (reason) / Held (no clock|low heap) / Enabled / Disabled; held shown neutral, not error. - Brokers list shows the real status line + colour instead of just "enabled". - Editor shows jwt_owner / iata_override resolved defaults (`jwt_owner_resolved`, `iata_resolved`) as greyed placeholders when the raw key is blank; only writes the raw key when the user enters a value (blank stays the source of truth). Sourced from the pool dump (getBrokers); getBroker's per-field GET list is unchanged pending the firmware GET-ability answer on #173. Unit-tested mapping, parsing, and backward-compat (9 tests). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
Strycher	4d7921d2f7	feat(#89): verify broker enable/disable actually applied before confirming ... A firmware build can ACK a broker enable/disable as success without applying it (HV4; meshcore-firmware#179). The quick toggle and the editor save previously trusted the ACK and showed a success snackbar, so an ack-but-no-op looked like it worked. Both paths now SET, wait a short settle, re-read the slot, and report what the device ACTUALLY did: - applied -> confirm - notApplied -> warn "possible firmware issue"; the editor stays and re-seeds to the device's true state instead of popping a false success - unverified -> re-read failed (e.g. an enable that rebooted the device) Every device is treated identically: the UI reflects the re-read, never assuming a change took that the device didn't confirm. - BrokerConfig.classifyApply pure classifier + BrokerApplyOutcome (unit-tested) - ObserverConfigService.applySettleDelay - wired into mqtt_brokers_screen quick toggle + broker_editor_screen save - widget test for the ACK-but-not-applied path Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
Strycher	247133511b	test(#70): lock observer config model behavior (M1) ... The models are the existing draft (1983ed9); Gemini flagged nothing in them. This pins the defensive behavior they give untrusted wire data: enum fromWire fallback, numeric tryParse fallback, secret-presence flag, SecretField three-state, copyWith. 7 tests, all green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	4 weeks ago
zjs81	4ad4a93a20	formatted code	4 months ago
zjs81	4962a48e64	Msg Retry fixes, channel message fixes. Notification fixes. Make more desktop friendly. Enhance retry algo. Fix predicted location clustering add retries to reactions and fix the reactions in private DMS centralize and cleanup code in var areas	4 months ago