Daily KB follow-up and drift scan - 2026-06-10

Top pressing items

PMax is still live and spending, reason pressing: older notes treated PMax as paused, but live NotFair setup now shows Pmax 2026 ENABLED with $200 daily budget. Evidence: NotFair summarizeAccountSetup at 2026-06-10 plus campaign-specific getChanges showing enableCampaign on 2026-06-05, not rolled back. Read-only GAQL at 2026-06-10T11:28:50Z showed $2.10 spend today and $170.91 yesterday with 2 conversions. Safest next action: keep as approval-gated Ads decision, no mutation from this automation.
VM/session ENOSPC remains the main write-lane blocker, reason pressing: pSEO and SEO audit tasks are blocked by the session overlay, not Sam's Mac disk. Evidence: 2026-06-10 Daily Pulse says sandbox root is 97 percent used with about 330 MB free, while local df -h showed 118 GiB available on this Mac. Safest next action: migrate pSEO and SEO audit write lanes to cloud or Codex lane with low-disk preflight.
GCLID propagation still needs runner recovery, reason pressing: newest local command-lane JSON remains blocked-before-write and June 10 Notion says the exec surface blocked that day's runner. Evidence: local JSON /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/output/gclid-propagation-automation/daily-2026-06-09T10-21-59-041Z/daily-gclid-propagation-report.json reports missing config/webform-gclid-resolution-manifest.json; Notion page Daily Litify GCLID propagation audit blocked by exec surface on 2026-06-10. Safest next action: rerun from canonical cwd or update runner cwd handling, read-only until report is healthy.
KB backlog continues to climb, reason pressing: live helper returned 254 Needs Follow-up at 2026-06-10T11:26:55Z, up from 246 yesterday and higher than the same-day pulse count of 252. Evidence: /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py, source live_notion_status_query. Safest next action: add a 10-oldest or 10-highest-risk triage shortlist to the daily pulse rather than relying on aggregate counts.
Website QA and orange-background findings remain staged-only, reason pressing: read-only Notion scans show 16 orange-background pages and the Sunday Site QA backlog remains open. Evidence: Weekly Orange-BG Sweep - 2026-06-09 and Sunday Site QA - 2026-06-07. Safest next action: stage draft remediation and keep public website changes approval-gated.
Salesforce SOAP API deprecation trace remains unfinished, reason pressing: June 4 and June 5 warnings are not fully traced, but live org is connected. Evidence: sf org list --json confirmed LITIFY_ORG connected; recent Notion drift reports still carry the trace. Safest next action: deeper read-only trace using EventLogFile/LoginHistory/connected app evidence.

Likely forgotten or unfinished

Operations and Notion health

Status: open. Owner visible: automation/agents. The official backlog count is 254, and the Daily Pulse still marks four QA choices pending. It looks unfinished because the count is rising daily and the pulse does not yet emit a prioritized triage shortlist.
Status: open. Owner visible: automation/agents. Claude/Scheduled mirror still lacks kb_live_backlog.py, and its notion_paged_query.py remains older than the canonical Projects/Skills copy. It looks unfinished because the scheduled mirror is not fully self-contained.

Google Ads and attribution

Status: open, approval-gated. Owner visible: Sam/agents. PMax is enabled and spending after June 5 NotFair changes; no rollback was recorded. It looks unfinished because the KB still contains older paused-state context, while current readback shows active spend.
Status: open. Owner visible: agents. Litify upload conversion segment readback returned no rows for the last 30 days, while Google Ads has Litify upload conversion actions configured. It looks unfinished because attribution command-center work depends on separating import availability, CallRail OAuth, and Google Ads readback.
Status: open. Owner visible: automation/agents. GCLID propagation has a runner/cwd or manifest-path block, not a Salesforce write failure. It looks unfinished because the June 10 page says the runner could not execute and the freshest JSON is still the June 9 blocked-before-write report.

Website and SEO

Status: open, staged-only. Owner visible: website/SEO agents. pSEO remains halted after repeated ENOSPC failures. It looks unfinished because draft work exists, but deploy/write lanes are blocked.
Status: open, staged-only. Owner visible: website agents. Sunday Site QA and orange-background governance findings need staged remediation. It looks unfinished because the latest pages are read-only scans, not deployed fixes.

Litify and Salesforce

Status: closed for Nick launch, enhancement-only for future work. Owner visible: Litify/Salesforce agents. sf org list metadata --metadata-type Bot --target-org LITIFY_ORG --json confirmed Nick_Attorney_Hub_Agent exists, along with Jon_Hollan_Attorney_Hub_Agent. Older Nick launch blockers should remain historical unless newer evidence reopens them.