Scope

Read-only inspection on May 13, 2026 of scheduled GitHub workflows under C:\Users\SAguiar\Documents\Projects, centered on google-ads-cloud-runner and seo-cloud-runner, plus other workflow files that clearly map to the same Google Ads / SEO recurring automation lanes.

Scheduled workflows and overlap assessment

• C:\Users\SAguiar\Documents\Projects\google-ads-cloud-runner\.github\workflows\competitive-context-drift.yml
  • Cron: 5 11 * * 1
  • Local time: Monday 7:05 AM America/New_York during EDT
  • Assessment: confirmed parallel of the existing weekly-competitor-drift-check lane. Repo files and prior automation memory both point to the same cadence.
• C:\Users\SAguiar\Documents\Projects\google-ads-cloud-runner\.github\workflows\google-ads-runner.yml
  • Cron: 30 11 * * 1-5
  • Local time: weekdays 7:30 AM America/New_York during EDT
  • Assessment: likely cloud counterpart to the local guarded preflight habit, but no second live GitHub schedule or confirmed Claude scheduler entry was found for this exact runner.
• C:\Users\SAguiar\Documents\Projects\seo-cloud-runner\.github\workflows\weekly.yml
  • Cron: 15 14 * * 2
  • Local time: Tuesday 10:15 AM America/New_York during EDT
  • Assessment: likely duplicate or parallel of the local weekly SEO market-intel lane. The repo README says the same weekly lane is meant to run locally or in CI.
• C:\Users\SAguiar\Documents\Projects\_repo-staging\sail-seo\.github\workflows\scope-scan.yml
  • Cron: 0 16 * * *
  • Local time: daily 12:00 PM America/New_York during EDT
  • Assessment: confirmed parallel of the local sail-seo-scope-scan-daily task. The workflow comment explicitly says it is a later cloud clone of the local 7:00 AM America/New_York task and that local remains canonical.
• C:\Users\SAguiar\Documents\Projects\_repo-staging\sail-seo\.github\workflows\weekly-site-audit.yml
  • Cron: 0 12 * * 6
  • Local time: Saturday 8:00 AM America/New_York during EDT
  • Assessment: one of three mirror copies of the same cloud weekly site-audit lane.
• C:\Users\SAguiar\Documents\Projects\_repo-staging\sail-seo\Website_project\.github\workflows\weekly-site-audit.yml
  • Cron: 0 12 * * 6
  • Local time: Saturday 8:00 AM America/New_York during EDT
  • Assessment: duplicate mirror of the same weekly site-audit workflow.
• C:\Users\SAguiar\Documents\Projects\_repo-staging\website-seo\Website_project\.github\workflows\weekly-site-audit.yml
  • Cron: 0 12 * * 6
  • Local time: Saturday 8:00 AM America/New_York during EDT
  • Assessment: duplicate mirror of the same weekly site-audit workflow.

Excluded from the live overlap list

• C:\Users\SAguiar\Documents\Claude\Projects\Google Ads Negative Keywording\repo-scaffold\.github\workflows\daily-sweep.yml exists outside Projects, but its schedule is commented out and the related handoff notes say the scheduled task was not created. I treated it as background only, not a live overlap.
• C:\Users\SAguiar\Documents\Projects\_repo-staging\skills\web-content-new\runner\.github\workflows\web-content-new.yml is a separate content-publishing lane, not obviously the same Google Ads / SEO audit / drift / preflight stack.

Main takeaways

• Confirmed local/cloud duplicate: scope-scan.yml.
• Confirmed same-lane cloud copy of an existing recurring automation: competitive-context-drift.yml.
• Likely local/cloud parallel lane: seo-cloud-runner\.github\workflows\weekly.yml.
• Mirror duplication inside staging repos: three separate weekly-site-audit.yml files on the same Saturday schedule.
• No second live GitHub schedule under Projects clearly duplicates google-ads-runner.yml itself.

Pending approvals