Top pressing items

• Google Ads PMax is enabled and spending, which keeps yesterday's drift current. Evidence: NotFair listConnectedAccounts, summarizeAccountSetup, and read-only runScript on account 3813916687 at 2026-06-08T11:28:41Z showed Pmax 2026 enabled, $200/day, $9.01 spend today, 1 click, 0 conversions. Safest next action: read-only PMax audit and approval packet only; no spend mutation from this automation.
• Programmatic SEO is halted after the 10th consecutive ENOSPC failure. Evidence: Notion page 2026-06-08 Programmatic SEO Twice-Daily - HALTED says the 3+ failure rule triggered, 13 drafts and 3 blueprints are staged, and no further drafts should be produced before the environment is fixed. Safest next action: choose GitHub Actions migration or sandbox cleanup path; do not create a 14th draft.
• SAIL KB backlog is still rising. Evidence: /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py returned 232 Needs Follow-up at 2026-06-08T11:26:36Z, compared with today's Daily Pulse count of 230 and yesterday's drift-scan count of 220. Safest next action: keep using the live helper count and add a 10-oldest triage shortlist to make the backlog actionable.
• Repo-health has real follow-up, but not missing checkpoint support. Evidence: today's repo-health page says the checkpoint was rebuilt at Codex/repo-health/run-state/repo-health-latest.json; local runner files both contain RUNNER_USE_CHECKPOINT and RUNNER_CHECKPOINT_PATH; the current checkpoint exists with June 8 timestamp. Safest next action: address org-wide Dependabot config and runner ceiling as approval-gated repo-health work.
• Sunday Site QA created a large staged website backlog. Evidence: June 7 Sunday Site QA scanned 547 pages, found 525 findings on 358 pages, including 14 missing .sa-sidebar, 299 title/H1 mismatches, missing FAQ schema, link gaps, and 1 duplicate meta page. Safest next action: staged sampled remediation plan only; no live design reversal or direct published post_content edits.
• Salesforce SOAP API deprecation caller trace remains unfinished. Evidence: June 4 and June 5 daily briefings report Salesforce email warnings for SOAP API v31-64 logins detected in May; current Salesforce org is connected, but this run did not perform a deeper EventLogFile or connected-app trace. Safest next action: read-only caller trace before cutoff.
• Attribution is monitored, not globally blocked. Evidence: newest local GCLID report remains daily-2026-06-07T10-21-34-189Z/daily-gclid-propagation-report.json, status completed, blockers []; NotFair readback still shows no Litify offline conversion rows in the last 30 days. Safest next action: keep GCLID runner separate from Data Manager/offline conversion readback and CallRail OAuth.

Likely forgotten or unfinished

Operations and Notion

• Status: unfinished. Owner visible: Daily Pulse and KB drift workflows. Why unfinished: live count rose to 232 and today's Daily Pulse created four pending QA items, including ratifying the helper patch, low-disk preflight, triage shortlist, and mirror sync.
• Status: unfinished. Owner visible: skills-scheduled-mirror-sync. Why unfinished: June 7 run says 5/5 mapped mirrors are in sync, but notion_paged_query.py is drifted and unmapped, discover_unmapped_partials.sh is missing, and the mirror-sync skill is not covered by its own map.

Google Ads and Attribution

• Status: needs verification and approval packet. Owner visible: Google Ads account user aguiarlawmarketing@gmail.com in recent change events. Why unfinished: PMax is enabled again and spending, while the June 4 decision page still frames reactivation as approval-gated and measurement cleanup remains incomplete.
• Status: monitored. Owner visible: Litify attribution runner. Why unfinished: GCLID propagation is clean, but Google Ads offline conversion readback still has no Litify rows for the last 30 days, and CallRail Google Ads OAuth remains a separate open lane unless a newer page closes it.

Website and SEO

• Status: staged audit pending. Owner visible: Sunday Site QA routine. Why unfinished: findings are numerous and live remediation must use safe draft/deployer paths.
• Status: halted. Owner visible: programmatic SEO twice-daily. Why unfinished: repeated ENOSPC triggered the stop-and-rewrite rule; staged drafts have not shipped.

Litify and Salesforce

• Status: enhancement lane, not launch blocker. Owner visible: Litify/Salesforce agents. Why unfinished: Nick_Attorney_Hub_Agent exists, so Nick launch is closed; remaining work is other attorney hubs, dashboard/report advisor expansion, or document-generation safeguards.