Daily Repo-Health Check — 2026-05-28

At a glance

12 repos in scope. All git-backed today; sail-googleads converted from non-git scaffold overnight.
0 new commits on any default branch in 24h. sail-seo's 272abc4 from 2026-05-27 remains the most recent main movement account-wide.
CI block continues — ~16th consecutive day. Zero workflow runs anywhere. Gates P4 (Dependabot merges) and P8 (sail-seo PRs). P7 remains the single highest-leverage open item.
Dependabot coverage: 0 of 12 (denominator +1 from sail-googleads conversion).
Secret-store integrity: clean. secrets_github_only empty for every repo. NOTION_TOKEN present in sail-knowledge alongside ANTHROPIC_API_KEY.
Disabled workflows: 0.
Vault key count: 294, unchanged from 2026-05-27.
Autonomous fixes this run: 0 net writes (audit trail at ~/Documents/Codex/repo-health/backups/2026-05-28/README.md).

What changed vs 2026-05-27

sail-googleads converted from non-git scaffold to a git repo on agent/restoration-continue-2026-04-24, 96 dirty, 4 commits ahead. New P12 captures the "first push and establish remote main" decision.
sail-command-center main went dirty 7 → 30 with new connector-OS files (connector-os.ts, connector-registry.ts, connector-store.ts, src/app/api/connectors/, src/app/api/cron/, vercel.json) and 16 modifications to core files. Should move to wip/connector-os-2026-05-28 to stop main accumulating in-flight work. New P13.
sail-seo agent branch behind-count steady at 24 (no new main commit; rebase debt not growing this cycle).
Workflows API now consistent with direct GitHub API — yesterday's "partial recovery" reading was an artifact. The real account state is: only sail-seo/weekly-site-audit.yml exists in state=active; every other repo has zero workflows. The empty arrays are not an API hiccup — they are the actual state.
sail-litify git status --porcelain core-dumped in the sandbox at the 30 s memory ceiling both during the parallel pass and a sequential re-verification. Dirty count carries the 2026-05-26 checkpoint baseline (517). Local HEAD verified standalone at d05e5d8. Runner-edge degradation, not a P9 regression.

Repo scoreboard

Repo	Branch	Dirty	Ahead/Behind	Δ vs 2026-05-27
sail-googleads	agent/restoration-continue-2026-04-24	96	4/0	NEW: non-git → git-backed, 4 ahead (P12)
sail-litify	agent/fix-attorneyhubpayton-test-2026-05-23	517*	–	dirty count carried (sandbox kill)
sail-marketing	agent/projects-reorg-2026-04-18	1724	0/0	unchanged
sail-seo	agent/credential-redaction-2026-05-04	2	2/24 vs origin/main	unchanged (main flat at `272abc4`)
sail-knowledge	hotfix/redact-leaked-pat-2026-05-08	698	–	unchanged (11th day at 698)
sail-cases	main	0	0/0	clean
sail-hr	main	2	0/0	unchanged
sail-infrastructure	agent/projects-reorg-2026-04-18	136	0/0	unchanged
sail-templates	agent/trust-strip-sitewide-2026-04-19	2	0/0	unchanged
sail-spanish-lp	main	0	0/0	clean
ha-law	main	83	0/0	unchanged (11th day, P3)
sail-command-center	main	30	0/0	dirty 7 → 30 (P13)

*sail-litify dirty from 2026-05-26 checkpoint (sandbox kill on git status).

QA Recommendations Pending Approval

Permanent checks P1–P6 appear every run. P1, P2, P5, P6 stay passive/resolved. P3, P4, P7, P8, P10 carry forward. P9 stays passive at run-loop level. P11 doesn't fire (vault unchanged). Two new items: P12 and P13.