Top pressing items

• Litify attribution and GCLID propagation is still the top operational risk. Reason: today's run did not execute because local command execution dependencies failed, so no runner JSON or Salesforce write/read validation was produced. Evidence: Daily Litify attribution GCLID propagation, 2026-06-01, plus Outlook search showing Website Intake Lead #88 is visible. Safest next action: rerun the canonical automation once exec is stable, then validate against Litify, CallRail, and Google Ads before any writes.
• CallRail Google Ads attribution remains unresolved, but the failure scope is narrower than older notes implied. Evidence: 2026-05-31 attribution repair page says CallRail account/API health worked but GoogleAdword integration failed; current run confirmed the CallRail API account and companies are reachable, while public integration endpoints returned 404, so UI/OAuth verification is still needed. Safest next action: repair or reauthorize the CallRail Google Ads integration through the CallRail/Google OAuth lane, not via blind API changes.
• Sitemap health needs a same-day rerun before staying red. Evidence: the 2026-05-31 sitemap health page marked page-sitemap broken with 318 page URLs removed, but this run's live HTTP checks returned 200 XML for sitemap_index.xml, page-sitemap.xml, and post-sitemap.xml. Rank Math plugin version could not be verified because SSH rejected auth and public plugin files return 403. Safest next action: rerun the sitemap routine and fix the routine/GSC invalid_grant if the live sitemap stays healthy.
• Skills repo and mount reconciliation is high priority because it affects future agent behavior. Evidence: Tier 1 pushed 85 mount-only skills to branch reconcile/mount-to-repo-2026-05-31, Tier 2 is held to avoid overwriting repo-only sa-template-reference assets, and no hosted skill write lane exists yet. Safest next action: review/merge Tier 1, then do a per-file union for Tier 2.
• Google Ads follow-up is active, but NotFair access is not blocked. Evidence: listConnectedAccounts returned Sam Aguiar Injury Lawyers account 3813916687, summarizeAccountSetup succeeded, and read-only runScript confirmed 2026-05-31 spend of $419.15, 44 clicks, 0 conversions. Safest next action: keep pending negative/offline conversion decisions, but retire old NotFair quota or blocked-access language unless a newer verified failure appears.

Likely forgotten or unfinished

Litify and attribution

• Status: Needs Follow-up. Owner not visible. Daily GCLID propagation failed before the runner could execute, and ExactaCare/Guetter medical-email automation did not run on 2026-05-31. Why unfinished: both are operational automations with live-data consequences and no completed rerun page yet.
• Status: partially superseded. Multiple Nick Agentforce pages from 2026-05-31 still say publish timeout or missing bot metadata, but later pages on 2026-06-01 say Nick Agentforce deployed and verified and the easy-access hub update shipped. Why unfinished: older blockers should be consolidated into one current Nick Agentforce status page instead of all staying current.

Website and SEO

• Status: needs verification. Sitemap Health Check 2026-05-31 is red, but live sitemap HTTP is now green. Why unfinished: the routine may have had a transient fetch failure or stale auth, and GSC invalid_grant remains unresolved.
• Status: pending approval or productionization. Our Results enhanced mockup, Sam Cares redesign package, and Abogado Lexington full-bleed/Spanish SEO items still have follow-up status. Why unfinished: deliverables are staged or diagnostic, not confirmed live production closures.
• Status: likely superseded. Sitewide Call Now button verification from 2026-05-30 should be downgraded because the 2026-05-31 Call Now Button Contrast Live Recheck page verified a 17-URL live fix on desktop and mobile.

Google Ads

• Status: Needs Follow-up. Daily Briefing asks whether to block drivesafelouisville and build CallRail-to-Google Ads offline conversion import. Why unfinished: those are cost/conversion-policy decisions and should stay approval-gated.
• Status: active but not blocked. Weekly Google Ads Leverage still flags Spanish, Brand Protection, and Lexington performance issues. Why unfinished: data-backed follow-up exists, but no destructive or budget-changing action should be taken without approval.

Operations

• Status: Needs Follow-up. Monthly dedupe found 7.97 GB reclaimable and nested .git cleanup found 9 nested repos, but both require approval before deletion or structural cleanup. Why unfinished: potentially destructive cleanup was correctly staged, not applied.
• Status: Needs Follow-up. Repo-health has 11 open Dependabot PRs and large dirty trees, but checkpointing is present and should not be reported missing.