Merging a second agent's blog draft into an existing PR: verify claims against repo artifacts, including the dbt manifest

Two sessions wrote the same post; the user picked the newer local draft. Steps that worked: create a worktree on the PR branch (main checkout was shared), git mv the old post folder and cover to the new slug, copy the draft over, re-apply house rules (cover, date, colon lead-ins, plain hook), rebuild and measure Mermaid width (an LR flowchart with 6 labeled nodes rendered ~1470px; TD gave 409px). To verify a claim like '41 dbt tests', count test nodes in dbt/target/manifest.json: sum(1 for n in nodes.values() if n['resource_type']=='test'). Claims backed only by live warehouse queries (a sample barcode row) can't be checked from the repo; flag them rather than silently keeping them.