[Code Quality] Investigate and fix daily-code-metrics reporting-cadence gap (23-day scheduling failure) #49243

Description

The Daily Code Metrics Report - 2026-07-30 noted this workflow last ran on 2026-07-07 before this run on 2026-07-29/30 — a 23-day gap in what is supposed to be a daily report. This makes week-over-week trend deltas unreliable (they span the full 23-day gap rather than a single week) and suggests the schedule/trigger silently stopped firing or failed repeatedly without surfacing an alert.

Suggested Changes

• Check the daily-code-metrics workflow's schedule/cron trigger and confirm it is correctly configured and not disabled.
• Review Actions run history for the workflow between 2026-07-07 and 2026-07-29 for skipped/failed runs and root-cause any failures (e.g. concurrency lock, quota/rate-limit, permissions change, workflow_dispatch-only fallback).
• Add or verify alerting (e.g. via the existing [aw] workflow-failure filer) so silent multi-day scheduling gaps are caught automatically going forward.

Success Criteria

• Root cause of the 23-day gap identified and fixed.
• Workflow resumes its intended daily cadence with no further multi-day silent gaps.
• A regression safeguard (alert or check) exists to catch future scheduling gaps.

Source

Extracted from Daily Code Metrics Report - 2026-07-30 (discussion #49188)

Priority

Medium - restores reliability of an automated quality-tracking workflow.

🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · auto · 49.2 AIC · ⌖ 7.51 AIC · ⊞ 10.2K · ◷

• expires on Jul 31, 2026, 5:21 PM UTC-08:00