Ran a read-only live audit of location-page hero blocks against sa-copywrite-design v1.1.12. The audit used authenticated WordPress REST context=edit for all published pages under /locations/, plus Playwright Chromium visual and computed-style QA on a representative live sample.
The concern was partly right, but broader than the evidence supports. This is not a total location hero collapse. Out of 76 reviewed /locations/ URLs, 73 carry a recognizable split-family hero marker: 49 sa-split-results-hero, 21 cva-hero, and 3 sa-hero-loc-* custom split/form-side variants. Three pages do not carry a split-family marker: https://aguiarinjurylawyers.com/locations/, https://aguiarinjurylawyers.com/locations/kentucky/, and https://aguiarinjurylawyers.com/locations/louisville/motorcycle-accident-lawyer/.
Confirmed live issues: the /locations/ hub uses retired sal-hero, lacks a split-card marker, has legacy orange #F89C22 in hero scope, and uses banned breakpoint drift. The Kentucky page renders a plain sa-hero and visibly shows a phone number in the hero CTA, which conflicts with the current no-visible-phone-in-hero rule. The Louisville motorcycle location page renders a plain sa-hero, not a split-card family. The Louisville page is visually a custom form-side split, but source still contains retired sa-location-form-hero marker. The source audit found 69 pages with banned mobile breakpoint drift in hero scope, mostly 700px, plus 12 pages with unapproved hero font-weight source findings. Browser QA confirmed at least one real rendered font-weight issue: Danville cva-hero buttons computed at weight 800.
Browser QA did not confirm a live text-opacity regression in the sampled hero text. Sampled hero text rendered opacity 1, with white rgb(255,255,255) and Foundry orange rgb(217,119,6) where expected. The source-only opacity signal was treated as unreliable because overlay opacity and text selectors sit near each other in minified/source snippets.
Audit script created: /Users/samaguiar/Documents/Current Page Updates/tools/audit_location_heroes.js
Latest source audit JSON: /Users/samaguiar/Documents/Current Page Updates/audit-output/location-hero-regression-2026-06-15/reports/latest-location-hero-regression.json
Latest source audit CSV: /Users/samaguiar/Documents/Current Page Updates/audit-output/location-hero-regression-2026-06-15/reports/latest-location-hero-regression.csv
Latest Markdown report: /Users/samaguiar/Documents/Current Page Updates/audit-output/location-hero-regression-2026-06-15/reports/latest-location-hero-regression.md
Rendered sample QA: /Users/samaguiar/Documents/Current Page Updates/audit-output/location-hero-regression-2026-06-15/reports/latest-location-hero-rendered-sample.json
Screenshots: /Users/samaguiar/Documents/Current Page Updates/audit-output/location-hero-regression-2026-06-15/screenshots/
The session answered the immediate question with live evidence and created reusable audit artifacts. No live edits were made because the request was framed as verification and the findings include multiple page types that should be patched in a controlled proof-first pass.
A good next agent can use the generated report to patch one proof page first. Suggested proof order: fix the /locations/ hub hero because it is the clearest regression, then fix /locations/kentucky/, then fix /locations/louisville/motorcycle-accident-lawyer/. After the proof page passes desktop and 390px mobile QA, the same agent can batch-normalize breakpoint drift and font-weight:800 button styles across the split-family location heroes.
If a batch fix is approved, preserve rollback by pulling context=edit HTML backups for every page before update, patch in batches, purge Cloudflare, run the audit script again, and Playwright-check desktop plus mobile samples after each batch. A cloud version of this audit would be useful because location hero drift is exactly the kind of check that should be available to any agent without depending on this local folder.
Importance: High. Task status: verification complete, remediation pending.