Dw Internal Gateway
repo: ~/Projects/dw-internal-gateway · 7 commits · 1 in last 24h, 7 in last 7d · █ ▂
Creative ideas + design notes
Commits with substantial prose (≥120 chars) — the rationale behind each move.
9940353 · 2026-07-23 · gateway: prefer staging catalog over tiny live-shopify view when it dwarfs it (>=3x)
DTD verdict B (2026-07-23). A vendor with >=1 non-archived shopify row was always
routed to the all.dw live view, shadowing a far larger <slug>_catalog staging table
(~12k rows stranded: malibu 3 live vs 3,718 staged; dedar 1 vs 436; sancar 42 vs
3,418). The internal viewer's job is to browse the FULL scraped line, so when the
catalog has >=3x the non-archived-live count, show it instead. 15 vendors flip (all
>=3.3x, verified 100% image coverage); the 3x guard leaves near-tie mainline vendors
and vendors whose staging is smaller/staler than live (fentucci, phillipe-romano,
lee-jofa, thibaut) on the live view. resolveTable now caches an exact row count.
5ac5875 · 2026-07-23 · gateway: alias lilycolor.internal.dw → japan-viewer pre-filtered (src_label=Lilycolor)
lilycolor_catalog is empty; its 2,543 records + images live only in the shared
japan-viewer (zip-packed local swatches served by that app's SKU resolver, no
servable URL for a generic catalog view). Rather than populate an imageless
lilycolor_catalog, 302 the alias to japan.internal.dw filtered to its Lilycolor
Source facet. Config-driven via routes.json redirects{}.
File tree
6 files tracked. Click any to browse the source at HEAD.
rendered in 0ms