Sam selected A: mark sail-googleads local-only so hosted repo-health reports do not show the known intentional GitHub 404 as a red error.
I updated the hosted repo-health Worker source, added a regression test, updated the Worker README, deployed the Worker, and updated the local run report plus QA queue.
/Users/samaguiar/Documents/Projects/routines-build/cloudflare/repo-health-worker/src/index.js/Users/samaguiar/Documents/Projects/routines-build/cloudflare/repo-health-worker/test.mjs/Users/samaguiar/Documents/Projects/routines-build/cloudflare/repo-health-worker/README.md/Users/samaguiar/Documents/Codex/repo-health/2026-05-26-hosted-worker-and-index-reconcile.md/Users/samaguiar/Documents/Codex/_qa-queue/2026-05-26.mdDEFAULT_REPOS now marks sail-googleads as local_only. The Worker returns an intentional local-only record with fetch_status=hosted_skipped_local_only, hosted_status=local_only_repo, and no GitHub API error.
npm test: passed, including the new local-only regression test.wrangler deploy --dry-run: passed with upload size 8.60 KiB, gzip 2.69 KiB.wrangler deploy: deployed Worker version 020beec3-2e9e-4e00-9847-9a7a83f03a4c.GET /health: HTTP 200 with ok=true.GET /repo-health: repo_count=12, sail-googleads present, local_only=True, fetch_status=hosted_skipped_local_only, hosted_status=local_only_repo, api_status=None, api_errors=[], and sail-command-center still present.GET /repo-health?repo=sail-googleads: returned the focused local-only record.Note: Python urllib received Cloudflare error 1010; curl succeeded. This appears to be a Cloudflare client-fingerprint behavior, not a Worker auth or repo-health failure.
The selected follow-up is implemented, deployed, documented, and live-verified. The only remaining repo-health QA item is separate from this fix: triaging the 115 real dirty entries in the Projects root after the earlier git-index reconciliation.