CLEARNET DEFAULT CUTOVER — 2026-10-21
Existing https://54.241.198.5/?url=<base64> entry/share links now return temporary302 to https://proxy.torry.io/ with original query preserved; new engine creates an isolated HTTPS session. Exact root only; empty-root behavior and legacy /_tav/ routes remain. Live Torry search button was clicked and destination loaded in the new viewer. Main search, AI and onion server/configurations were not modified.

Rollback on54.241.198.5:
 sudo sh /var/backups/torry-compat-default-20261021/rollback.sh
Restores only preceding IP-entry Nginx config; validates checksums/current revision and nginx syntax before reload. New engine stays running for existing sessions. No DNS change required. Old launcher/proxy both remain active. Actual rollback restored old entry HTTP200; identical cutover then reapplied. Use this FIRST for any rollback; old preview-removal script intentionally refuses while entry points to new engine.

Backup:
 /var/backups/torry-compat-default-20261021/before.conf
 /var/backups/torry-compat-default-20261021/after.conf
 /var/backups/torry-compat-default-20261021/configs.sha256
 /var/backups/torry-compat-default-20261021/preview-source-before.tgz

Candidate production labels applied;256 sessions maximum,128 upstream WebSockets global,4/session,15-minute no-connection expiration,6-hour hard expiry. Existing per-host stream/private-IP protections and Nginx rate limits retained. Capacity bound is not a load benchmark. Source package must be regenerated for these changes. Existing direct YouTube embed path is bypassed for NEW entry visits; new engine has no direct-player fallback. Old open pages can retain old behavior until reopened.

Four backend checks passed. Live search -> Anonymous View -> new HTTPS session verified; HLS tested through legacy IP entry. Certificate valid until Jan19,2027; manual DNS renewal remains required. No ongoing monitoring or renewal reminder scheduled. No GitHub commit/push requested or performed.
