iqon/reports/continuation-risk-closure-2026-05-20.md

IQON continuation risk closure

Purpose: record the next execution pass after legacy hardening: backup confirmation, live health, visual QA, and remaining gates.

Created: 2026-05-20 Updated: 2026-05-20

Completed checks

1. Git worktree was clean before this continuation pass.
2. Local backup folder was checked for SQL/dump/archive files at max depth 3.
3. No local SQL/dump/archive file was found under server-backup-20260518.
4. Existing restore documentation says DB archive for u0012812_iqon was initiated on 2026-05-18, not confirmed downloaded.
5. FTP account root listing was checked read-only.
6. FTP webroot listing was checked read-only.
7. No DB dump/archive was visible in the accessible FTP listings.
8. scripts/iqon-phase1-verify.sh https://iqon.com passed.
9. https://www.iqon.com/ still showed new redesign markers: theme-color, topbar, hero-cloud.
10. https://iqon.com/contact/ showed legacy contact content with office@iqon.com and @infobidgebot.
11. Browser QA checked apex home, apex contact, and www home at 390px, 768px, and 1440px.
12. Browser QA found contact page horizontal overflow at 390px.
13. Contact template inline width: 600px!important was removed from the CAPTCHA row.
14. Browser QA after the fix showed contact 390px scrollWidth=375, viewportWidth=390, horizontalOverflow=false.

Classification

Item	Status	Evidence
DB/archive confirmation	IN_PROGRESS	No local or FTP-visible DB archive found; panel archive only documented as initiated
Apex hardening health	VERIFIED	Existing phase verification script passed
WWW redesign health	VERIFIED	Live markers still present on www.iqon.com
Contact page content	VERIFIED	Current email and Telegram found; obsolete phone patterns absent in matched output
Contact mobile overflow	VERIFIED	Browser QA after patch reports no horizontal overflow at 390px
Contact form delivery	PROPOSED	Not submitted; requires explicit approval because it sends external mail

Browser artifacts

Screenshots were created inside the Firecrawl browser session at:

1. /private/tmp/iqon-visual-qa-20260520/apex-home-390.png
2. /private/tmp/iqon-visual-qa-20260520/apex-home-768.png
3. /private/tmp/iqon-visual-qa-20260520/apex-home-1440.png
4. /private/tmp/iqon-visual-qa-20260520/apex-contact-390.png
5. /private/tmp/iqon-visual-qa-20260520/apex-contact-390-after.png
6. /private/tmp/iqon-visual-qa-20260520/apex-contact-768.png
7. /private/tmp/iqon-visual-qa-20260520/apex-contact-1440.png
8. /private/tmp/iqon-visual-qa-20260520/www-home-390.png
9. /private/tmp/iqon-visual-qa-20260520/www-home-768.png
10. /private/tmp/iqon-visual-qa-20260520/www-home-1440.png

Note: these paths belong to the browser execution environment, not the local git workspace.

Remaining gates

1. Confirm/download DB archive from reg.ru panel or another trusted source.
2. Submit contact form smoke only after explicit approval.
3. Decide whether to keep WordPress apex long-term or freeze old design into static snapshot.
4. Implement sitemap/redirect cleanup only after target sitemap approval.