UPDATE 2026-06-12: known $25k coverage action reports

Sam clarified that the broader reports can stay, but the working action report should isolate Treatment matters with known damages above threshold where Litify shows known or minimum-known per-person BI coverage of $25,000.

Created two live-validated report cuts:

Each report folder contains CSV, summary JSON, Markdown report, HTML report, chart PNG, and raw live-read JSON.

Also created the focused working packet from the $20k+ report only: /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/analytics/insurance_update_letter_package_known_25k_20k_adjuster_ready_2026-06-12/ with 6 client folders and 12 Word docs. The $15k cut remains report-only because the added row is early-warning, not a generated-letter priority row.

Verification: live LITIFY_ORG preflight succeeded; Python compile passed; both CSVs were checked so every row has known/minimum-known coverage exactly $25,000; exact-term scan found no rejected internal leverage strings; focused packet DOCX scan found 12 Word docs and 0 rejected-string hits. No production Litify writes, Drive writes, portal writes, or adjuster communications occurred.

UPDATE 2026-06-12: calculated leverage metric removed from Trent report files

Sam rejected the internal leverage phrasing in the insurance packet/report outputs. Corrected locally and in this handoff: the calculated damages-versus-coverage metric is no longer present in the current Treatment queue CSV, Exacta/Aptiva provider CSVs, HTML/Markdown report, package manifest, local ops notes, or adjuster-ready Word packet.

Regenerated current outputs: /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/analytics/treatment_limits_pressure_quick_wins_2026-06-12/, /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/analytics/exacta_aptiva_treatment_review_2026-06-12/, and /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/analytics/insurance_update_letter_package_adjuster_ready_2026-06-12/.

Verification: live LITIFY_ORG preflight succeeded; Python compile passed; Treatment queue rebuilt with 64 Treatment matters, 17 $20k+ candidates, and 13 limits-pressure rows; Exacta/Aptiva verifier passed with 35 provider rows, 82 draft Litify update rows, and 35 no-send draft adjuster rows; exact-term search across source/docs/current analytics was clean; DOCX text scan found 26 Word docs and 0 rejected-string hits; Brandi Wilhite's sample letter and Exhibit A rendered cleanly.

Obsolete local generated folders removed: first-pass insurance package and stale June 3 quick-win snapshot. No production Litify writes, Drive writes, portal writes, or adjuster communications occurred.

UPDATE 2026-06-12: adjuster-ready packet correction after Sam review

Sam rejected the first generated packet as not suitable for insurance companies. Specific defects: Matter numbers appeared in outgoing enclosures, markdown/support notes were present, internal coverage-leverage fields were visible, the Exhibit A table had a Notes column, and Litify provider links leaked as raw HTML.

Corrected deliverable: /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/analytics/insurance_update_letter_package_adjuster_ready_2026-06-12/. This package contains 13 Trent client folders and 26 outgoing Word docs only. Each client folder has Insurance Update Letter.docx, Exhibit A - Medical Bills.docx, and an empty Supporting Documents to Attach/ staging folder. There are no .md, .url, or .txt files inside the adjuster-ready folder.

Content standard now applied: no Matter numbers, no Litify/internal fields, no calculated coverage-leverage metrics or internal coverage-assumption analysis, no notes column, and no HTML provider links in outgoing DOCX files. Exhibit A now shows claimant, date of loss, claim number, carrier, total medical bills, and a clean medical-bill table with Provider, Service Dates, Billed, Paid/Adjusted, and Balance Due. Letters use claimant/date-of-loss/claim-number proof-of-loss language and ask for tender of available limits or coverage confirmation where appropriate.

Verification passed: python3 -m py_compile scripts/generate_insurance_update_letter_package.py; regenerated 13 client folders; rendered Brandi Wilhite's letter and Exhibit A plus James Thomas's large Exhibit A stress sample to PNG; scanned all 26 DOCX files for MAT-, href, target=, internal coverage labels, internal leverage labels, Notes, Litify, matter number, and Matter: with no hits. No production Litify writes, Drive writes, portal writes, or adjuster communications occurred.