Top pressing items

• Google Ads PMax status drift is pressing because yesterday's automation memory carried Pmax 2026 as paused, but live NotFair readback on 2026-06-07 shows it enabled with a $200 daily budget and $32.70 spend today. Evidence: NotFair listConnectedAccounts, summarizeAccountSetup, and read-only runScript. Safest next action: keep this as approval-gated Ads review, no mutation from this automation.
• SAIL KB follow-up backlog is rising. The live helper returned 220 Needs Follow-up at 2026-06-07T11:26:58Z, up from 208 on June 6 and 189 on June 5. Evidence: /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py. Safest next action: patch the Daily Pulse display reconciliation and add a triage shortlist, both non-destructive but still held as workflow changes.
• Repo-health has a current checkpoint problem, not missing checkpoint support. Evidence: today's repo-health page says the local runner timed out because the checkpoint is 7 days stale; local readback confirms RUNNER_USE_CHECKPOINT and RUNNER_CHECKPOINT_PATH exist, while /Users/samaguiar/Documents/Codex/repo-health/run-state/repo-health-latest.json is absent today. Safest next action: chunked resumable checkpoint refactor, no repo-level writes until approved.
• Website QA has a live audit load that should stay staged only. Evidence: Sunday Site QA scanned 547 pages, found 525 findings on 358 pages, including 14 missing .sa-sidebar, 299 title and H1 mismatches, missing hero blocks, FAQ schema gaps, link gaps, and one duplicate meta page. Safest next action: draft remediation plan with sampling, no public design or post_content changes.
• Write-lane and ENOSPC drift is still blocking scheduled website/content work. Evidence: June 7 Twice-Daily SEO run stayed research-only for the second consecutive run, and Daily Pulse reports multiple write-heavy tasks blocked while cleanup reclaimed 4.71 GiB. Safest next action: shared disk preflight and cleanup path for write-heavy routines.
• Rank Math vulnerability should stay closed, not carried as a blocker. Evidence: live WordPress REST plugin read shows Rank Math SEO active at version 1.0.271.1 and Rank Math SEO PRO active at 3.0.111. Safest next action: monitor only unless newer evidence reopens it.
• Nick Attorney Hub launch should stay closed. Evidence: live Salesforce metadata lists Nick_Attorney_Hub_Agent plus Jon_Hollan_Attorney_Hub_Agent. Safest next action: describe future work as enhancements, not launch blockers.

Likely forgotten or unfinished

Operations and Notion

• Status: unfinished. Daily Pulse headline reconciliation is still open. Owner visible: scheduled Daily Pulse workflow. Why unfinished: today's page shows total 505, displayed sub-counts summing to 494, and a recommendation to patch build_report.py.
• Status: unfinished. Skills scheduled mirror sync has 2 policy items open. Owner visible: scheduled mirror-sync workflow. Why unfinished: all mirrors are byte-equal, but discover_unmapped_partials.sh is missing and skills-scheduled-mirror-sync is not drift-guarded in its own mirror map.
• Status: unfinished. Needs Follow-up backlog cleanup is not keeping pace. Owner visible: operations automation. Why unfinished: live count increased to 220 despite prior consolidation to 182 on June 4.

Google Ads and Attribution

• Status: needs review. PMax is enabled and spending today. Owner visible: Google Ads account user aguiarlawmarketing@gmail.com in recent changes, but PMax enabling cause was not isolated in this run. Why unfinished: the current state conflicts with yesterday's carried paused status.
• Status: monitored, not blocked. GCLID propagation completed cleanly today. Owner visible: Litify attribution runner. Why unfinished: Google Ads sheet lane remains dry-run only, and CallRail to Intake matching still needs upstream review for recycled-phone cases like Gabriel Perez.

Website and SEO

• Status: staged audit pending. Sunday Site QA findings need triage. Owner visible: website QA routine. Why unfinished: 525 findings exist, but live remediation is approval-gated and must avoid design reversions or direct published post_content writes.
• Status: research-only blocker. Twice-Daily SEO run is blocked by disk and JS lanes for a second consecutive run. Owner visible: programmatic SEO routine. Why unfinished: write lane is not healthy enough to create WordPress drafts.

Repo Health