[docs] Update documentation for features from 2026-05-13

[github-actions]

Documentation Updates - 2026-05-13

This PR updates the documentation based on user-facing features merged in the last 24 hours.

Features Documented

• firewall.effective-token-steering budget-warning injection (from Bump AWF to v0.25.44 and add firewall.effective-token-steering compiler support #31796)
• concurrency.queue and features.group-concurrency-queue opt-out (from Add concurrency.queue support and queue-aware conclusion job defaults #31764)
• features.ghes-artifact-compat per-workflow frontmatter opt-in and GH_AW_FEATURES env var (from feat: add GHES-compatible artifact action versions via feature flag #31664)

Detailed Changes and References

Changes Made

• docs/src/content/docs/reference/network.md: added an Effective Token Steering subsection under firewall configuration documenting firewall.effective-token-steering: true, the warning thresholds (80/90/95/99%), and the AWF v0.25.44 version gate.
• docs/src/content/docs/reference/concurrency.md: added a Queue Behavior section explaining single vs max, documented that compiler-generated groups emit queue: max by default, and described the features.group-concurrency-queue: false opt-out. Updated the Conclusion Job Concurrency example to show the generated queue: max field.
• docs/src/content/docs/reference/enterprise-configuration.md: added an Enable per workflow via features subsection covering features.ghes-artifact-compat: true frontmatter and the GH_AW_FEATURES=ghes-artifact-compat env var alternative, plus the fail-fast behavior when v3 artifact pins are missing.

Merged PRs Referenced

• Bump AWF to v0.25.44 and add firewall.effective-token-steering compiler support #31796 - Bump AWF to v0.25.44 and add firewall.effective-token-steering compiler support
• Add concurrency.queue support and queue-aware conclusion job defaults #31764 - Add concurrency.queue support and queue-aware conclusion job defaults
• feat: add GHES-compatible artifact action versions via feature flag #31664 - feat: add GHES-compatible artifact action versions via feature flag

Skipped Issues

None - the open documentation-labeled issues in this repository are bot-generated activity reports (skill optimizer, glossary scan, spdd), not unaddressed documentation gaps.

Notes

• frontmatter-full.md is auto-generated from the JSON schema and was not edited; concurrency.queue will appear there on the next schema regeneration.
• Other merged user-facing PRs in the 24h window (centralized slash-command strategy Add centralized slash-command trigger strategy with compiler-generated agentic_commands router workflow #31605, on.skip-author-associations Add on.skip-author-associations pre-activation gating by author_association #31836, pre-agent-steps/post-steps allowlist Docs/tests: include pre-agent-steps and post-steps in shared import allowlist #31912, gh aw fix codemods Add default gh aw fix codemod to lowercase discussion trigger categories in frontmatter #31872 and Add gh aw fix codemod to rewrite single-quoted tools.bash args safely #31874, gh aw first-class runtime Treat gh aw as a first-class runtime with release setup-cli injection, dev source build, and firewall domains #31622, npm/pip validation messages Clarify npm and pip package name validation errors #31822, strict-mode opt-out Align strict-mode compatibility: allow Playwright MCP warnings and honor workflow-level strict opt-out for pull_request_target #31914, top-level command rejection Reject unused top-level command in main workflow frontmatter schema #31750) were verified against existing docs and already have coverage in triggers.md, command-triggers.md, frontmatter.md, maintaining-repos.md, imports.md, and the CLI/troubleshooting pages.

Generated by Daily Documentation Updater · ● 16.3M · ◷

• expires on May 14, 2026, 11:34 AM UTC

[github-actions]

Hey team 👋 — thanks for this automated documentation sweep covering firewall.effective-token-steering, concurrency.queue / features.group-concurrency-queue, and features.ghes-artifact-compat. The changes are well-scoped, clearly described, and directly tied to recently merged features.

One mechanical flag from the checklist:

• No test changes detected — for a docs-only PR this is expected and not a real concern, but it trips the automated quality signal. If there are any doc-test or link-validation fixtures that should cover new content in network.md, concurrency.md, or enterprise-configuration.md, it may be worth wiring them into the automation pipeline.

If you would like to address that proactively, here's a ready-to-use prompt:

Check whether the docs site has any automated link-validation or content-lint tests (e.g. in tests/ or scripts/).
If so, verify that the new sections added in:
  - docs/src/content/docs/reference/network.md
  - docs/src/content/docs/reference/concurrency.md
  - docs/src/content/docs/reference/enterprise-configuration.md
are covered, and add or update tests as needed.

Otherwise this looks ready for a quick maintainer review. 🤖

Generated by Contribution Check · ● 11.9M · ◷

[pelikhan]

@copilot use --ghes or aw.config option.

[Copilot]

Added a tip note pointing readers to the --ghes CLI flag and ghes: true in aw.json as the broader alternatives for repository-wide coverage. Done in the latest commit.

[pelikhan]

@copilot this feature does not exist

[Copilot]

Removed the entire features.ghes-artifact-compat per-workflow frontmatter section and the GH_AW_FEATURES env var content — the file is back to its pre-PR state for that page.