Actions Fleet Monitor — 2026-09-14

Org: petry-projects | Lookback: 1 day(s) | Repos: 11 | Workflows: 331

Fleet Health

🔴 CRITICAL: 2 🟠 DEGRADED: 1 🟡 WARNING: 3 ✅ HEALTHY: 105

pie title Workflow Status Distribution
  "CRITICAL" : 2
  "DEGRADED" : 1
  "WARNING" : 3
  "HEALTHY" : 105

Top Failing Workflows

xychart-beta
  title "Top Failing Workflows (≥5 runs)"
  x-axis [".github-private/.github/workflows/lint.yml","repo-template/.github/workflows/ci.yml",".github-private/.github/workflows/pr-review-trigger.yml",".github-private/.github/workflows/test.yml","repo-template/.github/workflows/dev-lead.yml"]
  y-axis "Failure Rate %" 0 --> 100
  bar [93,58,3,3,0]

Per-Repo Summary

Fleet Detail

Failed Runs

petry-projects/.github-private / .github/workflows/daily-pr-review-health.yml

petry-projects/.github-private / .github/workflows/lint.yml

petry-projects/.github-private / .github/workflows/pr-review-trigger.yml

petry-projects/.github-private / .github/workflows/test.yml

petry-projects/TalkTerm / .github/workflows/pr-auto-review.yml

petry-projects/repo-template / .github/workflows/ci.yml

petry-projects/repo-template / .github/workflows/dev-lead.yml

Dev-Lead Timeouts (walls)

Stage timeouts (reason=timeout) that escalate to a human, broken out from generic engine-error, over the window.

Per-repo rows list only repos with >=1 dev-lead marker in the window; the Total runs fleet total (and the rate denominator) include all dev-lead runs fleet-wide, incl. all-success repos with no markers.

Timeout rate (reason=timeout / total dev-lead runs fleet-wide — prevalence over all runs, not just failures): 0% (0 / 1085)

Schedule Reliability

Expected cron ticks vs. actual schedule-triggered runs per scheduled workflow over the window. A cron that silently stopped firing shows as STALLED even when its last run "succeeded" — so a stalled backlog stops hiding behind a green check.

Scheduled runs are best-effort — GitHub may delay or drop ticks under load and only schedules crons on the default branch. A tolerance of 1 tick(s) is applied so a late-but-present run is not scored as a miss, and only schedule-event runs are counted (workflow_dispatch / push / repository_dispatch excluded). Run queries are capped at 1000 results per window, so very high-volume workflows may under-report actual runs.

Persona opt-out label coverage

Every persona advisory tells maintainers they can opt out with <id>:hands-off, and the mention router matches that label by exact name — a label that does not exist can never match, so a missing opt-out reads silently as "not opted out" (fail-open by omission, #1644). The family is derived from personas/*/persona.yml, so a new persona is covered automatically.

✅ COMPLETE: 4 🔴 INCOMPLETE: 7 · derived family size: 9

These repos carry some but not all persona opt-out labels — the escape hatch is inert for the missing personas. Fan out the derived family:

Initiative-planner stub coverage & drift

Canonical template SHA: d4af6cd · enrolled repos (stub present): 11

✅ ALIGNED: 0 🔴 DRIFTED: 11 ⬜ MISSING (not enrolled): 0

These enrolled repos have drifted from the canonical stub — re-sync them:

Initiative-driver stub coverage & drift

Canonical template SHA: 5a58fa2 · enrolled repos (stub present): 11

✅ ALIGNED: 1 🔴 DRIFTED: 10 ⬜ MISSING (not enrolled): 0

These enrolled repos have drifted from the canonical stub — re-sync them: