7e3d01f633
All checks were successful
Demo images / Build & push demo images (push) Successful in 2m59s
A pairing QR minted while the node UI was browsed over the mesh carried npub….fips as fhost. Android's system DNS can't resolve .fips, so every direct handshake dial failed and first connect crawled through public- anchor discovery (2m35s observed) instead of one LAN hop. - node UI: resolveServerUrl treats .fips names and IPv6 ULA literals as phone-unreachable and substitutes the node's LAN IP (same guard as tailnet/localhost) - app: QR parser falls back to the url param's host when fhost is .fips - app: peer store never keeps .fips dial addresses - app: peer aliases slugged for the fips host map (spaces dropped "Framework PT"/"Mesh anchor" from name resolution entirely) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
