backlog: catalog ItemList dead-code RESOLVED (38f6db1) — committed+verified, deploy gated

82a0b9b9fc0c1836028da71084a98f1a521071a7 · 2026-06-03 13:44:19 -0700 · Steve

Files touched

M YOLO_BACKLOG.md

Diff

commit 82a0b9b9fc0c1836028da71084a98f1a521071a7
Author: Steve <steve@designerwallcoverings.com>
Date:   Wed Jun 3 13:44:19 2026 -0700

    backlog: catalog ItemList dead-code RESOLVED (38f6db1) — committed+verified, deploy gated
---
 YOLO_BACKLOG.md | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/YOLO_BACKLOG.md b/YOLO_BACKLOG.md
index 821829f..b13e778 100644
--- a/YOLO_BACKLOG.md
+++ b/YOLO_BACKLOG.md
@@ -196,12 +196,11 @@ reversible local commit** marked `[x]` w/ hash, then ScheduleWakeup ~1800s.
   deploy.sh ran clean (lint+env-preflight+rsync+npm-ci+pm2-reload+smoke 200); verified live:
   1 clean canonical, sitemap +16, noindex on art-review, breadcrumbs, sr-only h1, og:site_name,
   twitter:card, autocomplete. CNCP win logged. **No longer pending.**
-- **FINDING (pre-existing, not auto-fixed):** the dedicated `/catalog` route (server.js ~L182)
-  serves catalog.html directly and never calls renderWithSEO, so catalog's rich ItemList
-  JSON-LD (the `if (slug==='catalog')` branch, ~L283) is **unreachable dead code** for the
-  `/catalog` URL. catalog shows 0 structured data. Fixing means either routing catalog
-  through renderWithSEO or moving the ItemList injection into the L182 route — a code-path
-  rewire I left for you (riskier than a loop edit; the if-branch touches catalog data load).
+- ✅ **RESOLVED — catalog ItemList dead-code** — `38f6db1` (DTD verdict B). Routed /catalog
+  through renderWithSEO then layered the SSR cards. Verified locally: /catalog now has 1
+  clean canonical + ItemList + Breadcrumb + 4 cards; /catalog.html also canonicals to
+  /catalog. **Committed + verified, AWAITING DEPLOY** (the `go` deploy was correctly
+  classifier-gated — needs explicit "deploy"). Run `/deploy` to ship `38f6db1` to prod.
 - **(optional, architectural — your call)** The `.html` URLs and clean URLs are both
   indexable (each self-canonicals to its own form). Truly ideal would be picking ONE form
   and 301-redirecting the other. Left untouched — that's a routing-policy decision for you,

← 38f6db1 TSD SEO: route /catalog through renderWithSEO (DTD verdict B · back to Thesetdecorator · backlog: catalog SEO fix DEPLOYED + verified live on prod 6130054 →