Daily Report: The state of the estate

0 PIM13 pages live0 tested in 24h0 passed0 failed Every finding → The daily status report → The runners report →
👁️ read the defects here⚠️ the failure waiting on a decision📝 the page’s test📄 the run’s report📋 the route in Aegis the page name opens the live page

PIM (preview) 0 of 13

Pages with a preview URL set, which is what makes a page a PIM page. They run only when somebody asks for a run, so they are never overdue and never appear in the tabs beside this one. They ARE part of the 13 — every tab on this page counts out of the same total. This is the list of what is being worked on rather than a list of anything wrong.

No page is in preview.

Live (no issues) 10 of 13

Pages that appear in neither of the next two tabs: a test is running against them, its last run was answered, and no defect is open. Counted out of all 13 live pages, the same total every tab here uses — including the 0 in PIM, which are live but run only when asked.

Page Type Platform Actions
/autumn-home-spoiler 🇬🇧 AI Landing Lovable 📋
/autumn-juggler 🇬🇧 AI Landing Lovable 📋
/autumn-sceptic 🇬🇧 AI Landing Lovable 📋
/collections 🇬🇧 Collections Shopify 📋
/emmasignature 🇬🇧 AI Landing Lovable 📋
/floor-clean-editorial 🇬🇧 AI Landing Lovable 📋
/floor-clean-problem 🇬🇧 AI Landing Lovable 📋
/memberoffer-summer 🇺🇸 LP Shopify 📋
/pages/ingredients 🇺🇸 Information Shopify 📋
/pages/memberoffer-summer 🇺🇸 LP Shopify 📋

Live (failed QA) 2 of 13

QA cannot vouch for these. Most are a failure nobody has triaged yet; the rest have nothing testing them at all — no test written, a stub that passes without checking anything, a draft waiting to be signed off, or QA paused by hand. The Why column says which.

Page Type Platform State Why Detail Actions
/floor-clean-education 🇬🇧 AI Landing Lovable Signed off Untriaged failure failed, nobody has triaged it ⚠️📄
/pages/about-us 🇺🇸 Information Shopify Signed off Untriaged failure failed, nobody has triaged it ⚠️📄

Live (with defects) 1 of 13

Known faults on the page itself, whoever is fixing them. These do not stop QA running — a page can carry a defect and still be tested every pass, so a page here may also be in the tab before this one.

Page Type Platform Open Worst Actions
/pages/completestarterkit 🇺🇸 LP Shopify 1 low 👁️ 📋
/pages/completestarterkit 1 open 📋 ×
lowBuy-box review-star block is a pointer-cursor control that throws a jQuery error and does nothing when clicked
found once · last seen 2026-10-02 18:09
What is wrong

The star-rating / 71.2K verified 5-star reviews block in the buy box (div.stars-img-review.click-scroll, 492x24, visible) carries the page's scroll-CTA class click-scroll but an empty data-target attribute (data-target=""). It renders with cursor: pointer, so it is presented to the customer as clickable, and clicking it does nothing except throw an uncaught JavaScript error.

Evidence

Measured on run of 2026-10-02, theme 191433212218 role main, viewport 1280x813.

  • The element: data-target is the empty string; getComputedStyle(el).cursor = pointer; bounding box 492x24, visible.
  • Clicking it (genuine DOM click, dispatched in page context) left window.scrollY unchanged at 1965 → 1965.
  • At that exact moment (19:08:21) the console threw:
Error: Syntax error, unrecognized expression: #
    at ae.error (theme.min.js:2:13542)
    at ae.tokenize / ae.select / k.fn.init.find
    at HTMLDivElement.<anonymous> (theme.min.js:2:152098)
    at HTMLBodyElement.dispatch

The delegated click-scroll handler concatenates '#' with the data-target value; with an empty target it builds the selector #, which jQuery cannot parse, so it throws before scrolling anywhere.

Two instances of this block exist on the page. One is the zero-size duplicate node the baseline documents in section 8.2; the other (492x24) is the one a customer actually sees and can click.

False positives ruled out
  • Not suppressed smooth scrolling. The smooth-scroll-to-instant patch was applied and document.documentElement.style.scrollBehavior set to auto before this measurement. On the same page load and with the same patch, the announcement-bar GET YOUR OFFER CTA — which uses the same click-scroll mechanism but a populated data-target="starterkit-product" — moved the page scrollY 0 → 2251 and reached the buy box. So the mechanism works; only the empty-target instance fails.
  • Not a click that failed to land. The click was dispatched in page context on the element itself, and it demonstrably reached the page's own delegated handler — that handler is what threw the selector error.
  • Not unreachable markup. The element measures 492x24 with a pointer cursor in the rendered buy box.
Impact

Minor. No money path is affected — add-to-cart, discount and checkout all work correctly on this route. The cost is a customer-visible control that looks clickable and silently fails, plus an uncaught exception on every such click. Likely fix is either to populate data-target (presumably a reviews section, which this page does not have) or to drop the click-scroll class and the pointer cursor from the rating block.