`rescrape-todo/glitter-walls.md`

37 lines
# Glitter Walls — Re-scrape TODO

**Status**: 237 affected SKUs, NO scraper-manager skill, catalog tables effectively empty for these SKUs.

## The problem
- `glitter_walls_catalog` has 16 rows total — well below the 554 GW products in Shopify and the 237 SKUs flagged dead.
- `glitter_catalog` has 121 rows but its SKU column is numeric IDs (e.g., `26048552`) — does NOT match the affected SKU format which is verbose-kebab `BUTTERFLY-GLITTER-WALLCOVERING-RAINBOW`.
- Only 3 of 237 partially match `glitter_walls_catalog` via ILIKE.

## Recommendation
Build a `glitter-walls-scraper-manager` skill.

**Vendor URL**: `glitterwalls.com` (no trade portal required — public catalog)
**Existing scaffolding**: `~/Projects/glitterwalls/` exists (DW microsite for this label). The vendor's public PDPs use slug URLs like `/products/butterfly-glitter-wallcovering` — the SKU format suggests the slug IS the SKU (downcased, no `-` → `-` substitution).
**Target DB table**: `glitter_walls_catalog` (already exists with proper schema).

## Affected SKU list
237 SKUs at `/tmp/glitter_walls_affected_skus.csv`.

Sample:
```
BUTTERFLY-GLITTER-WALLCOVERING-RAINBOW
GRUNGE-GLITTER-WALLCOVERING-MULTI
CRACKLE-GLITTER-WALLCOVERING-GOLD
CRACKLE-GLITTER-WALLCOVERING-CHAMPAGNE
FISHNET-SEQUIN-GLITTER-WALLCOVERING-LAVENDER
```

## SKU → URL mapping hypothesis
The DW SKU like `BUTTERFLY-GLITTER-WALLCOVERING-RAINBOW` likely maps to a vendor PDP at
`https://glitterwalls.com/products/butterfly-glitter-wallcovering-rainbow` (lowercase).
Worth one-shot HEAD-testing 5 SKUs to confirm the pattern before building the full scraper.

## Suggested next step
1. HEAD-test the slug pattern hypothesis on 5 SKUs.
2. If it works, write a Node script that walks all 237 SKUs, fetches each PDP, extracts `og:image`, writes to `glitter_walls_catalog.image_url`, then re-runs the swap-proposal logic.