While fixing the pedestrian page, Sam asked to recolor the legacy orange. Investigation showed the legacy orange #F89C22 is NOT a single shared block (the verdicts block 68294 was already Foundry) but is embedded in ~483 items sitewide.

Done this session

• All 23 shared reusable blocks (wp_block) recolored to Foundry #D97706 via REST /wp/v2/blocks/{id} (each auto-revisioned = rollback). Verified 0 #F89C22 left in every block. Cloudflare purge_everything run. Backups in outputs/ped-fix/block-backups/.
  • Blocks: 27562, 40442, 40512, 40864, 40865, 40866, 40867, 40900, 40965, 40970, 41066, 41528, 42285, 42286, 42308, 42309, 42364, 42725, 43401, 43411, 45024, 68292, 68330 (sidebars, results strips, hero block, As Seen In, Us vs Other Firms, etc.).
• Pedestrian page 61283 already fully Foundry from the prior task.

Remaining (pending)

Carry legacy orange in post_content: 230 published pages, 135 published posts, 1 brb_collection, 1 kadence_element, 2 wpcode (+ 95 drafts, lower priority).

Sam's directive (2026-06-09)

Start from the SA Element Registry (https://sa-element-registry.onrender.com/, 77 elements catalogued). Treat legacy orange as a marker of a stale asset: replace the element in full with its current canonical registry version (don't just swap the hex), preserving verified firm data (results, reviews, regional phone in tel: href). Then run page batches.

Plan for the 365 page/post batch (registry-driven, triggers a sec-31 retroactive audit)

1. Per page: detect legacy-orange elements -> map to registry element (catalog saved) -> replace block in full with Foundry canonical -> preserve verified data.
2. Deploy via REST draft pipeline (no direct DB post_content writes), QA each, WP revision rollback.
3. Batches of 25, 10% Playwright/DOM QA sample per batch, stop on FAIL, Cloudflare purge per batch.
4. Good candidate for a scheduled/off-hours task to avoid colliding with other agents' jobs.

Artifacts (in Projects/_reports/ped-fix-2026-06-08/)

• MIGRATION-RUNBOOK-legacy-orange-to-foundry-2026-06-09.md
• legacy-orange-inventory-2026-06-09.csv (all IDs + type + status)
• registry-catalog-2026-06-09.json (77 elements id->name)
• block-backups/ (pre-change content for all 23 blocks)

Why paused here

Session context is high. Block migration (the proof batch) is complete and verified. The 365-page registry-driven full-element replacement is a large, high-blast-radius batch best run as a fresh focused/scheduled effort. Awaiting Sam's pick on run-now-batched vs scheduled vs dry-run-first (asked inline).