Summary of work done

• Confirmed this is a content-source issue, not a CSS transform issue. The live post content for 10-mistakes-to-avoid-after-an-accident stores lowercase Related Resources labels directly in HTML.
• Ran a live authenticated WordPress audit across published posts and pages. Flagged 24 published URLs where at least one related-link label starts with a lowercase letter.
• Updated the local SA content guardrails so future pages stop shipping raw lowercase keyword-style related-link labels.
• Wrote the live-scope audit to admin/session_logs/related-content-casing-audit-2026-05-18.md.

What has shipped and what has not

• Shipped: skill and QA guardrail updates in the Projects workspace.
• Shipped: local audit log with the 24 affected URLs.
• Not shipped: no live WordPress content changes were made in this session.

Root cause read

• Recent and older page-generation patterns are using keyword-style labels in related blocks instead of destination page titles or clean headline-case labels.
• The current skill stack already enforced the canonical heading pattern, but it did not explicitly fail lowercase related-link labels until this session.

Suggested next steps

• Build a batch remediation pass that replaces each affected related-link label with the target page title or a curated headline-case label.
• Start with the 24-page affected set from the audit log and verify each replacement against the destination page title before any live write.
• If desired, widen the audit to catch title-case drift in other link clusters beyond Related Content blocks.

Handoff for a new agent

• Use admin/session_logs/related-content-casing-audit-2026-05-18.md as the live target list.
• The key internal files updated are Skills/sa-web-content-creation/SKILL.md, Skills/sa-template-reference/SKILL.md, and Skills/pre-publish-qa/SKILL.md.
• Do not blindly uppercase the first character only. Normalize related-link labels to the destination page title or a clean headline-case label.