How to read this

Five items below. For each, option A is my recommendation. Reply with the letter for each item (e.g., "1A, 2B, 3A, 4C, 5A") and I will act on them in the next run.

1. Word count on the three drafts (2,070 / 1,915 / 1,645 words vs 3,000-word default target)

The drafts are tight, well-cited, and on-brand. The target is 3,000 words for AI discoverability + authority. Meniscus is the furthest off.

• A. (Recommended) Expand all three to 3,000+ before publish. I add 2-3 H2 sections per page (case examples, KY-specific evidence rules, settlement-range guidance with citations), keeping brand voice and citation standards. Adds ~30 minutes to next run.
• B. Expand only Meniscus (the shortest), publish the other two as-is.
• C. Publish all three as-is. They are clean and cited; length is not law.
• D. Other (tell me).

2. Meniscus slug collision (meniscus-tear-car-accident already taken by legacy draft 61876, new post forced to -2)

• A. (Recommended) Delete the legacy draft 61876 and re-slug 66481 to meniscus-tear-car-accident so the canonical URL is clean. The legacy draft has been sitting unpublished; the new content is more complete.
• B. Keep both drafts. Publish 66481 at meniscus-tear-car-accident-2 and let SEO sort it out.
• C. Move new content into 61876 (preserve the older post ID and history), delete 66481.
• D. Other (tell me).

3. wp-content-deployer skill update (initial deploy created posts with empty content)

Root cause: Get-Content -Raw + Invoke-RestMethod -Body $bodyBytes produced an empty content.raw server-side. Fixed by switching to [IO.File]::ReadAllText + ConvertTo-Json -Compress + [Text.Encoding]::UTF8.GetBytes.

• A. (Recommended) Update wp-content-deployer to use the ReadAllText + Compress pattern, and add a post-deploy verify step that re-reads content.raw and fails the run if it is empty. Prevents silent empty-content deploys going forward.
• B. Update the skill to use the new pattern but skip the post-deploy verify.