Top pressing items

• Salesforce SOAP API deprecation is now the most time-sensitive Litify item. Evidence: Daily Morning Briefing, 2026-06-05 and Daily Briefing, 2026-06-04 both report Salesforce email warnings for SOAP API v31 through v64 login activity in May. Live check: sf is connected to LITIFY_ORG; a newest-2,000-row LoginHistory sample found 0 rows below API 65, but that sample is not exhaustive for May. Safest next action: run a deeper read-only trace through EventLogFile, Setup Audit Trail, connected app inventory, or Salesforce support evidence before touching any integration.
• June 5 GCLID propagation runner needs recovery verification, but the attribution command lane is not globally broken. Evidence: Daily Litify attribution GCLID propagation, 2026-06-05 says that session could not execute the local runner. Counter-evidence: the canonical local runner completed on June 4 at /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/output/gclid-propagation-automation/daily-2026-06-04T18-02-54-693Z/daily-gclid-propagation-report.json, with status: completed, blockers [], 2 CallRail GCLID updates applied, webform conflict count 0, quarantine count 1, Google Sheet sync applied, and hosted status synced. Safest next action: rerun the canonical runner for June 5 before making Salesforce attribution writes.
• Google Ads access is healthy, but Litify upload conversion readback is still unresolved. Evidence: NotFair listConnectedAccounts returned account 3813916687; summarizeAccountSetup confirmed auto-tagging enabled and the Litify upload conversion actions exist; read-only runScript at 2026-06-05T11:27:47Z returned no Litify - Converted Intake (Web Form) or Litify - Signed Retainer (Web Form) conversion-action rows for the last 30 days. Safest next action: keep Data Manager or direct-upload QA open, but do not upload conversions or change spend from this automation.
• Google Ads performance watch needs a decision, not an autonomous budget edit. Evidence: same NotFair readback showed June 4 spend of $442.66 with about 1 conversion overall; Spanish campaign spent $133.22, 3 clicks, 0 conversions; search terms over 7 days still show generic zero-conversion spend including attorneys in louisville, lawyers ky, top litigation law firms, and 24 7 lawyer hotline. Safest next action: keep negative-keyword cleanup and Spanish budget changes in the briefing decision lane.
• Lexington SEO remains approval-gated. Evidence: Lexington SEO canonical page remains the newest relevant source; it reports the canonical car page and redirect/cannibalization strategy. Safest next action: stage a redirect and broad-PI reposition plan, but do not execute 301s or live content edits here.
• Orange design drift remains governance work before page work. Evidence: Orange drift source prompt, orange source map, and Weekly Orange-BG sweep. Safest next action: update stale validators and skills with rollback before any draft-only visual remediation.

Likely forgotten or unfinished

Operations

• Live KB backlog: 189 Needs Follow-up pages at 2026-06-05T11:26:16Z from /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py, source live_notion_status_query. Status: active tracking. It is up 7 from the verified post-triage count of 182 on June 4.
• Repo-health: checkpoint support should not be reopened. Evidence: local rg found RUNNER_USE_CHECKPOINT and RUNNER_CHECKPOINT_PATH in both /Users/samaguiar/Documents/Projects/Skills/daily-repo-health-check/repo-health-runner.sh and /Users/samaguiar/Documents/Claude/Scheduled/daily-repo-health-check/repo-health-runner.sh. Status: remaining work is chunking/timeouts and dirty-tree coordination.
• Daily briefing decisions: today’s briefing is Needs Follow-up and includes Salesforce SOAP tracing, billboard inventory, shoot footage background, Spanish campaign efficiency, and optional pre-publish QA for the Nursing Home hub.

Attribution and Google Ads

• GCLID command lane: June 4 machine report is healthy, but June 5 runner execution failed in another session. Status: Needs Follow-up until the June 5 canonical runner writes a fresh machine report.
• CallRail Google Ads OAuth: remains Needs Follow-up under the attribution command center unless a newer verified repair page appears. Do not merge this with CallRail API health or local CallRail GCLID recovery.
• Litify upload conversions: Needs Follow-up. The conversion actions exist, but Ads readback did not show Litify upload conversion rows in the last 30 days.
• PMax: setup snapshot shows Pmax 2026 is paused, consistent with today’s briefing and the June 4 PMax pause review. No spend mutation was made.

Litify and Salesforce

• Nick Agentforce: closed, not a launch blocker. Evidence: live sf org list metadata --metadata-type Bot --target-org LITIFY_ORG --json returned Nick_Attorney_Hub_Agent, and the canonical closure remains Nick Attorney Hub Agentforce deployed and verified, 2026-06-01. Future work should be hub enhancement or safeguards.
• Salesforce SOAP API deprecation: Needs Follow-up. The warning is current, but the caller identity is not yet isolated.