Summary

Audited the dirty tree in /Users/samaguiar/Documents/Projects after the Daily Repo Health cleanup. No additional repo mutations were made except creating a local audit note at /Users/samaguiar/Documents/Codex/git-tree-cleanliness-check/2026-05-10-dirty-tree-audit.md.

Work Done

• Checked root branch status: 23 tracked modified files and 78 untracked entries.
• Compared untracked workflow files against origin/main.
• Inspected tracked diffs across governance docs, Skills, scheduled-task registry, routine scripts, schema validator, uptime/SSL, WP cron, competitor scrape, and Outlook review.
• Checked nested repo status for Repos/sail-knowledge and Repos/sail-spanish-lp.
• Checked local Google Ads MCP tree structure and size.
• Ran Python compile checks for modified/new routine modules.
• Ran routines-build/scripts/test_seo_routines.py directly with unittest: 14 tests passed. pytest is missing in the venv, so pytest itself did not run.

Key Findings

• heartbeat-check.yml is byte-identical to origin/main, so it should not be committed from this branch.
• daily-sitemap-health-check.yml is stale versus origin/main; main has a safer force-add step for ignored state/output files.
• AGENT-TOOL-MANIFEST.md is useful but names many credential variables and token routes, so it should be reviewed or redacted before commit.
• Repos/sail-knowledge and Repos/sail-spanish-lp are independent Git repos but are not ignored by the root .gitignore. Both have their own local dirty state.
• google_ads_mcp/ is a 365M untracked runtime/source tree, mostly due to .venv; it should not be committed wholesale.
• The broken Google Ads MCP checkout archive contains a .git directory with lock files, useful as local rollback only, not as committed repo content.
• Some routine changes are coupled to untracked scripts. For example, run_daily_technical_bundle.sh now depends on check_forbidden_production_artifacts.sh, and registry.json references run_competitor_scrape.sh.
• Outlook review changes remove GoDaddy uptime alerts from low-priority handling. Given recent GoDaddy/Cloudways cleanup context, this should be held or reclassified deliberately.

Recommendation