chore: record iqon gates and redirects

This commit is contained in:
Sergei Vasilev
2026-05-20 22:56:16 +03:00
parent f9c513e4c8
commit f1093fb178
5 changed files with 317 additions and 0 deletions
+60
View File
@@ -0,0 +1,60 @@
# IQON next gates and rollback runbook
Purpose: document the remaining IQON operational gates after restoring the old apex design and hardening it.
Created: 2026-05-20
Updated: 2026-05-20
## Current production split
| Host | Intended live design | Current role |
|---|---|---|
| `https://iqon.com/` | Old WordPress IQON design | Primary apex site |
| `https://www.iqon.com/` | New static dark redesign | Separate www variant |
## Rollback sources
| Source | Path | Use |
|---|---|---|
| Pre-static remote snapshot | `/private/tmp/iqon-remote-prestatic-20260520-ftp/` | Restore files that existed before static upload |
| Current deployed legacy patch copy | `deploy/legacy-wordpress-2026-05-20/` | Re-upload current known-good patched theme files |
| Legacy restore docs | `server-backup-20260518/RESTORE.md` | Recovery instructions and non-secret server paths |
| Static www artifact | `index-www-new-redesign.html` on remote webroot | Keep `www.iqon.com` new design route active |
## Health checks to run before and after any future change
```bash
scripts/iqon-phase1-verify.sh https://iqon.com
curl -k -sS -L https://www.iqon.com/ | rg -n "theme-color|hero-cloud|topbar"
curl -k -sS -L https://iqon.com/contact/ | rg -n "Bucharest Office|office@iqon.com|infobidgebot"
```
Expected signal:
1. Apex hardening script prints `[OK] iqon Phase 1 verification passed for https://iqon.com`.
2. `www.iqon.com` contains `theme-color`, `topbar`, and `hero-cloud`.
3. Apex contact page contains `Bucharest Office`, `office@iqon.com`, and `@infobidgebot`.
## Remaining approval gates
| Gate | Status | Required approval or evidence |
|---|---|---|
| DB archive confirmation | Blocked | Confirm/download `u0012812_iqon` archive from reg.ru panel or another trusted source |
| Contact form smoke | Approval required | Explicit approval to submit a live form that sends email |
| Sitemap redirects | Approval required | Confirm target sitemap and whether stale multilingual URLs should redirect or remain archived |
| WordPress retirement | Decision required | Choose long-term mode: keep hardened WP apex or freeze old design into static snapshot |
## Recommended next execution order
1. Confirm DB archive in reg.ru panel and download it if available.
2. Run contact form smoke with a clearly marked test message after approval.
3. Decide long-term apex platform: hardened WordPress or static snapshot of old design.
4. Approve sitemap redirect policy for stale RU/KZ/encoded URLs.
5. Implement redirect policy only after backup gate is closed.
## Explicit non-actions
1. Do not delete WordPress files.
2. Do not overwrite `www.iqon.com` routing.
3. Do not submit contact form silently.
4. Do not publish broad redirects without target sitemap approval.