chore: record iqon live deployment

deploy/.htaccess

@@ -3,6 +3,9 @@
 # Created: 2026-05-20
 # Updated: 2026-05-20
 
+# ── Prefer static entrypoint while WordPress files remain for rollback ──
+DirectoryIndex index.html index.php
+
 # ── Security headers ──────────────────────────────────────────────
 <IfModule mod_headers.c>
     Header always set X-Content-Type-Options "nosniff"
@@ -16,10 +19,6 @@
 <IfModule mod_rewrite.c>
     RewriteEngine On
 
-    # ── Force HTTPS ───────────────────────────────────────────
-    RewriteCond %{HTTPS} off
-    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
-
     # ── Canonical host ────────────────────────────────────────
     RewriteCond %{HTTP_HOST} ^www\.iqon\.com$ [NC]
     RewriteRule ^ https://iqon.com%{REQUEST_URI} [L,R=301]

deploy/README.md

@@ -147,8 +147,8 @@ curl -I https://iqon.com/robots.txt
 
 If the static deployment has issues:
 
-1. Log in to reg.ru hosting panel
-2. Restore files from the backup created in Step 1
+1. Restore the pre-static files from `/private/tmp/iqon-remote-prestatic-20260520-ftp/` if only root entry files changed
+2. Log in to reg.ru hosting panel if a full restore is required
 3. If only `.htaccess` caused the issue: restore the original WordPress `.htaccess` from `server-backup-20260518/.htaccess`
 4. The WordPress database and theme files in `_wordpress_backup/` can be restored