githubnext / githubnext/gh-aw-cao
[self-care:open-source-failures] Open-source failure digest for 2026-09-05 bounded snapshot
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
Bounded seven-day snapshot across 7 public projects found 1,174 failed runs and multiple recurring clusters; the highest-impact untracked pattern is repeated live-mode pre-activation failure in `githubnext/gh-aw-cao` AW Doctor and Dependabot workflows due to missing or incomplete target authority. Because the activity feed is truncated to the newest 100 failed runs, this digest reflects bounded evidence only.
**Action:** Maintainers should review the two remediation issues linked below first; accept when `githubnext/gh-aw-cao` live-mode pre-activation failures stop recurring and no new equivalent high-severity clusters appear in the next bounded snapshot.
- Snapshot generated: `2026-09-05T05:59:17.450Z`
- Evidence window: last `168` hours
- Public projects scanned: `7`
- Failed runs in snapshot: `1174`
- Evidence truncation: `true` (only newest 100 failed runs available)
- Cluster counts in this bounded analysis: `P0 0`, `P1 7`, `P2 8`
- Existing coverage check: could not be completed because `gh issue list` returned infrastructure errors from the local GitHub API bridge; duplicate risk remains
- Prioritized remediation list:
1. `githubnext/gh-aw-cao`: recurring live-mode pre-activation failures in AW Doctor workflows caused by missing `aw-doctor` target authority
2. `githubnext/gh-aw-cao`: recurring live-mode pre-activation failures in Dependabot Release Trains caused by missing `dependabot` target authority
Bounded cluster summary
- **P1** `githubnext/gh-aw-cao` — AW Doctor workflows (`aw-failures-investigator`, `aw-maintenance-upgrade`, `aw-maintenance-compiler-security`) repeatedly fail in `pre_activation` / `Run CAO control precompute` with signature `Target authority missing` and one corroborating stricter message requiring `target-authority.packages.aw-doctor.authority`.
- **P1** `githubnext/gh-aw-cao` — Dependabot Release Trains repeatedly fails in `pre_activation` / `Run CAO control precompute` with signature `Target authority missing` and one corroborating stricter message requiring `target-authority.packages.dependabot.authority`.
- **P1** `githubnext/gh-aw-cao` — Optimization / AI Credit Savings repeatedly fails in `agent` / `Generate GitHub App token`.
- **P1** `github/gh-aw` — multiple workflows (`avenger`, `cli-version-checker`, `schema-consistency-checker`, `daily-cli-tools-tester`, `daily-documentation-diagram`) repeatedly fail in `agent` / `Execute Codex CLI`; cross-workflow merge is bounded because the shared cause is not proven.
- **P1** `githubnext/gh-aw-cao` — Dev Practices / Well-Architected repeatedly fails in `safe_outputs` / `Process Safe Outputs`.
- **P1** `githubnext/gh-aw-workshop` — multiple workflows repeatedly fail in `activation` / `Upload activation artifact`; cross-workflow merge is bounded because a shared cause is plausible but not proven.
- **P1** `githubnext/gh-aw-cao` — self-care dashboard review workflow has repeated conclusion-only failures with insufficient enrichment.
- **P2** `githubnext/gh-aw-cao` — SelfCare safe outputs failure (`Process Safe Outputs`) is isolated in bounded evidence.
- **P2** `githubnext/gh-aw-cao` — SelfCare conclusion-only failures are isolated and insufficiently evidenced.
- **P2** `githubnext/gh-aw-cao` — SelfCare / Dashboard Performance safe outputs failure is isolated in bounded evidence.
- **P2** `github/gh-aw` — reviewer workflows with conclusion-only failures are kept separate where evidence is insufficient to prove a shared cause.
### Control Plane
- Correlation ID: `33949930283-204`
- Central repository: `githubnext/gh-aw-cao`
- Control-plane run: https://github.com/githubnext/gh-aw-cao/actions/runs/33949930283
> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33950105363) · pi · gpt54 · 16.6 AIC · ⌖ 8.59 AIC · ⊞ 8.3K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Fself-care-open-source-failures%22&type=issues)
> - [x] expires on Sep 19, 2026, 6:37 AM UTC
Contributor guide
Research direction
No source files or tests are named. Start by reviewing the AW Doctor and Dependabot workflows at the `pre_activation` `Run CAO control precompute` step, focusing on the reported missing target authority; done means the recurring live-mode failures stop in a subsequent bounded snapshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100