Package-level declarations
Types
Caches the nRF52 bootloader/OTA quirk catalog from the Meshtastic API (/resource/bootloaderOtaQuirks), seeded from the bundled device_bootloader_ota_quirks.json snapshot so it is never empty offline. Unlike DeviceHardwareRepositoryImpl (which this mirrors for seeding), reconcile carries no TTL of its own — DeviceHardwareRepositoryImpl's own refresher calls it on the same cadence as its catalog refresh, so the two caches age together instead of drifting on separate schedules.
Caches the resolved device-links catalog from the Meshtastic API (/resource/deviceLinks). The server does all the classification (type/targets/regions), so the client just seeds from a bundled snapshot, refreshes from the network, and filters the cache. Mirrors DeviceHardwareRepositoryImpl's seed → single-flight refresh pattern.
Memoizes per image name for the process lifetime: a model is a few hundred KB to a few MB and the hero re-asks on every node detail open. The flasher's answer is cached either way; a failed request is not, so a later open retries.
Backed by the Koin-provided DiscoveryDao, which resolves the active database on every call, so readers follow a device switch and writes register with the cross-transport merge barrier.
Caches event-firmware display metadata in the DB, seeded from the bundled event_firmware.json snapshot and refreshed from /resource/eventFirmware. DB-backed (not just in-memory) so the snapshot survives across process restarts without waiting on a fresh network round-trip. Mirrors DeviceHardwareRepositoryImpl's seed → single-flight refresh pattern.
Caches the maintenance-UF2 manifest from the Meshtastic API (/resource/maintenanceUf2), seeded from the bundled maintenance_uf2.json snapshot so it is never empty offline — mirrors BootloaderOtaQuirksRepositoryImpl's seed-then-refresh shape exactly, including its "reconcile carries no TTL of its own" contract: DeviceHardwareRepositoryImpl's refresher calls this on the same cadence as its catalog refresh.
Repository implementation for managing and retrieving logs from the local database.
Caches the MQTT root directory from the Meshtastic API (/resource/mqttRoots), seeded from the bundled mqtt_roots.json snapshot, in MaintenanceUf2RepositoryImpl's seed-then-refresh shape: reconcile carries no TTL of its own, and each topic finder ViewModel calls it once when created.
Repository for managing node-related data, including hardware info, node database, and identity.
What a survey needs to know about the connected radio.