Importance: Medium. A visible bug (invisible CTA headline line) on one live, published blog post. Now fixed and verified. No other page was affected.

Status: Complete. The optional preventive follow-ups below are pending your approval and are not blockers.

What was done

• Diagnosed the broken "Focus On Healing. / We'll Handle The Rest." sidebar CTA on the NTSB UPS Flight 2976 post (ID 70405). The second line rendered white-on-white and was invisible. Selecting the text made it reappear because the selection highlight forces contrast, which is exactly what the two screenshots showed.
• Root cause: the CTA was rebuilt 2026-06-06 as a white card. The rebuild added inline color:#0B212D !important to the h3, the paragraph, and the CALL NOW link, but not to the second-line <span>. The page still carries a stale sitewide rule .sa-sidebar-cta * { color:#ffffff !important; } (leftover from the deprecated dark-navy CTA). With no inline color, that rule won and the span went white on the white card. Confirmed in a live browser: computed color was rgb(255,255,255).
• Fix: added color:#0B212D !important to the span's inline style. One-line surgical change, pushed via the WP REST API. The post stayed published because the live page was the broken one. Verified live: span is now rgb(11,33,45) navy, heading centered, on desktop (1280px) and mobile (390px). Link count unchanged (22 to 22), content still wrapped in wp:html. Original content backed up before the push.
• Blast-radius scan: queried every page and post using this CTA (18 total). The NTSB post was the ONLY one with a color-less span; all others already carry an inline color. Nothing else needed fixing.
• Registry: updated Web Design Elements Library v1 (element #10, Sidebar CTA) with a Known Issue + canonical rule + changelog entry. Canonical rule: every text child of a white-card .sa-sidebar-cta must carry its own inline color; the second-line span must be <span style="display:block !important;color:#0B212D !important;">.

Why the session ended

The requested work is complete and verified. Ending normally.

Recommended next actions (optional, your call)

1. Patch the sa-sidebar-option-b skill so its heading markup ships the span color inline. I could not edit skills from this session (skills are read-only here and are edited via Settings > Capabilities). Once that one line is in the skill, new pages inherit the fix automatically.
2. Add a pre-publish-qa guard that FAILs any .sa-sidebar-cta text child (h3 span, p, a) lacking an inline color. This catches the leak no matter which stale sitewide rule is present.
3. Optional sitewide hardening: scope or retire the deprecated .sa-sidebar-cta * { color:#fff } rule so white-on-white cannot happen even without inline colors. Slightly higher risk because some older pages may still use the dark-navy CTA variant where white text is correct, so it needs a carefully scoped selector.

Handoff for the next agent

The live fix is done and verified; no urgent follow-up. The canonical corrected markup and full diagnosis are in Web Design Elements Library v1 under the new "Known Issue + Canonical Fix" section. Note: the element's real code lives in the sa-sidebar-option-b skill, not in the older sa-template-reference Notion page (that page still documents the deprecated dark-navy sidebar CTA and was not the source of this element). WP REST credentials are in wp-content-deployer. Pre-fix and fixed copies of post 70405 are saved in the session working folder (post_70405_backup.html, post_70405_FIXED.html); rollback is a one-line revert if ever needed.

Update — SA Element Registry hardened (2026-06-09, same session)

The actual runtime source of truth is the SA Element Registry (Render app, https://sa-element-registry.onrender.com), operated via the sa-element-registry skill — not the skill files or the Notion doc. Fixed it directly there.

• Found the CTA lives in four sidebar elements: id 17 (Option A), 18 (Option B), 70 (Option C), 71 (Option D). All four had the same fragility: the second-line heading span .cta-l2 had only display:block and no color, so it inherited its color and went white on any page still carrying the legacy .sa-sidebar-cta *{color:#fff !important} rule.
• Hardened all four via POST /admin/edit: changed .cta-l2{display:block;} to .cta-l2{display:block;color:#0B212D !important;}. The element selector (.sa-sidebar-opt{x}-poppins .sa-sidebar-cta h3 .cta-l2) outranks the legacy .sa-sidebar-cta * rule on specificity, so the navy now wins even with both marked !important. Bumped each to version 2026-06-09 and added a rule note.