Retire the legacy NodeInfo, INodeStore, and IContactStore directory model. Route contact projections, protocol observations, persistence, and platform composition through IMeshPeerDirectory across ESP, Linux, and nRF52.
Split LXMF runtime ownership into focused peer, path, link, propagation, and delivery helpers while keeping the adapter as the coordination layer.
Make chat delivery refs and send-result events protocol-aware across Reticulum, Meshtastic, and MeshCore, including Sent/Delivered/Failed semantics, UI badges, retry lookup, and store persistence.
Fix Meshtastic MQTT private replies to publish encrypted direct packets and cover the new delivery behavior with smoke tests.
Add Reticulum token crypto support and conformance coverage, improve LXMF destination/link handling, expand contact/chat UI behavior, and rework Network/Nomad page UI with a Micron renderer.
Keep the Network renderer RAM-conscious by moving page link contexts to a bounded PSRAM-preferred pool and reducing Micron text/table object churn.
Persist and render cached Nomad page bodies, align the Network announce list with nomadnetwork.node entries, and preserve Reticulum identity hashes when opening saved contact details.
Add MeshPeerDirectory core persistence and contract tests.
Route MT, MC, and RT peer stores through the shared directory.
Move Reticulum LXMF address projections onto MeshPeerDirectory on ESP and Linux.
Add Reticulum as a first-class product protocol with LXMF delivery over LoRa and Wi-Fi TCP gateway carriers, SD-backed groups, identity/settings UI, Team appdata support, and conformance guardrails.
Remove the user-facing PC Link surface and keep RNode/LXMF as internal Reticulum implementation details.
Route phone custom channel variables to Meshtastic primary channel state instead of MeshCore config, keep explicit MeshCore aliases, and cover Custom/AQ short-PSK plus manual LoRa admin settings with the phone core smoke test.
Preserve protocol-specific send/discovery failures through the router and ChatService, restore MeshCore group fallback key handling, classify signed adverts/discovery responses on ESP/nRF52, and enable target logs plus smoke coverage so the next failure has actionable detail.
liu weikai