5 Commits

Include renames

Author	SHA1	Message	Date
DorianandClaude Fable 5	3995ab5cf5	perf(companion): 5s discovery timeout — fresh-join route lookups fail fast — 0.5.14 ... First lookups fire before the phone's tree position settles and are doomed; at 10s completion timeout each one cost 10s before the 1s retry could fire (observed 19s to a route on a fresh 5G join, session 3ms after the route — discovery convergence was the whole cost). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-24 15:35:50 +01:00
DorianandClaude Fable 5	9d83ee3770	perf(companion): fast-connect mesh profile — 5G cold connect 40s+ → 5.4s — 0.5.13 ... Stock fips pacing is tuned for always-on routers: a failed discovery backs off 30s, session resends gap out to 8-16s, dead links redial at 5s→300s. On a phone that stacked into a 40s+ first connect over cellular. Config-only tuning in build_config (no fork changes): discovery backoff 1s (cap 30s), session resends 400ms x1.5 (10 max), link redial 1s (cap 30s). Measured on-device: anchor +1.2s, node session +5.4s from cold start over 5G. Ops note: vps2 anchor daemon had degraded again (multi-second link RTTs after 15h uptime) — restarted, recycle tightened 1d → 6h. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-24 15:23:57 +01:00
DorianandClaude Fable 5	f0926ece94	feat(companion): mesh party + Flare, keep-warm mesh, restored fast-start, UI fixes — 0.5.7 ... Combined session state from both agents (shared checkout): - Mesh Party / Flare (experimental): phone-to-phone FIPS via party QR, Flare chat/beam on :5680, optional fixed UDP listen (2121); party-only phones get the baked-in Archipelago anchor so two bare phones reach each other across the internet, not just on a hotspot. - Keep-warm mesh: a running healthy node survives app opens (restart only when dead or peers changed — peersDirty); requestMeshRestart for config changes. Cold start measured on-device: session in ~3.1s. - Restored after regression: startup LAN-vs-mesh race (the party work was based on a pre-#114 file copy) and same-node routing (BTCPay/ Pine/HA had returned to opening in the external browser). - UI: top status-bar scrim removed (bottom-only bars); web app-session mobile bar is solid black — app theme colour no longer bleeds through the bar and its safe-area strip. Served APK: 0.5.7 (vc27). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-24 01:04:36 +01:00
DorianandClaude Fable 5	53037b2b71	fix(companion): TUN reader no longer dies on non-blocking fd + VPN not metered ... On-device diagnosis (phone on adb, 5G): mesh sessions established but no packet ever entered the tunnel — Android hands the VpnService TUN fd over non-blocking, and the fips fork's dedicated blocking-read thread treats EAGAIN as fatal, dying at startup. archy-fips-core now forces the fd into blocking mode before Node::start_with_tun_fd. Verified on-device: reader survives, packets flow into the mesh, and the 30s anchor-link flap is gone (stable 8+ min on 5G). Also setMetered(false): Android 10+ defaults VPNs to metered, flipping the phone into data-restricted behaviour whenever the mesh is up. Served APK: 0.5.4 (vc24). Handoff updated with the remaining node-side blocker: phone->anchor works, phone->node ULA gets no reply — needs fipsctl introspection on Framework PT (suspect fork/daemon session or routing mismatch). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-23 22:47:26 +01:00
DorianandClaude Fable 5	4b91765cc7	feat(companion): embedded FIPS mesh replaces WireGuard for remote access ... - Android/rust/archy-fips-core: leaf-only fips node as a JNI cdylib (fips pinned to the fips-native fork rev with VpnService fd support), built by gradle via cargo-ndk (arm64), tested on host - ArchyVpnService: split-tunnel VpnService routing only fd00::/8 (MTU 1280, foreground specialUse); FipsManager handles the one-time VPN consent and silent auto-start — no settings surface at all - pairing QR now fully configures the mesh: fnpub/fip/fhost/fudp/ftcp plus fanchors (the node's seed-anchor list, npub@addr/transport) so the phone can rendezvous through public anchors when the LAN endpoint is unreachable - default seed anchors gain the two dual-transport join.fips.network test anchors (23.182.128.74:443/tcp, 217.77.8.91:443/tcp); anchor adverts are Nostr kind-37195 events - device token rides the password field end-to-end: backend accepts tokens wherever it accepts the password, so scan = instant login (WebSocket auth + WebView form injection unchanged); token logins skip TOTP - ServerEntry.meshIp + IPv6-bracketed URLs; WebView retries the mesh address on main-frame errors, auto-login and origin checks honor it - companion v0.5.0 (versionCode 20), arm64 abiFilter; FipsNative.available gates everything so non-arm64 still runs as a plain companion Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-22 22:06:32 +01:00