[docs] Update documentation for features from 2026-08-01

[github-actions]

Documentation Updates - 2026-08-01

This PR updates reference documentation for user-visible workflow behavior merged in the last 24 hours.

Features Documented

• Clarified Copilot BYOK threat-detection target resolution when COPILOT_PROVIDER_BASE_URL is a literal URL (from Fix Copilot BYOK target resolution for self-hosted provider URLs #49464)
• Clarified that the go network ecosystem includes go.dev for toolchain downloads as well as module hosts (from fix: set GOTOOLCHAIN=auto in Avenger and hourly-ci-cleaner workflows #49461 and Stabilize go-logger workflow toolchain resolution #49473)

📝 Detailed Changes & References

Changes Made

• Updated docs/src/content/docs/reference/engines.md to explain that threat detection derives its Copilot API target from a literal COPILOT_PROVIDER_BASE_URL when other target settings are absent
• Updated docs/src/content/docs/reference/network.md to list go.dev in the go ecosystem identifier description

Merged PRs Referenced

• Fix Copilot BYOK target resolution for self-hosted provider URLs #49464 - Fix Copilot BYOK target resolution for self-hosted provider URLs
• fix: set GOTOOLCHAIN=auto in Avenger and hourly-ci-cleaner workflows #49461 - fix: set GOTOOLCHAIN=auto in Avenger and hourly-ci-cleaner workflows
• Stabilize go-logger workflow toolchain resolution #49473 - Stabilize go-logger workflow toolchain resolution

AI dictionary alignment summary

• Terms reviewed: BYOK, threat-detection step, ecosystem identifier
• Terms adopted: BYOK, ecosystem identifier
• Conflicts resolved: none

Skipped Issues

• No documentation issues were updated in this run because GitHub issue search returned a local gh CLI error (malformed version:), so only merged-PR-driven documentation changes were applied.

Notes

These edits stay in reference docs because they clarify existing behavior rather than introducing a new guide or tutorial.

Generated by 📝 Daily Documentation Updater · gpt54 · 18 AIC · ⌖ 10.3 AIC · ⊞ 9.4K · ◷

• expires on Aug 2, 2026, 3:08 AM UTC-08:00

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.48 AIC · ⌖ 10.4 AIC · ⊞ 8.1K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.48 AIC · ⌖ 10.4 AIC · ⊞ 8.1K · ◷
_{Comment /souschef to run again}

---

Caution

agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.

Details

Potential security threats were detected in the agent output.

Review the workflow run logs for details.

Run details: https://github.com/github/gh-aw/actions/runs/30702262954

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 17.7 AIC · ⌖ 5.22 AIC · ⊞ 8.1K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.99 AIC · ⌖ 9.58 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

---

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.28 AIC · ⌖ 7.2 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

---

Branch refresh requested by pr-sous-chef for run https://github.com/github/gh-aw/actions/runs/30709866559

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 10.4 AIC · ⌖ 6.49 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

[gh-aw-bot]

@copilot quick triage for this PR:

• This PR is currently UNSTABLE; please inspect the latest checks and repair or rerun whatever is blocking merge.
• Branch refresh: GitHub branch update was requested from this run.
• Please run the pr-finisher skill before handoff and summarize whether maintainer action is still needed.

Generated by 👨🍳 PR Sous Chef

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.48 AIC · ⌖ 10.4 AIC · ⊞ 8.1K · ◷
_{Comment /souschef to run again}

[github-actions]

Nice work! 👏 This documentation update is ready for review. The changes are well-scoped—clarifying the Copilot BYOK threat-detection target behavior and adding go.dev to the ecosystem identifier description. Both updates are tied to recently merged features (#49464, #49461, #49473) and are exactly the kind of incremental clarifications that keep reference docs current and useful.

The PR body is comprehensive, including feature context, merged PR references, and dictionary alignment notes. Documentation-only contributions like this are a great way to improve the project.

Generated by ✅ Contribution Check · auto · 50.4 AIC · ⌖ 12.9 AIC · ⊞ 8.7K · ◷

[gh-aw-bot]

Caution

agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.

Details

Potential security threats were detected in the agent output.

Review the workflow run logs for details.

@copilot quick triage for this PR:

• This documentation-only PR looks review-ready; please run the pr-finisher skill, confirm there are no hidden blockers, and summarize any maintainer action still needed before merge.
• Branch refresh: GitHub branch update was requested from this run.
• Run details: https://github.com/github/gh-aw/actions/runs/30702262954

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 17.7 AIC · ⌖ 5.22 AIC · ⊞ 8.1K · ◷
_{Comment /souschef to run again}

[Copilot]

[!CAUTION]
agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation....

Manual triage is complete.

• ✅ Reviews — no unresolved review threads or pending code-review comments were found.
• ✅ Checks (local) — make fmt, make lint, make test-unit, and make recompile completed cleanly with no file changes. make test hit a pre-existing unrelated wasm golden/version drift (GH_AW_INFO_VERSION 1.0.75 → 1.0.77 in pkg/workflow golden tests), not a docs-PR regression.
• ✅ Checks (CI/manual review) — the latest PR Sous Chef run 30702262954 finished successfully; all 8 jobs succeeded. The threat-detection note was warn-mode/manual-review only, and I did not find a hidden code blocker from it.
• ✅ Mergeable — the branch is already current with main (594778a), so no branch refresh was needed.

Still needed before merge: maintainer manual review of the warn-mode threat-detection note, and if branch protection requires fresh green automation after bot activity, re-trigger the relevant PR checks before merging.

[gh-aw-bot]

@copilot quick triage for this PR:

• This PR is currently UNSTABLE; please inspect the latest checks/state and summarize whether any maintainer action is still needed.
• Branch refresh: GitHub branch update was requested from this run.
• Please run the pr-finisher skill before handoff.

Generated by 👨🍳 PR Sous Chef

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.99 AIC · ⌖ 9.58 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot quick triage for this PR:

• This PR is currently UNSTABLE; please inspect the latest checks/state and summarize whether any maintainer action is still needed.
• Branch refresh: GitHub branc...

Manual triage is complete.

• ✅ Reviews — no unresolved review comments or review threads were found.
• ✅ Checks (local) — make fmt, make lint, make test-unit, and make recompile passed cleanly. make test still hits the pre-existing unrelated wasm golden drift in pkg/workflow (GH_AW_INFO_VERSION 1.0.75 → 1.0.77), not a docs-PR regression.
• ❓ Checks (CI/state) — the PR is currently UNSTABLE because this active Copilot job is still in progress: Addressing comment on PR #49568 (30705811459). The older PR workflow runs on this head are action_required, but they show no failed jobs via log inspection; they appear to be moderation/manual-review style gates rather than code failures.
• ✅ Mergeable/base freshness — the branch is already current with main (2a77c29 is directly based on 594778a), so no branch refresh was needed.

Actions taken: verified PR state, reviewed the latest workflow/check state, fetched origin/main so full-test triage could run, and confirmed no code changes are needed for this comment.

Still needed: let the in-progress Copilot run finish, and if branch protection treats the existing action_required moderation checks as blocking, a maintainer should complete the required manual review/acknowledgement before merge.

[gh-aw-bot]

@copilot quick triage for this PR:

• The branch is still UNSTABLE; inspect the latest state and confirm whether the only remaining blocker is the in-progress/stale automation state.
• Branch refresh: GitHub branch update was requested from this run.
• Please run the pr-finisher skill before handoff and summarize any maintainer action still needed.
• Run details: https://github.com/github/gh-aw/actions/runs/30707634635

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 9.28 AIC · ⌖ 7.2 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot quick triage for this PR:

• The branch is still UNSTABLE; inspect the latest state and confirm whether the only remaining blocker is the in-progress/stale automation state.
• Branch refresh...

Manual triage is complete.

• ✅ Reviews — no unresolved review comments or review threads were found.
• ✅ Checks (local) — on the unchanged 2a77c29 head, make fmt, make lint, make test-unit, and make recompile passed again. make test remains the same pre-existing unrelated wasm golden/version drift in pkg/workflow (GH_AW_INFO_VERSION 1.0.75 → 1.0.77), not a docs-PR regression.
• ❓ Checks (CI/state) — the only active automation blocker is the new in-progress Copilot run 30707879216 / job 91390030286. Earlier Copilot runs on this same head completed successfully, and the latest PR Sous Chef run 30707634635 completed successfully with no missing-tools/errors/warnings in the audit output. The older PR workflow runs on this head are still action_required, but log inspection shows no failed jobs; they still look like moderation/manual-review gates rather than code failures.
• ✅ Mergeable/base freshness — the branch is still directly based on main (2a77c29 parent 594778a), so no branch refresh was needed.

Actions taken: re-checked the latest PR/check state, reviewed the latest Sous Chef run, re-ran local fmt/lint/test-unit/recompile on the current head, and confirmed no code changes are needed.

Still needed: let the in-progress Copilot run finish. After that, if branch protection still treats the existing action_required moderation checks as blocking, a maintainer needs to complete the required manual review/acknowledgement before merge.

[gh-aw-bot]

@copilot Please triage PR #49568 ([docs] Update documentation for features from 2026-08-01). Refresh the branch if GitHub allows it, address any outstanding review feedback or CI instability, and run the pr-finisher skill before pushing updates.

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 10.4 AIC · ⌖ 6.49 AIC · ⊞ 5.7K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot Please triage PR #49568 ([docs] Update documentation for features from 2026-08-01). Refresh the branch if GitHub allows it, address any outstanding review feedback or CI instability, and run ...

Manual triage is complete.

• ✅ Reviews — no unresolved review threads or review comments are open on PR [docs] Update documentation for features from 2026-08-01 #49568.
• ✅ Mergeable/base freshness — no branch refresh was needed; /home/runner/work/gh-aw/gh-aw is now unshallowed locally, origin/main is fetched, and HEAD (2a77c29) is already directly based on main (594778a).
• ✅ Checks (local) — make fmt, make lint, make test-unit, and make recompile passed locally with a clean working tree.
• ❓ Checks (CI) — the only live instability is the in-progress Copilot check for this comment (30710167575). The older PR action_required runs on this head (Doc Build - Deploy, AI Moderator, Agentic Commands, Content Moderation) have no failed jobs in log inspection, so they still look like manual-review/moderation gates rather than code failures. make test still reproduces the same pre-existing unrelated wasm golden drift in pkg/workflow (GH_AW_INFO_VERSION 1.0.75 → 1.0.77), not a docs-PR regression.

Actions taken: ran the pr-finisher triage flow, fetched full history plus origin/main so impacted tests could run correctly, revalidated the branch locally, and confirmed no code changes were needed.

Still needed: let the in-progress Copilot run finish. If branch protection treats the existing action_required moderation checks as blocking, a maintainer will need to complete that manual review/acknowledgement before merge.

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.84.3