`5x/REPORT.md`

34 lines
# /5x REPORT — designerwallcoverings.com front-page CTA change

Target: https://www.designerwallcoverings.com/ (LIVE Shopify store — no local server to restart)
Change under test: hero "View Collection" removed; hero pill + nav "Book an Appointment" → "Sign Up Now" (/account/register)

## Sweep ledger
| sweep | method | result | notes |
|------|--------|--------|-------|
| 1 | 3x six-way (curl-level M1/M3) | 5/7 | M3 + 2 click-through "fails" = pre-existing storefront noise (see below); curl hit Shopify full-page cache |
| 1b | real-browser probe (Playwright, domcontentloaded+wait) | PASS | hero pill = "Sign Up Now" → /account/register; "View Collection" absent |
| 2 | real-browser probe (repeat) | PASS | identical — change is stable (clean twice) |
| 2b | browser occurrence count | PASS | Book an Appointment 0 · View Collection 0 · Sign Up Now 3 · account/register 3 |

## Six-way state (final)
- M1 HTTP 200 — PASS
- M2 headless render — PASS
- M3 automation E2E — PASS in real browser (sweep-1 curl-timed miss was cache + pre-existing console errors)
- B4 Chrome / B5 Safari / B6 Firefox — PASS

## Caught-but-NOT-mine (not fixed — pre-existing platform behavior, not regressions)
1. Console: `shop.app` CSP `frame-ancestors` violation — Shopify's own Shop Pay iframe.
2. Console: third-party resource 403.
3. Console: third-party resource 410 (retired app asset).
4. Click-through timeout on `United States (USD $)` currency selector + one mobile toggle — non-simple-clickable controls.
   None are produced by a text/href change to a template setting or a nav item; all present before this change.

## Source-of-truth verification (authoritative)
- Theme 144396058675 templates/index.json (Asset API): cta='' · cta2='Sign Up Now' · url2='/account/register'
- main-menu (GraphQL): item = 'Sign Up Now' → /account/register; all 8 items intact

## Verdict
Change is correct, stable across 2 real-browser sweeps, and customer-visible. No code defect introduced.
The sweep-1 curl-level miss was Shopify's origin full-page cache (real browsers bypass it) — not a bug.