[deep-report] Housekeeping: 4 workflows declare schedule: but are disabled_manually (14-82 day gaps) #66882

Description

The 2026-10-07 Agent Job Health report's schedule-heartbeat check found 4 workflows that still declare a schedule: trigger in frontmatter but are disabled_manually on GitHub, with large gaps since their last run:

Live-verified: .github/workflows/daily-geo-optimizer.md, daily-hippo-learn.md, slide-deck-maintainer.md, and smoke-ci.md all still exist with active schedule:/cron frontmatter in the repo today, confirming the drift is real and not yet cleaned up.

Expected Impact

Each of these shows up as a false "blind spot" / undiagnosed-cron-misfire candidate in every future fleet-health report until resolved, wasting reviewer/agent attention. A one-time decision (re-enable or retire) removes the recurring noise.

Suggested Fix

For each workflow, either gh workflow enable <name>.lock.yml if still wanted, or remove the schedule: trigger (and consider removing the workflow files entirely) if intentionally retired.

Suggested Agent

Repo housekeeping / workflow-maintenance agent (e.g. Tidy).

Estimated Effort

Fast (< 30 min) — a judgment call per workflow plus a one-line frontmatter edit or gh workflow enable call.

Data Source

DeepReport Intelligence Briefing analysis, 2026-10-08. Source: discussion #66705 (Agent Job Health). Live-verified all 4 .md files still exist with active schedule/cron frontmatter.

Generated by 🔬 Deep Report · claude · agent · 342.4 AIC · ⌖ 10.9 AIC · ⊞ 7.1K · ◷

• expires on Oct 10, 2026, 4:53 AM UTC-08:00