[docs] Self-healing documentation fixes from issue analysis - 2026-03-17

[github-actions]

Self-Healing Documentation Fixes

This PR was automatically created by the Daily Documentation Healer workflow.

Gaps Fixed

• Issue GHES: Create prerequisites guide and troubleshooting runbook for Copilot engine #20968 (GHES prerequisites guide, closed as not_planned) — surfaced a related documentation gap: the GHES section of docs/src/content/docs/setup/cli.md described configure_gh_for_ghe.sh only as a manual step for custom steps:, but commit Inject GH_HOST configuration step into compiled agent job for GHE Cloud data residency #21408 (merged today) now automatically injects this step into every compiled agent job. The docs now correctly state that no manual configuration is needed for the agent itself, and that only user-defined custom steps: outside the agent sandbox still require the manual source call.

Root Cause

DDUw's Step 1b searches only for open documentation issues (is:open label:documentation). Issue #20968 was closed as not_planned on 2026-03-15 before DDUw ran, so DDUw never saw it. Additionally, a related code change (commit #21408, merged today) introduced automatic GHES gh CLI configuration in the compiled agent job — but because DDUw's 24-hour window and issue-scan logic were both focused on open issues, neither the deferred issue nor the behavioral change triggered a documentation update.

💡 DDUw Improvement Suggestions

DDUw Improvement Suggestions

Step 1b should also scan recently closed documentation issues. DDUw currently only checks is:open label:documentation. It should additionally run:

repo:$\{\{ github.repository }} is:issue is:closed label:documentation closed:>=YESTERDAY

For each recently closed issue:

• If closed as completed and no [docs] PR references it → potential missed documentation gap; investigate the related code changes.
• If closed as not_planned → log as a deferred documentation need; do not auto-create docs, but cross-reference with any related code changes in the same window to detect accidental doc gaps (like the configure_gh_for_ghe.sh auto-injection case here).

This would have caught issue #20968 and prompted DDUw to look at commit #21408, where the behavioral change needed a doc update.

Related Issues

• Closes GHES: Create prerequisites guide and troubleshooting runbook for Copilot engine #20968 (partially — the comprehensive GHES prerequisites guide requested there remains not_planned; this PR addresses only the related documentation gap surfaced by the associated code change)

References:

• §23212553221

Generated by Daily Documentation Healer · ◷

• expires on Mar 20, 2026, 7:35 PM UTC

[Copilot]

Pull request overview

Updates the GHES setup documentation to clarify how gh CLI is configured for agentic workflows and when users need to run the helper script manually.

Changes:

• Renames and rewrites the GHES gh CLI configuration section to explain automatic configuration in the compiled agent job.
• Adds guidance for manually invoking the helper script in custom workflow steps: outside the agent environment.
• Simplifies the final paragraph to focus on where the helper script is installed.

Comments suppressed due to low confidence (1)

docs/src/content/docs/setup/cli.md:92

• The example uses source /opt/gh-aw/actions/configure_gh_for_ghe.sh, but the script is meant to be executed as a standalone Bash script (it has a shebang, runs main, and persists GH_HOST via GITHUB_ENV). Using source is Bash-specific and can be confusing in Actions (it won’t carry shell state across steps). Prefer documenting run: bash /opt/gh-aw/actions/configure_gh_for_ghe.sh (or explicitly set shell: bash) for portability/clarity.

steps:
  - name: Configure gh for GHE
    run: source /opt/gh-aw/actions/configure_gh_for_ghe.sh

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.