Top pressing items

• Repo-health drift is still open. Why pressing: the May 24 repo-health run says GitHub Actions has been dark for about 12 days, sail-command-center is active but outside scan scope, and 13 QA items remain open. Evidence: most recent KB page Daily Repo-Health Check — 2026-05-24, plus local verification that Repos/sail-command-center is a git repo with GitHub remote and 15 commits. Safest next action: extend the scan spec to include sail-command-center, then treat the CI billing or self-hosted-runner fix as the main unblock.
• Needs Follow-up triage is still not registered. Why pressing: the KB pulse now reports 706 Needs Follow-up items and still carries the same missed-run, routine-log inflation, and duplicate-title improvements. Evidence: SAIL KB Daily Pulse - 2026-05-24, plus local verification that Skills/needs-followup-triage/scheduled-task-spec.md exists while no matching automation exists under ~/.codex/automations/. Safest next action: register the weekly triage task before adding more daily report layers.
• Litify GCLID propagation is stalled by runner failure. Why pressing: two consecutive recent notes show the workflow stopped before repo or Salesforce validation, so the daily attribution lane is accumulating missed write work. Evidence: Daily Litify attribution GCLID propagation blocked, 2026-05-24, local automation memory, and last-blocker-report.md showing shell-spawn failure. Safest next action: restore a command-capable runner and only then resume the normal validation and sync sequence.
• Website drift backlog remains high, but the stale-cwd claim is no longer current. Why pressing: the May 24 site QA flagged 388 findings across 302 pages, including 6 published noindex pages. Evidence: Sunday Site QA — 2026-05-24. Separately, the older stale-cwd issue cited by yesterday's drift-scan test run is now contradicted by the May 23 correction note and the local daily-website-content-drift-qa automation file. Safest next action: treat the path issue as closed, and re-verify the 6 noindex pages from the live site before any edits. needs verification
• Google Ads quota-block language is stale. Why pressing: several follow-up notes still point to the June 15 NotFair reset even though a later May 23 note verified the paid plan and restored reporting. 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 post-restore monitoring and negatives-review work, not the old quota blocker.

Likely forgotten or unfinished

Operations

• Daily Repo-Health Check — 2026-05-24: Status Needs Follow-up. Owner not explicit. Looks unfinished because the report itself says all 13 QA items from May 23 are still open, and the new sail-command-center drift is still unaddressed.
• Skills-Scheduled Mirror Sync — 2026-05-23 (Clean, 2 policy items open): Status Complete, but follow-up still pending. Looks unfinished because the mirror map is clean while the missing skill_surface_check.py and 144 uncommitted files remain open policy work.
• SAIL KB Daily Pulse - 2026-05-24: Status Needs Follow-up. Looks unfinished because the same three KB-pulse improvements were carried from May 23 without action.
• Older stale Active operations items surfaced by the pulse, including Server Deduplication: Repo Audit, Organization, and Forward Plan (March 3, 2026) and Mac Migration File Cleanup: Agent Prompts for Documents & Downloads (April 6, 2026), look genuinely dormant and should be reviewed for closure or reactivation. needs verification

Website and SEO

• Sunday Site QA — 2026-05-24: Status Needs Follow-up. Looks unfinished because the note lists high-severity SEO problems but no repair session yet.
• 2026-05-23 Fixed daily website content drift QA stale cwd: Status Complete. This should be treated as shipped, not as an open blocker.
• SEO Ops Session 2026-05-23 — seo-audit pre-flight shipped; seo-ops cloud workflow + Cloudways block pending: Status Needs Follow-up. Looks unfinished because the pre-flight shipped but the cloud workflow decision and Cloudways credential path remain open. needs verification

Litify and Google Ads

• Daily Litify attribution GCLID propagation blocked, 2026-05-24: Status Needs Follow-up. Looks unfinished because no repo, Salesforce, or sheet work actually ran.
• Google Ads Live Review via NotFair - 2026-05-23 and Google Ads Lexington execution audit - 2026-05-23: both remain Needs Follow-up. Looks unfinished because the audit work is done, but the negative-keyword and RSA follow-up steps are still open.
• Google Ads Daily Negatives - 2026-05-22: still open in Notion, but its quota-block explanation is superseded by the later paid-plan verification.