Summary of work done

Applied the 6 update_ready Google LSA CallRail_Call_Log__c to Intake__c links from the rollback-safe dry run. Verified each exact Salesforce row live after the write. Traced the 37 skip_no_phone_match rows from the same baseline to separate true blockers from unsafe backfill candidates.

What shipped

• Ran node scripts/backfill-lsa-callrail-intake-links.mjs --start-date 2026-04-29 --apply against LITIFY_ORG
• Verified all 6 target call-log rows now carry the intended Intake__c
• Re-ran the same-scope dry run and confirmed the queue changed from 56 blank rows with 6 update_ready to 50 blank rows with 0 update_ready
• Updated the workflow doc and Litify diary with the live apply result, rollback artifacts, and blocker classification

What has not shipped

No loose-match backfill was applied. The remaining 50 blank rows still include 37 with no same-phone Intake, 11 mismatch rows, 1 multiple-candidate row, and 1 generic-source review row.

Verification

Exact post-apply SOQL verification passed for these six rows:

• CRAIL-26052614071 -> a0CUV00006j3ecX2AQ
• CRAIL-26052113852 -> a0CUV00006j3vma2AA
• CRAIL-26052113829 -> a0CUV00006fAfrd2AC
• CRAIL-26051413519 -> a0CUV00006XMePB2A1
• CRAIL-26051113355 -> a0CUV00006ZrFTY2A3
• CRAIL-26043012973 -> a0CUV00006TXFuE2AX

37-row blocker trace

The skip_no_phone_match set is not one bug:

• 11 generic caller or location labels such as WIRELESS CALLER and LOUISVILLE KY