githubnext / githubnext/gh-aw-cao
[self-care:open-source-failures] Open-source failure digest for bounded 7-day snapshot
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
The bounded activity snapshot from 2026-09-04T19:58:53.598Z covers the last 168 hours across 7 public projects and contains 1048 failed runs. The highest-value untracked findings are repeated live-mode target-authority failures blocking AW Doctor workflows and repeated GitHub App token bootstrap failures blocking `Optimization / AI Credit Savings`.
**Action:** Repository maintainer should triage the two linked remediation issues in priority order and confirm that each affected workflow family produces at least one fresh successful run after the fix.
Critical clusters identified from the bounded evidence:
- P1: 13 runs in `githubnext/gh-aw-cao` AW Doctor workflows failing `Run CAO control precompute` with missing live-mode target authority.
- P1: 5 runs in `githubnext/gh-aw-cao` `Optimization / AI Credit Savings` failing at `Generate GitHub App token`.
- P1: 5 runs in `githubnext/gh-aw-cao` SelfCare workflows blocked by temporary GitHub API rate limiting.
- P1: 5 runs in `githubnext/gh-aw-cao` `Dev Practices / Well-Architected` failing during `Process Safe Outputs`.
- P1: 3 runs in `githubnext/gh-aw-workshop` workshop workflows failing `Upload activation artifact`.
Snapshot summary
- Snapshot generated: 2026-09-04T19:58:53.598Z
- Evidence window: 168 hours
- Public projects scanned: 7
- Failed runs in snapshot: 1048
- Snapshot truncated: yes, only the newest 100 failed runs were available
Cluster counts by severity
- P0: 0
- P1: 5 evidenced recurring clusters selected from the bounded snapshot
- P2: additional isolated or insufficient-evidence failures are present but were not opened for remediation
Existing coverage and filing decision
I could not confirm existing open issue coverage via GitHub read APIs in this sandbox because `gh issue list` failed locally with `malformed version:` before returning issue data. I therefore used the allowed maximum of 2 remediation issues for the highest-severity evidenced clusters and limited them to clearly distinct signatures to minimize duplicate risk.
Prioritized remediation list:
1. Restore live-mode target authority for AW Doctor workflows.
2. Fix repeated GitHub App token bootstrap failures in AI Credit Savings workflow.
Additional recurring clusters observed but not opened in this run:
- SelfCare workflows blocked by temporary GitHub API rate limiting.
- Dev Practices / Well-Architected safe-output processing failures.
- Workshop activation artifact upload failures in `githubnext/gh-aw-workshop`.
### Control Plane
- Correlation ID: 33916506448-180
- Central repository: githubnext/gh-aw-cao
- Control-plane run: https://github.com/githubnext/gh-aw-cao/actions/runs/33916506448
> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33916779396) · pi · gpt54 · 27.7 AIC · ⌖ 8.48 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 18, 2026, 8:39 PM UTC
Contributor guide
Research direction
Start with the listed AW Doctor and Optimization / AI Credit Savings workflow failures, using the control-plane run as the entry point. Inspect the `Run CAO control precompute` and `Generate GitHub App token` steps, then confirm the affected workflow families each produce at least one fresh successful run after remediation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, 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
- 20/100