Top pressing items

• KB backlog math is currently clashing inside the same morning. Why pressing: the daily pulse at 2026-05-25 11:07 UTC reported Needs Follow-up: 714, the weekly triage page at 11:24 UTC reported 651, and a live Notion SQL query during this run returned 652. Evidence: SAIL KB Daily Pulse - 2026-05-25, Needs Follow-up Triage - 2026-05-25, and a live structured query against the SAIL Knowledge Base. Safest next action: treat the weekly triage page plus live query as current, and patch the pulse so it reads post-triage live counts instead of carrying inflated backlog math forward.
• Repo-health is now scanning sail-command-center, but the GitHub Actions block is still open. Why pressing: the May 25 repo-health page says all 12 SAIL repos are now in scope, yet CI has been dark for about 13 days and Dependabot follow-through is still gated. Evidence: Daily Repo-Health Check 2026-05-25, plus local verification that Skills/daily-repo-health-check/repo-health-runner.sh includes sail-command-center. Safest next action: keep sail-command-center treated as covered, and carry forward only the CI, Dependabot, and runner checkpoint items.
• Litify GCLID propagation recovered from the runner failure, but apply is still blocked. Why pressing: the lane is no longer failing before validation, yet 3 webform conflicts still prevent any write pass. Evidence: Daily Litify attribution GCLID propagation, 2026-05-25. Safest next action: preserve the no-apply posture and review the three conflicts before any production sync.
• Website drift is a real live backlog; the old cwd blocker is not. Why pressing: the current audit reports 92 fail and 22 warn in read-only mode across live pages and posts, while the older stale-cwd claim has already been corrected. Evidence: Daily website content drift QA, 2026-05-24, 2026-05-23 Fixed daily website content drift QA stale cwd, and local verification that the active automation cwd is /Users/samaguiar/Documents/Projects/wp-content-visual-scripts-2026. Safest next action: keep the path issue closed, and prioritize repair planning around the high-signal live drift pages.
• Google Ads blocker language is still split between old and current pages. Why pressing: some pages still frame the lane as blocked until June 15, but the paid NotFair access was verified restored on May 23. Evidence: conflict between Google Ads Daily Negatives - 2026-05-22 and NotFair paid plan verified and Google Ads reporting restored, 2026-05-23. Safest next action: carry forward only the restored read-access state and the remaining review or negatives work, not the old quota blocker.
• Command Center source hygiene shipped, but the canonical exact report is still not built. Why pressing: the May 25 hygiene handoff explicitly warns against reintroducing stale MTD marketing-spend logic, and the local repo has moved forward since older pages that still cite 15 commits. Evidence: Command Center Litify Report Hygiene: Sam's Dashboard and Marketing Reports, plus local verification that Repos/sail-command-center is a live git repo with GitHub remote and 17 commits. Safest next action: keep the direct live query as the trusted source until an exact Litify report is created.

Likely forgotten or unfinished

Operations

• SAIL KB Daily Pulse - 2026-05-25: Status Needs Follow-up. Owner not explicit. Looks unfinished because the page still carries the older 1A, 1B, and 1C improvement set and reports an inflated backlog compared with both the weekly triage page and the live query.
• Daily Repo-Health Check 2026-05-25: Status Needs Follow-up. Owner not explicit. Looks unfinished because the repo-scope drift is closed, but the CI block, runner checkpoint need, and duplicate Dependabot PR cleanup are still open.
• Daily Briefing 2026-05-25 (Monday, Memorial Day): Status Needs Follow-up. Owner not explicit. Looks unfinished because it is new, high priority, and still open with no later completion note yet. needs verification
• Older dormant operations items still in open states include Server Deduplication: Repo Audit, Organization, and Forward Plan (March 3, 2026) and Git Repo Organization and GitHub Setup for All Project Folders. Both are old enough that they should be either reactivated with evidence or closed. needs verification

Website and SEO

• Sunday Site QA — 2026-05-24: Status Needs Follow-up. Looks unfinished because it remains the highest-severity live website drift summary and there is no later repair note yet.
• Cloudways Flexible follow-up: traffic graph and www SSL, 2026-05-24: Status Needs Follow-up. Looks unfinished because the weekly triage page still lists it as a front-edge pending example. needs verification
• Session 2026-05-24 — Cannibalization Audit Re-Check + Personal-Injury Metadata Fix: Status Needs Follow-up. Looks unfinished because the correction shipped but the page remains open.

Litify and Google Ads

• Daily Litify attribution GCLID propagation, 2026-05-25: Status Needs Follow-up. Looks unfinished because the runner and dry run are healthy, but the 3 webform conflicts still prevent apply.
• Google Ads Live Review via NotFair - 2026-05-23, Google Ads Lexington execution audit - 2026-05-23, and Google Ads Leverage Weekly — 2026-05-24: all remain open after reporting access was restored. Looks unfinished because the review work exists but the follow-through steps are still pending.