Rebuild + redeploy of the prior commit. Version bumped from 0.0.3 →
0.0.4 so the chip actually surfaces itself for anyone still on 0.0.3
(the versionIsNewer check requires a strict semver bump — same-version
rebuilds are intentionally silent).
TheseusNavigator-Setup-0.0.4.exe
sha256 2722c07317b6ab45b22bbaaacb043f0dcdb30a02a6ec1c3c9525ad94ecbd2574
TheseusNavigator-0.0.4-portable.exe
sha256 938505db9a9a83387387c998423925168498bc482768e23b1b888ad62069fa20
Live on dl.silentmode.st + Sia bns/silentmode/. Manifest bumped to
2026-08-08. Site pages (site/tools/index.html + site/releases/index.html)
updated with the new filenames + hashes.
Rollback points on the VPS at /opt/silent-mode/dl/_prev/ (7 versions):
- 8ab9cc3e (0.0.3, UX batch — the ship right before this one)
- 9c09955e (0.0.3, password manager phase 1)
- b62ecf52 (0.0.2, shield green)
- 418e7bba / 208b059a / 036e94c7 (0.0.1 series)
- 81831c08 (parallel-session 0.0.1)
On-chain pointer at releases.silentmode.bch unchanged — publishes the
manifest URL, so 0.0.4 is reachable via BCNR without a wallet spend.
What existing 0.0.3 users will see: on their next Theseus launch the
new update-check chip fires immediately (startup fetch of the manifest),
showing "↓ Update to 0.0.4" next to the Tor toggle. Click → downloads
the installer via the system browser. Dismiss → hidden this session,
reappears next launch until they upgrade.
bde5c787fc