installer: drop the wifi check entirely

docs/INSTALLER.md

@@ -3,9 +3,15 @@
 ## What it does
 
 One linear flow, forward-only (every No skips ahead, nothing loops back):
-confirm → copy `orbisrpc.bin` to `/data/GoldHEN/bin/elf/` (mkdir -p + size
-read-back, one OK/denied line) → WiFi check → token prompt (skipped when
-valid) → done. Declining install offers a read-only status screen instead.
+confirm → copy `orbisrpc.bin` to `/data/GoldHEN/bin/elf/` (mkdir -p +
+byte-count + hash read-back, one OK/denied line) → token prompt (skipped
+when valid) → done. Declining install offers a read-only status screen
+instead.
+
+There is no WiFi check. The installer runs sandboxed, so its socket probe
+measures the app's network stack, not the payload's — and a FAILED line
+reads like a verdict on Discord itself. The daemon reports real reachability
+in its own log once started.
 
 The installer never boots anything. Starting the daemon is GoldHEN's
 payload menu or AutoRun — see below. No loopback ports, no eviction, no
@@ -22,12 +28,12 @@ exits are Done, explicit close, or a payload write failure.
   3 s foreground settle, or the first dialog flash-dismisses.
 - Dialog/IME/IME-backend sysmodules + internal SYSTEM/USER/COMMON modules
   load before use (unloaded calls panic).
-- Network stack: internal NET module + `sceNetInit` + pool, verified with a
-  probe socket. All connects non-blocking with hard deadlines (blocking
-  connect ignores timeouts on filtered hosts — 75 s hole).
+- `stat()`/`fstat()` lie about sizes inside the sandbox (observed 4096/4160
+  for a 2071552-byte file), so install proof is byte count + FNV hash on
+  read-back, and status uses open-existence, never stat.
 - Config writes are atomic (tmp+fsync+rename) with read-back proof.
-- IME wait is bounded; EAGAIN send retries are capped; asset key charset
-  validated (bad keys blank the activity).
+- IME wait is bounded; asset key charset validated (bad keys blank the
+  activity).
 
 ## Auto-start