Session overview

A live QA audit reviewed the SA website and element registry form surfaces on 2026-06-11. The session grounded findings in the current Projects rules, the live Flexible app path, and rendered browser behavior.

What was completed

• Confirmed live Cloudways/Flexible production context for site QA.
• Compared registry form snippets against actual rendered pages.
• Identified many registry Live or Beta entries that still looked mock-style rather than deployable.
• Confirmed rendered Chrome QA is the reliable proof path when static HTML or registry labels disagree.

What was tried and did not work

• Static HTML and registry status alone were not sufficient to prove deployability.
• Bundled Playwright Chromium was missing in the environment, so installed Chrome/rendered QA was the practical route.

Decisions and reasoning

• Treat published rendered pages as the source of truth for form deployability.
• Do not assume registry Live means a real production form contract exists.

Files, URLs, source systems, and artifacts

• Local rollout summary: /Users/samaguiar/.codex/memories/rollout_summaries/2026-06-11T17-33-35-F7RP-sa_site_and_registry_form_audit.md.
• Raw rollout: /Users/samaguiar/.codex/sessions/2026/06/11/rollout-2026-06-11T13-33-35-019eb7bf-1be7-77e0-98c3-cc563024e33d.jsonl.
• Source systems: live WordPress site, SA Element Registry, browser-rendered QA.

Rollback or recovery instructions

No live form writes are recorded in this backfill entry. For any future registry/form changes, use the deployment pipeline and rerun rendered-form QA before marking deployable.

Current state