You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs/src/content/docs/setup/cli.md (line 582) — replaced Forecast token usage and costs with Forecast AI Credit (AIC) usage and costs, matching pkg/cli/forecast_command.go:38.
pkg/cli/README.md (line 60) — same terminology update in the command index table so the in-repo CLI README stays in sync with the user-facing docs page.
Root Cause
Issue #38386 was auto-closed as not_planned by github-actions[bot] after PR #38828 merged. DDUw treats not_planned issues per Step 1c as not requiring action unless a related code change is found in the same 7-day window. The forecast command was not modified recently, so DDUw skipped the remaining items in #38386. But the terminology drift is a real documentation gap that exists today regardless of recent commits — it persisted from the prior Forecast AI Credit usage rename in the CLI.
💡 DDUw Improvement Suggestions
DDUw Improvement Suggestions
Proposed change to .github/workflows/daily-doc-updater.md Step 1c (closed as not_planned branch):
If the closed cli-consistency issue lists multiple discrete items and only some were fixed by a related PR, treat each unaddressed item independently. For each one, run the direct content check from the closed as completed branch (parse referenced files, verify the gap persists today) and fix it if the gap is unambiguous — do not require a matching commit in the 7-day window.
Why this helps: cli-consistency issues are produced by the CLI Consistency Checker, which compares the current CLI binary against the current docs. A drift it reports is, by construction, present today. A bot-driven not_planned close should not bypass that check.
A narrower alternative: extend Step 1c to recognise that issues tagged with documentation and cookie whose body lists multiple severity buckets need item-by-item triage rather than whole-issue skip/accept.
The bundle file is available in the agent artifact in the workflow run linked above.
To create a pull request with the changes:
# Download the artifact from the workflow run
gh run download 27450242681 -n agent -D /tmp/agent-27450242681
# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-27450242681/aw-doc-healer-forecast-terminology-2026-06-13.bundle refs/heads/doc-healer/forecast-terminology-2026-06-13:refs/bundles/create-pr-doc-healer-forecast-terminology-2026-06-13-f14c6f6c7f990a7c-a64c913c
git update-ref refs/heads/doc-healer/forecast-terminology-2026-06-13-f14c6f6c7f990a7c refs/bundles/create-pr-doc-healer-forecast-terminology-2026-06-13-f14c6f6c7f990a7c-a64c913c
git checkout doc-healer/forecast-terminology-2026-06-13-f14c6f6c7f990a7c
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-doc-healer-forecast-terminology-2026-06-13-f14c6f6c7f990a7c-a64c913c
# Push the branch to origin
git push origin doc-healer/forecast-terminology-2026-06-13-f14c6f6c7f990a7c
# Create the pull request
gh pr create --title '[docs] Self-healing documentation fixes from issue analysis - 2026-06-13' --base main --head doc-healer/forecast-terminology-2026-06-13-f14c6f6c7f990a7c --repo github/gh-aw
Caution
Protected files were modified in this change.
This pull request is in
request_reviewmode and requires explicit human scrutiny before merge.Protected files:
README.mdSelf-Healing Documentation Fixes
This PR was automatically created by the Daily Documentation Healer workflow. It resolves a confirmed documentation gap that DDUw missed.
Gap Fixed
Forecast AI Credit (AIC) usage) and the docs (Forecast token usage and costs). DDUw PR [docs] Update documentation for features from 2026-06-09 #38098 / [docs] Update documentation for features from 2026-06-12 #38828 addressed--gh-aw-refand themcp addinline comment but left this terminology mismatch in place.Files changed
docs/src/content/docs/setup/cli.md(line 582) — replacedForecast token usage and costswithForecast AI Credit (AIC) usage and costs, matchingpkg/cli/forecast_command.go:38.pkg/cli/README.md(line 60) — same terminology update in the command index table so the in-repo CLI README stays in sync with the user-facing docs page.Root Cause
Issue #38386 was auto-closed as
not_plannedby github-actions[bot] after PR #38828 merged. DDUw treatsnot_plannedissues per Step 1c as not requiring action unless a related code change is found in the same 7-day window. The forecast command was not modified recently, so DDUw skipped the remaining items in #38386. But the terminology drift is a real documentation gap that exists today regardless of recent commits — it persisted from the priorForecast AI Credit usagerename in the CLI.💡 DDUw Improvement Suggestions
DDUw Improvement Suggestions
Proposed change to
.github/workflows/daily-doc-updater.mdStep 1c (closed as not_plannedbranch):Why this helps:
cli-consistencyissues are produced by the CLI Consistency Checker, which compares the current CLI binary against the current docs. A drift it reports is, by construction, present today. A bot-drivennot_plannedclose should not bypass that check.A narrower alternative: extend Step 1c to recognise that issues tagged with
documentationandcookiewhose body lists multiple severity buckets need item-by-item triage rather than whole-issue skip/accept.Related Issues
Note
This was originally intended as a pull request, but the git push operation failed.
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.To create a pull request with the changes: