Upgrade gh-aw and fix Codex runtime compatibility and usage reporting - #330
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ABC's mixed gh-aw runtimes included a retired
gpt-5-codexmodel, and Workflow Health missed the new runtime's usage artifacts while assigning unknown models an unrelated price. Upgrade all 27 workflows to gh-aw v0.89.21 / Codex CLI 0.154.0 and replace the eight retired model pins with the smoke-testedgpt-5.3-codex.Preserve shell-dependent prompts through explicit shell declarations, retain gh-proxy and existing security/output boundaries, fix custom-output step timeouts and Intake conclusion concurrency, and synchronize setup tooling, action pins, and upstream skills. The health collector now reads agent/detection usage artifacts, preserves provider identity, and reports unavailable or partial pricing honestly. Add configuration, evaluation, billing, and runtime-test documentation.
Validation:
The isolated smoke branch is excluded. Production locks are not staged. These tests cover representative runtime execution and staged output plumbing; they do not establish quality across all prompts or exercise actual external publication. The pinned release was the latest verified on September 24, 2026.