Scope

Read-only audit of local Codex automation folders under C:\Users\SAguiar\.codex\automations and nearby cloud scheduler definitions in the runner repos.

What I checked

• Local automation definitions for Azure SAS, Google Ads safe access preflight, AI Visibility Competitor Watch, Weekly SEO Market Intel, and orphan records.
• Nearby GitHub Actions workflows in C:\Users\SAguiar\Documents\Projects\google-ads-cloud-runner\.github\workflows and C:\Users\SAguiar\Documents\Projects\seo-cloud-runner\.github\workflows.
• Recent local artifact roots under C:\Users\SAguiar\Documents\Codex.
• Retained Codex memory notes for prior deletion or demotion guidance.

Recommendations

1. Google Ads Safe Access Preflight local vs cloud

Recommendation: demote the local automation to manual fallback and keep the cloud workflow as the recurring authority.

• Local path: C:\Users\SAguiar\.codex\automations\google-ads-safe-access-preflight\automation.toml
• Cloud path: C:\Users\SAguiar\Documents\Projects\google-ads-cloud-runner\.github\workflows\google-ads-runner.yml
• Why: cloud workflow is real and has downloaded artifacts; local and cloud both produced preflight evidence on 2026-05-11.

2. Azure SAS Monitor vs Local Mirror

Recommendation: keep azure-sas-monitor-local-mirror as the single local recurring lane and retire or archive the original azure-sas-monitor record unless you still want a separate worktree variant.

• Candidate retire/archive: C:\Users\SAguiar\.codex\automations\azure-sas-monitor\automation.toml
• Keep: C:\Users\SAguiar\.codex\automations\azure-sas-monitor-local-mirror\automation.toml
• Why: both target the same script and schedule window; no nearby cloud workflow was found in shared-infrastructure.

3. AI Visibility Competitor Watch vs Weekly SEO Market Intel

Recommendation: keep weekly-seo-market-intel-execution as the primary recurring lane and demote ai-visibility-competitor-watch to an on-demand deep-dive or merge its unique prompts into the weekly lane.