[self-care:open-source-failures] Open-source failure digest for 2026-09-04 activity snapshot

The 2026-09-04T19:58:53.598Z snapshot across 7 public projects captured 1,048 failed runs in the last 168 hours, with two highest-priority untracked recurring failure clusters in `githubnext/gh-aw-cao`: repeated live-mode target-authority admission failures across AW Doctor workflows (13 runs) and repeated safe-output processing failures in Dev Practices / Well-Architected (5 runs). Bounded evidence also contains many conclusion-only failures and isolated workflow-specific faults, so this digest prioritizes only the strongest actionable P1 clusters from the newest 100 failed runs available.

**Action:** Maintainers should triage the two remediation issues below and treat this digest as accepted when each issue has an owner and either a fix plan or a documented reason the bounded evidence was not sufficient.

- Snapshot generated: `2026-09-04T19:58:53.598Z`
- Evidence window: `168` hours
- Public projects scanned: `7`
- Failed runs in snapshot: `1048`
- Snapshot truncation: `true` — only the newest 100 failed runs were available for clustering
- Clusters surfaced in this review: `14`
- Severity counts: `P0 0`, `P1 14`, `P2 15`
- Existing open coverage matched: `0`

Prioritized remediation list:
1. `githubnext/gh-aw-cao` — AW Doctor live-mode admission blocked by missing target authority declaration (`13` runs across Upgrade, Compiler Security, and Failures).
2. `githubnext/gh-aw-cao` — Dev Practices / Well-Architected repeatedly fails during safe-output processing (`5` runs).

Cluster summary

### P1 clusters selected for remediation
- `githubnext/gh-aw-cao` — workflows `.github/workflows/aw-failures-investigator.lock.yml`, `.github/workflows/aw-maintenance-compiler-security.lock.yml`, `.github/workflows/aw-maintenance-upgrade.lock.yml`
Signature: `Target authority missing: add .github/workflows/cao.json to the target default branch for live mode`
Run count: `13`
Probable cause: live-mode admission is checking for target authority that is absent or unreadable on the target default branch.
Confidence: high.
- `githubnext/gh-aw-cao` — workflow `.github/workflows/software-development-practices-github-well-architected.lock.yml`
Signature: `Process Safe Outputs`
Run count: `5`
Probable cause: a recurring safe-output handoff or routing failure after agent execution; bounded snapshot does not show the underlying tool error.
Confidence: medium.

### Other bounded clusters not escalated here
- Multiple conclusion-only recurrences exist for `githubnext/gh-aw-cao` and `githubnext/gh-aw-workshop`, but the snapshot lacks enough enriched evidence to justify a distinct remediation issue without risking duplicate or speculative causes.
- Isolated rate-limit admissions and single-run agent-step failures were kept below the remediation cutoff.

### Control Plane
- Correlation ID: `33915562891-179`
- Central repository: `githubnext/gh-aw-cao`
- Control plane run URL: `https://github.com/githubnext/gh-aw-cao/actions/runs/33915562891`

> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33915982194) · pi · gpt54 · 28.2 AIC · ⌖ 8.57 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:29 PM UTC

Start with the three AW Doctor workflow files and inspect the target branch for .github/workflows/cao.json and the reported target-authority admission failures. Then examine the software-development-practices-github-well-architected.lock.yml workflow around Process Safe Outputs. Done means each cluster has an owner and either a fix plan or a documented reason that the bounded evidence is insufficient.

Written by the indexing model from the issue text.