Session Overview

Sam reported the commitments block on the Practice Areas page was visually broken, with the dark section starting around the middle of the viewport and the cards clipping off the right side. I treated this as a live website visual bug and used the reusable sa-commitments-grid, pre-publish-qa, playwright-visual-qa, sa-css-leak-guard, and WordPress deployment guidance.

What Was Completed

• Confirmed the target page is https://aguiarinjurylawyers.com/practice-areas/, WordPress page ID 48.
• Pulled authenticated REST edit content for page 48 before making changes.
• Used Playwright computed layout checks to identify the root cause: sitewide Additional CSS was overriding .sa-section-dark margins with !important, while the page still supplied left:50%, causing a double-shift.
• Updated the live Kadence custom CSS post 16458, not the page body, adding left: 0 !important and right: auto !important to the full-bleed dark-band allowlist.
• Added a mobile override so .sa-section-dark remains edge-to-edge on pages where Kadence keeps a 24px content gutter.
• Flushed WordPress object cache.

QA Evidence

• Public HTML contains the updated CSS.
• Playwright checks at 1280, 2048, and 390px found no horizontal overflow.
• Desktop: .sa-section-dark x 0, width 1280, grid x 50, width 1180, six cards.
• Wide: .sa-section-dark x 0, width 2048, grid x 434, width 1180, six cards.
• Mobile: .sa-section-dark x 0, width 390, grid x 20, width 350, six cards.
• Screenshots saved locally under /Users/samaguiar/Documents/Projects/admin/wp-repair-output/practice-areas-commitments-2026-05-30/.

What Was Tried And Did Not Work

• First SSH attempt using the older app SSH lane failed noninteractively. I switched to the Cloudways flexible SSH credentials from the vault.
• One WP-CLI update attempted to read the staged CSS from a remote /tmp path that was not present in that shell context. WP-CLI accepted the empty payload. I caught it immediately from the output, uploaded the prepared CSS to ~/codex-backups/wp-css-fix-2026-05-30/, restored the full CSS, and verified the live custom CSS post was populated again.

Rollback