Description
The Lockfile Statistics Analysis found 279/286 workflows (97.6%) support workflow_dispatch, leaving 7 workflows without manual-trigger capability. Adding workflow_dispatch to these 7 would give fleet-wide parity for manual debugging/testing, matching the repo's dominant schedule+workflow_dispatch convention (66% of workflows).
Expected Impact
Enables manual debugging/re-runs for the last 7 workflows that currently can't be triggered on demand, closing a small but real operational gap.
Suggested Agent
New Agent — identify the 7 workflows lacking workflow_dispatch and add the trigger where appropriate (some may intentionally exclude it, e.g. release-only workflows — verify case-by-case).
Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing analysis of Lockfile Statistics Analysis (discussion #53820, 2026-08-18).
Generated by 🔬 Deep Report · agent · 108 AIC · ⌖ 8.65 AIC · ⊞ 11.9K · ◷
Description
The Lockfile Statistics Analysis found 279/286 workflows (97.6%) support
workflow_dispatch, leaving 7 workflows without manual-trigger capability. Addingworkflow_dispatchto these 7 would give fleet-wide parity for manual debugging/testing, matching the repo's dominantschedule+workflow_dispatchconvention (66% of workflows).Expected Impact
Enables manual debugging/re-runs for the last 7 workflows that currently can't be triggered on demand, closing a small but real operational gap.
Suggested Agent
New Agent — identify the 7 workflows lacking
workflow_dispatchand add the trigger where appropriate (some may intentionally exclude it, e.g. release-only workflows — verify case-by-case).Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing analysis of Lockfile Statistics Analysis (discussion #53820, 2026-08-18).