[self-care:open-source-failures] Investigate recurring Codex CLI failures across gh-aw workflows

Multiple Codex-backed workflows in `github/gh-aw` are recurring at the same `Execute Codex CLI` step. The bounded snapshot shows 7 failures across 7 workflows, which is enough to justify a single shared investigation even though the snapshot does not expose the underlying runtime error.

**Action:** A `github/gh-aw` maintainer should assign this issue to Copilot to isolate the common `Execute Codex CLI` failure path and apply the smallest shared fix; accept when the next bounded snapshot shows no recurring `Execute Codex CLI` failures for the affected workflows.

Agent prompt
Investigate the recurring `Execute Codex CLI` failures across the affected `github/gh-aw` workflows. Find the shared action, wrapper, or runtime configuration used to invoke Codex CLI, determine the first concrete failing condition, implement the minimal reusable fix in the common path, and summarize which workflows were validated and why the change should prevent recurrence.

- Severity: P1
- Repository: `github/gh-aw`
- Affected workflows: `Daily Go Test Parallelizer`, `PureLock`, `Auto-Triage Issues`, `Package Specification Enforcer`, `GitHub API Consumption Report Agent`, `Daily Max Ai Credits Test`, `Daily Documentation Updater`
- Normalized signature: `Execute Codex CLI`
- Evidence-supported cause: repeated failure while invoking Codex CLI in the agent step; bounded evidence does not identify the underlying runtime cause
- Confidence: medium
- Bounded fix: diagnose and patch the shared Codex CLI invocation path without changing unrelated workflow behavior
- Representative runs:
- https://github.com/github/gh-aw/actions/runs/33966484770
- https://github.com/github/gh-aw/actions/runs/33966410850
- https://github.com/github/gh-aw/actions/runs/33966120309
- https://github.com/github/gh-aw/actions/runs/33963266095

Cluster evidence

Corroborating workflows in the bounded snapshot:
- `.github/workflows/daily-go-test-parallelizer.lock.yml`
- `.github/workflows/purelock.lock.yml`
- `.github/workflows/auto-triage-issues.lock.yml`
- `.github/workflows/spec-enforcer.lock.yml`
- `.github/workflows/api-consumption-report.lock.yml`
- `.github/workflows/daily-max-ai-credits-test.lock.yml`
- `.github/workflows/daily-doc-updater.lock.yml`

The newest 100 failed runs were the only available evidence, so this issue should start with the shared invocation path before workflow-specific debugging.

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

> Generated by [SelfCare / Open Source Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33969046593) · pi · gpt54 · 26.1 AIC · ⌖ 8.71 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, 1:35 PM UTC

Start by comparing the shared Execute Codex CLI step across the seven listed .github/workflows/*.lock.yml files, then inspect the representative failed runs to identify the first concrete runtime failure. Trace the common invocation or configuration path and validate the minimal fix against the affected workflows. Done means the next bounded snapshot shows no recurring Execute Codex CLI failures.

Written by the indexing model from the issue text.