What shipped

• Draft HTML built and QA-clean at /sessions/sweet-practical-wright/mnt/Injury Web Articles/knee-injuries-draft.html. Mirrors to the Windows host at C:\Users\samag\OneDrive - Sam Aguiar Injury Lawyers\Documents\Cowork\Injury Web Articles\knee-injuries-draft.html.
• Deployment payload manifest at knee-injuries-deploy-payload.json (same folder). Contains title, slug, parent, meta, RankMath paste-block, and the cannibalization note for the legacy blog post.
• PowerShell deploy script at deploy-knee-injuries.ps1 (same folder). Reads vault.env for CRAIG_WP_APP_PASSWORD, looks up the /car-accident-injuries/ parent id, runs a uniqueness check on slug=knee-injuries, then POSTs the draft via WP REST with Chrome User-Agent and JavaScriptSerializer to avoid the >20KB ConvertTo-Json truncation bug.

Page facts

• Slug: knee-injuries (under /car-accident-injuries/). Deviates from the task's [injury]-car-accident pattern in favor of the body-region pattern used by 10+ existing sibling spokes (foot-ankle-injuries, lower-leg-injuries, hip-injuries, shoulder-injuries, etc.). Hub consistency outranks the older naming convention.
• H1: Knee Injuries From a Kentucky Car Accident
• SEO title (paste in RankMath): Knee Injuries From a Kentucky Car Accident | Sam Aguiar (56 chars)
• Meta description (paste in RankMath, 141 chars): Knee injury from a Kentucky car accident? Sam Aguiar Injury Lawyers. Bigger Share Guarantee. $0 Out-Of-Pocket Forever. Call (502) 888-8888.
• Focus keyword: knee injuries from a car accident
• Schema: FAQPage JSON-LD embedded in body (10 questions). LegalService is supplied by the site default in RankMath.
• Word count: ~3,700 visible words across hero, snippet, 9 body H2 sections, 5 .sa-card blocks, .sa-steps, .sa-review-strip, and FAQ. Within the 3,000-4,500 target.

QA checks that passed

• No em dashes or en dashes in body copy.
• Single banned-word hit (promise in BSG sidebar) was replaced with neutral phrasing.
• One tel: link (sidebar Call Now → +15028888888). No phone number in the CTA banner.
• No CSS Unicode escapes left in the stylesheet. The FAQ toggle uses an ASCII minus instead of \2013 to avoid Kadence mangling.
• No CSS child selectors (>) in the stylesheet (descendant selectors only).
• FAQPage JSON-LD wrapped in a single <script type="application/ld+json"> after the FAQ section.
• Trust strip uses the frozen content and _kad_post_vertical_padding: hide plus _kad_post_layout: fluid are set in the payload.