HoneyBadger Mesh Android 0.1.18 — 2026-07-12

- Android now installs 1.1.1.1 and 8.8.8.8 as tunnel DNS resolvers. Restricted
  physical networks can no longer poison YouTube and other dual-stack domains
  before their traffic enters the Mac mini exit.
- Production E2E passed before release: api.ipify.org returned the Mac mini's
  99.47.65.72 address, Android's resolver used the VPN DNS network, the YouTube
  home page rendered, and a Big Buck Bunny video played over the live WSS relay.
- During playback the Mac mini delivered about 582 KB to Android in 10 seconds,
  confirming real media transfer rather than a cached page or static poster.

- Android now starts every mesh peer, including the selected exit, on the
  HTTPS/WSS relay path. Restricted mobile networks no longer leave the exit on
  an unreachable direct WireGuard/UDP endpoint while the UI says it is active.
- The HoneyBadger package remains excluded from its own full-tunnel route, so
  coordinator and relay sockets stay on the physical network without leaking
  any other application's traffic.
- Verified on Android API 35 against the live Mac mini exit: WireGuard completed
  a bidirectional handshake immediately, 1.1.1.1 returned 3/3 replies with 0%
  loss, and the exit's PF state table showed the Android HTTPS connections.
- Added relay-side first-frame diagnostics per source/destination pair. Logs
  expose ciphertext routing failures without logging payloads or private keys.

- Fixes Android relay-only exits: HoneyBadger's coordinator and WSS relay
  transport now bypass the VPN it owns, preventing a full-tunnel route from
  recursively capturing and breaking its own relay.
- Verified by blocking all direct UDP on Android: traffic initially stopped,
  the client detected the dead direct path, switched the Mac mini exit to WSS
  relay, and public traffic recovered and stayed active.
- Android's VPN UID policy was inspected at runtime and excludes only the
  HoneyBadger package while continuing to tunnel all other applications.
- Fixes the Android native crash that closed the app shortly after connection.
  HBMobile and WireGuard now run in isolated Android processes, so their two Go
  runtimes can no longer corrupt each other's runtime state.
- VPN and notification permission prompts are requested sequentially instead of
  launching two Android permission activities at once.
- Verified on Android API 35: mesh connection, background operation, disconnect
  and reconnect, Mac mini exit selection, IPv4/IPv6 default routes, WireGuard
  handshakes and public-network traffic all remain active without a new crash.
- Android follows the device language in English, Simplified Chinese and
  Traditional Chinese.
- Android is version 0.1.18; macOS, Windows, Linux and iOS remain on 0.1.13.
- Active relay-backed exits stay on their proven relay path instead of forcing
  a disruptive direct-path trial every five minutes.
- Control and relay endpoints bypass full-tunnel routes during bootstrap.
- macOS Exit-mode DNS uses a clean resolver inside the tunnel, handles parallel
  queries concurrently and flushes poisoned cache entries on upstream changes.
- macOS, Windows and Linux include the latest real WireGuard data plane.

Distribution status:
- macOS package: ad-hoc/unsigned installer.
- Windows archives: unsigned; x64 and ARM64.
- Linux archives: unsigned; x64 and ARM64.
- Android APK: debug-signed test build until a release keystore is supplied.
- iOS: device build is not publicly installable until an Apple distribution
  certificate and provisioning profile are supplied.