Run time: 2026-05-31 07:43 EDT.

Connector status: Notion connector used first against collection://13d5d9db-4588-41bc-afa9-45ce9e23e56c. No fallback mirror was used.

Live backlog count: 241 Needs Follow-up, verified through /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py at 2026-05-31T11:27:39Z from live_notion_status_query. I did not infer this from search counts. The local daily pulse, generated a few minutes earlier, reported 240 at 2026-05-31T11:20:28Z, so the current source of truth is 241.

Top pressing items

• Sunday Site QA found 7 published noindex pages and 401 total findings across 542 scanned URLs. Reason pressing: noindex on published pages can directly remove pages from Google, and the Sunday QA page marks this as severity 5. Evidence: Sunday Site QA - 2026-05-31. Safest next action: stage a Rank Math metadata-only repair for the 7 noindex pages first, with rollback notes, then re-run the crawl before touching broader H1/sidebar findings.
• Daily Morning Briefing is still device-dependent while its cloud migration and Teams/iMessage delivery repair have been approved but not executed. Reason pressing: the latest briefing itself created follow-up decisions, and the architecture note says the task still depends on a specific Mac unless moved to a Cloudflare Worker plus fallback channel. Evidence: Session export: Daily Morning Briefing skill rewrite (2026-05-29), Daily Briefing: device-independent architecture + backup plan (2026-05-31), and Daily Briefing 2026-05-31. Safest next action: in a Mac/Codex session, back up the live task, deploy the approved rewrite, then build the Worker path with Notion as the source of truth and SMS or Mac relay as the mobile fallback.
• Litify and CallRail attribution are still the most operationally risky data-quality lane. Reason pressing: the 2026-05-30 GCLID audit reports a CallRail email saying Google Ads integration failed and cannot send or receive data until reactivated, while the webform lane still has the INT-26042754516 conflict. Evidence: Daily Litify GCLID propagation audit - 2026-05-30, Live Website Form Parity Audit, Litify and Email Intake Routing, 2026-05-30, and Webform Lead 83-86 Graph and Litify Diagnostic - 2026-05-30. Safest next action: verify CallRail integration live, reactivate only if confirmed, quarantine or resolve INT-26042754516, and add a reconciliation monitor for direct Litify Services intakes, blank source fields, and Junk-routed lead emails.
• Daily Briefing operational items need separation from automation architecture work. Reason pressing: today's briefing lists concrete business follow-ups: CallRail access to the Google account, an expiring billing card, Maidens MRI records, 9 null-stage Litify matters, and Google Ads spend with Pmax at $246.97 and 0 conversions. Evidence: Daily Briefing 2026-05-31 (Sunday). Safest next action: keep these as operational follow-ups, not as proof the briefing automation itself is fixed.
• Monthly Dedupe and skills mirror-sync have a real Mac-only execution gap. Reason pressing: one page says the monthly dedupe core work is staged, but the injector must run against Mac-side skills, alert IDs are pending, and scheduler repointing is not done. Mirror-sync similarly cannot push post-run-qa-reflection and sail-kb-daily-pulse from cloud without reading the real Mac content. Evidence: Session Export: Monthly Dedupe deployment + scheduled-skill self-audit rollout and Session: executed 3A/4A + partial 2B on mirror-sync (2026-05-30). Safest next action: execute from the Mac context, not by reconstructing missing canonical files from memory.
• Rank Math vulnerability status needs live verification before downgrading. Reason pressing: the 2026-05-30 infra pulse flagged Rank Math free v1.0.270 as vulnerable and recommended staging-first patch to v1.0.271.1; the 2026-05-31 infra pulse reports healthy production but does not explicitly say the vulnerability was patched. Evidence: Infra Daily Pulse - 2026-05-30 (ATTENTION: Rank Math vuln) and Infra Daily Pulse - 2026-05-31 (QA: Open). Safest next action: verify current plugin version from the live WordPress/Cloudways source before treating it as closed.

Likely forgotten or unfinished

Website and SEO

• Status: Needs Follow-up. Owner not visible. Sunday Site QA has 7 noindex published pages, 14 missing-sidebar findings, 237 title/H1 mismatches, 47 missing FAQ schema findings, and 56 low-link pages. The noindex set is the clean first repair lane because it is small, high severity, and metadata-only.
• Status: Needs Follow-up. Owner not visible. Sitewide Call Now button verification confirmed one real unreadable white-on-white button case on Bullitt County and says the 323-page count is unreliable. It still needs a rendered-button classifier crawl before a global CSS fix.
• Status: Needs Follow-up. Owner not visible. Ahrefs/GSC Weekly SEO Pulse reports GSC still unlinked for the fourth week, Brand Radar unavailable on the current plan, Rank Tracker at 0 keywords, 7 new orphan pages, and 8 new 404/4XX URLs.
• Status: needs verification. Owner not visible. Rank Math vulnerability from 2026-05-30 may or may not be resolved; today's infra page does not explicitly close it.

Litify, intake, and attribution

• Status: Needs Follow-up. Owner not visible. INT-26042754516 is still the webform conflict blocking safe propagation.
• Status: Needs Follow-up. Owner not visible. CallRail Google Ads integration failure alert needs live verification and repair if confirmed.
• Status: Needs Follow-up. Owner not visible. Website lead emails #83-#86 landed in Junk even though Graph delivery and Litify creation succeeded. Teams integration failed with HTTP 400. No mailbox rule was found, so mail-flow or safe-sender handling is still open.