79c3cc5947
Some checks failed
Demo images / Build & push demo images (push) Failing after 3m50s
Two halves of the same twin-resolution gap, found live while testing images between archi-dev-box and archy-x250-dev: - peer_dest_prefix resolved the given contact row's own pubkey. For the UI's merged conversation (the federation-synthetic id) that's the Archipelago ed25519 identity key, NOT a radio routing key — so every Reticulum resource send (images/files over LoRa) failed with 'Unknown Reticulum prefix' while the UI showed the message as sent. It now resolves through the radio twin (same arch identity, radio-range id). - send_typed_wire sent EVERY federation-synthetic contact over the federation path (FIPS→Tor), even with the same node one LoRa hop away. Policy per operator: LoRa first when the payload fits and the radio twin is reachable, then FIPS, then Tor. Verified live: text to the merged contact now logs 'Radio-first routing' and lands with transport=reticulum on the peer. Also restyles the mesh-chat attachment download controls: the pre-fetch button was a bare .btn that squished to text width in the narrow mobile bubble; now a full-width glass pill with a download icon and fetch spinner, and the on-image overlay swaps the emoji glyph for a crisp SVG in a properly-sized glass circle. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>