iqon/MEMORY/WORK/20260519-224203_full-iqon-audit-plan/PRD.md

task, slug, effort, phase, progress, mode, started, updated

task	slug	effort	phase	progress	mode	started	updated
Полный аудит iqon.com и план изменений	20260519-224203_full-iqon-audit-plan	extended	complete	20/20	interactive	2026-05-19T22:42:03+03:00	2026-05-19T22:47:52+03:00

Полный аудит iqon.com и план изменений

Purpose: зафиксировать проверяемый аудит live-сайта iqon.com и план изменений с опорой на Open Design.

Context

Сергей попросил сделать полный аудит iqon.com, использовать skill opendesign и подготовить план необходимых изменений. В доступном списке нет skill с точным именем opendesign; использованы Open Design skill entries design-review и frontend-design. В рамках задачи не запрошены live-изменения, деплой, доступ к админке или перенос секретов.

Risks

• Live WordPress core version is not directly confirmed; avoid stale exact-version claims.
• Visual audit is based on HTML/CSS evidence, not browser screenshots.
• Security recommendations must not imply remote changes were performed.

Criteria

• ISC-1: OpenDesign design-review skill entry inspected
• ISC-2: OpenDesign frontend-design skill entry inspected
• ISC-3: Codex iqon project memory inspected
• ISC-4: Local prior design audit inspected
• ISC-5: Live homepage headers inspected
• ISC-6: Live homepage HTML inspected
• ISC-7: Live stylesheet inspected for layout signals
• ISC-8: Live sitemap index inspected
• ISC-9: Live page sitemap inspected
• ISC-10: Sitemap duplicate counts computed
• ISC-11: Live REST users endpoint inspected
• ISC-12: Live contact page inspected
• ISC-13: Live readme exposure inspected
• ISC-14: Local redesign prototype inspected
• ISC-15: Audit document created in project root
• ISC-16: Audit document lists prioritized findings
• ISC-17: Audit document includes implementation plan
• ISC-18: Audit separates current facts from stale memory
• ISC-19: Audit avoids credential values
• ISC-20: Verification evidence recorded in PRD

Decisions

• Create a new current audit document rather than overwrite prior iqon-design-audit.md.
• Treat prior WP 4.9.13 claim as historical until core version is separately confirmed.
• Recommend static/light redesign path unless WordPress editing must remain a hard requirement.

Plan

1. Create a current audit markdown document in the project root.
2. Separate verified live findings from stale/historical memory.
3. Prioritize quick hardening, SEO/accessibility cleanup, and full redesign work.
4. Include verification commands and expected signals for each phase.

Capability Tracking

• [INVOKED] OpenDesign design-review — read /Users/svmac/development/open-design/skills/design-review/SKILL.md.
• [INVOKED] OpenDesign frontend-design — read /Users/svmac/development/open-design/skills/frontend-design/SKILL.md.
• [INVOKED] Live HTTP inspection — checked homepage, headers, sitemap, REST, contact.
• [INVOKED] Local repository inspection — checked memory, old audit, root and new redesign.
• [INVOKED] Targeted audit document editing — create current audit artifact.

Verification

• test -f iqon-full-audit-2026-05-19.md exited 0.
• rg -n "P0|P1|Phase 1|Phase 3|Open Design|WordPress 4\\.9\\.13|66 URLs|29 sitemap|3 duplicated|admin|iqnadm01" iqon-full-audit-2026-05-19.md returned expected audit sections and evidence lines.
• rg -n "password|парол|token|secret|Ds7|Dih|TTSQ|credential" iqon-full-audit-2026-05-19.md exited 1, confirming credential terms/substrings are absent.
• python3 -c document check returned has_purpose True, has_toc True, has_plan True, has_dates True.