chore: record iqon continuation risk closure
This commit is contained in:
@@ -0,0 +1,48 @@
|
||||
---
|
||||
task: Продолжить IQON backup form visual redirects rollback
|
||||
effort: extended
|
||||
phase: package
|
||||
progress: 14/16
|
||||
mode: interactive
|
||||
started: 2026-05-20T21:40:00+03:00
|
||||
updated: 2026-05-20T21:40:00+03:00
|
||||
---
|
||||
|
||||
# Продолжить IQON backup form visual redirects rollback
|
||||
|
||||
Purpose: закрыть следующий слой рисков после live hardening старого apex-дизайна IQON.
|
||||
|
||||
## Context
|
||||
|
||||
После live patch старый `iqon.com` работает на WordPress, `www.iqon.com` отдаёт новый дизайн. Открытые риски: статус DB/archive, непроверенная contact form delivery, визуальная mobile QA, sitemap/redirect cleanup, rollback health note.
|
||||
|
||||
## Criteria
|
||||
|
||||
- [x] ISC-1: Git worktree is clean before new changes.
|
||||
- [x] ISC-2: Local backup files are inventoried safely.
|
||||
- [x] ISC-3: DB archive status is classified by evidence.
|
||||
- [x] ISC-4: FTP backup-visible files are checked read-only.
|
||||
- [x] ISC-5: Apex homepage health remains passing.
|
||||
- [x] ISC-6: WWW redesign health remains passing.
|
||||
- [x] ISC-7: Contact page health remains passing.
|
||||
- [x] ISC-8: Contact form submission remains gated by approval.
|
||||
- [x] ISC-9: Redirect cleanup inputs are checked locally.
|
||||
- [x] ISC-10: Sitemap cleanup next step is documented.
|
||||
- [x] ISC-11: Visual QA method is selected without guesswork.
|
||||
- [x] ISC-12: Rollback source artifacts are identified.
|
||||
- [x] ISC-13: No remote destructive operation is performed.
|
||||
- [x] ISC-14: No credential values are written to reports.
|
||||
- [ ] ISC-15: Findings report is saved in repo.
|
||||
- [ ] ISC-16: Project memory is updated with current status.
|
||||
|
||||
## Decisions
|
||||
|
||||
- Do not submit the public contact form without explicit approval.
|
||||
- Do not delete or overwrite remote backup files.
|
||||
- Prefer direct evidence over assumptions about reg.ru archives.
|
||||
|
||||
## Verification
|
||||
|
||||
- Use read-only filesystem and FTP checks.
|
||||
- Use existing live verification script.
|
||||
- Save report and memory update.
|
||||
@@ -103,7 +103,7 @@
|
||||
<label id="label_mesaj">Message:</label>
|
||||
<textarea name="mesaj" id="mesaj"></textarea>
|
||||
</div>
|
||||
<div class="rowInput" style="width: 600px!important;">
|
||||
<div class="rowInput rowInputValidation">
|
||||
<label id="label_validation">Validation code(required):</label>
|
||||
<input type="text" name="validation" id="validation" value="" data-default="validation code" class="text validation" style="width: 100px!important; text-transform: uppercase;" />
|
||||
</div>
|
||||
|
||||
@@ -0,0 +1,58 @@
|
||||
# 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.
|
||||
Reference in New Issue
Block a user