diff --git a/docs/WEEKLY_RELEASE_TRACKER.md b/docs/WEEKLY_RELEASE_TRACKER.md
index 5a09d2ba..fcb5eacc 100644
--- a/docs/WEEKLY_RELEASE_TRACKER.md
+++ b/docs/WEEKLY_RELEASE_TRACKER.md
@@ -4,19 +4,37 @@ Last updated: 2026-06-14 (session on node .116 / archi-thinkpad)
 
 ---
 
-# ▶ CURRENT PASS — v1.7.91-alpha (2026-06-14)
+# ✔ DONE PASS — v1.7.91-alpha + v1.7.92-alpha (2026-06-14)
 
-## RESUME PROMPT (paste into a fresh session, any machine)
+## Outcome (both releases PUBLISHED + LIVE on vps2)
 
-> Resume the v1.7.91-alpha release pass for the `archy` repo (on node .116 / archi-thinkpad
-> the tree is at /home/archipelago/Projects/archy; on another machine, clone/pull `main` from
-> gitea-vps2 http://146.59.87.168:3000/lfg2025/archy.git — my fix commit is pushed there).
-> Read the top section of docs/WEEKLY_RELEASE_TRACKER.md FIRST — it has the blocker, the fix
-> already made, and exact next steps. Two goals: (1) cut & PUBLISH v1.7.91-alpha, (2) finish
-> validating + integrating the new tests/lifecycle/os-audit.sh OS-wide health harness.
-> Do NOT redo: the bitcoinReceive.ts TS2538 fix (done, committed) or the os-audit jq false-trap
-> fix (done). Resume at "EXACT NEXT STEPS — v1.7.91" below. .116 login password: ThisIsWeb54321@
-> (.116 serves http on :80 → ARCHY_HOST=127.0.0.1 ARCHY_SCHEME=http).
+- **v1.7.91-alpha** — bitcoinReceive.ts TS2538 build-blocker fixed; cut, published, verified
+  live (`manifest.version==1.7.91-alpha`), tag `v1.7.91-alpha` on vps2. The fleet OTA'd to it
+  (confirmed on .116 + .198).
+- **v1.7.92-alpha** — cut, published, verified live (`manifest.version==1.7.92-alpha`), tag on
+  vps2, main@d462e444. Carries:
+  - `fix(ui)` ElectrumX **overlay-during-sync** bug — the "App not reachable / retry" overlay
+    no longer paints over the ElectrumX sync screen (AppSessionFrame.vue gated on `!electrsSync`).
+  - `test(resilience)` **L3 per-boot health gate** — `batch_host_reboot` now runs os-audit.sh
+    after reboot (RPC/OTA/all-apps/FM-guards), not just container-set equality. os-audit validated
+    11/0/0 green on .116.
+  - `feat(release)` **What's New sync gate** — `scripts/sync-whats-new.py` + `whats-new-sync`
+    stage in tests/release/run.sh. Backfilled the 8 missing modal blocks (v1.7.85→.92); the gate
+    fails any release whose CHANGELOG version isn't in the Settings modal.
+- **.116 node fix (not shipped — local config)**: restored the `/lnd-connect-info` nginx proxy
+  route that a 2026-06-10 "before-116-routing" change had dropped (fell through to SPA). Backup at
+  `/etc/nginx/conf.d/rpc.tx1138.com.conf.bak-lndconnect-*`. Shipped template already has the route.
+- **User symptoms triaged (none were .91/.92 regressions)**: receive-generate "unchanged" = .91's
+  receive change was a behavior-preserving build guard; ElectrumX "can't connect" on .198 = Bitcoin
+  node mid-"Verifying blocks…" (-28) so electrs was "waiting for Bitcoin node"; on .116 electrs was
+  ~59% mid-sync. The overlay UX bug is fixed regardless.
+
+## Known follow-ups (not blockers)
+- **gitea-local mirror push fails** (`localhost:3000` → redirect to `/login`, token auth). vps2 is
+  the OTA source and is fine; gitea-local secondary mirror is stale. Diagnose the local Gitea token.
+- `sync-whats-new.py` only **inserts missing** versions; it does not rewrite a block when CHANGELOG
+  bullets for an already-present version change (had to delete+resync the .92 block by hand to pick
+  up its 3rd bullet). Fine for the forward case; enhance to idempotently re-render if needed.
 
 ## What happened this session