Sam asked to advance the Kathy Saved Mail to Litify project from the June 12 status review. The targets were scheduler proof, June 10 and June 12 formal digest runs, Drive/OCR resolution with duplicate-title and parent-folder validation, continued PIP-only write scope, and no new guarded Litify write batch without explicit approval.
The scheduler was checked first. The previous local automation id, kathy-mail-litify-backfill, was not present in the app automation registry even though the local TOML said ACTIVE. I created the app-level automation as kathy-saved-mail-litify-backfill, set it to ACTIVE, and updated the local TOML to match. The prompt was narrowed to review/dry-run mode and explicitly says no live Litify writes unless Sam approves the specific guarded batch in the triggering conversation or run instructions.
The June 10 and June 12 Kathy digests were rerun into formal run folders. June 10 is /Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-09-25Z, with 1 message, 101 parsed rows, and 96 high-value rows. June 12 is /Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z, with 1 message, 80 parsed rows, and 72 high-value rows. Both runs include RUN_MANIFEST.md, summary.md, CSVs, and JSON outputs. No Litify writes were made by either run.
I built a PIP-only Drive/OCR resolution artifact around selected June 10 and June 12 rows. The artifact is /Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z/DRIVE_OCR_RESOLUTION_STEP.md, with structured CSV and JSON sidecars. Cheryl Lucas resolved to the expected Drive parent chain and live PIP record, but the PDF is image-only and still needs OCR before any status candidate can be staged. T Asia Phillips resolved to text and claim number, but the Drive parent chain points to Bush, Andre 080225 and the Litify matter is closed, so it is a hard hold. Anita Beach and Brianna Burleigh resolved to valid parent folders and live PIP records, but both documents show open/no-payment conditions rather than exhaustion.
The existing Litify writer was run against the hold-only JSON at /Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z/pip_extracted_fields_hold_only_2026-06-16.json. The report at /Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/litify-insurance-update-2026-06-16T01-15-34Z-hold-only-dry-run/litify_insurance_update_report.json shows apply=false, records=[], litify_writes_attempted=0, and litify_writes_succeeded=0. A live SOQL readback of the four reviewed PIP insurance records confirmed their Status__c values are still null.
The Google Drive connector could fetch Cheryl's raw image-only PDF and confirm the exact Drive title and metadata, but plain text extraction returned empty. I tried the Adobe Acrobat OCR bridge using the connector file reference. The tool treated the file reference as a local path and failed because that path did not exist. This means the workflow still needs a reliable local-download or OCR adapter before image-only PIP logs can become status candidates.
Fetching the Notion enhanced markdown spec resource also returned a validation error, so this export uses plain Notion-safe markdown.
I kept every reviewed PIP row out of the write queue. Cheryl has the strongest apparent exhaustion candidate from title and parent folder, but the document body has not been OCR-confirmed. T Asia has a text and claim match, but parent-folder conflict plus a closed matter is too risky. Anita and Brianna are useful evidence, but not exhaustion candidates. The current write lane remains PIP insurance fields only on litify_pm__Insurance__c, and no --apply run occurred.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/automation.toml: updated local config to match the app-level automation id and dry-run prompt.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-09-25Z: formal June 10 digest run folder.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z: formal June 12 digest run folder and Drive/OCR pilot folder.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z/SCHEDULER_REGISTRATION_PROOF.md: app-level scheduler proof and repair details.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z/pip_drive_resolution_2026-06-16.csv: row-level Drive, parent-folder, OCR, and Litify resolution grid.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/2026-06-16T01-10-10Z/pip_extracted_fields_hold_only_2026-06-16.json: writer-shaped candidate file with every reviewed row held.
/Users/samaguiar/.codex/automations/kathy-mail-litify-backfill/runs/litify-insurance-update-2026-06-16T01-15-34Z-hold-only-dry-run/litify_insurance_update_report.json: writer dry-run proof, zero candidates and zero writes.