[docs] Update documentation for 2026-03-23

[github-actions]

Documentation Updates - 2026-03-23

This PR updates the documentation based on features merged in the last 24 hours and addresses persistent open documentation issues.

Features Documented

• dispatch_repository safe-output type — new experimental feature for cross-repo repository_dispatch events (from feat: add dispatch_repository safe-output type for repository_dispatch events (experimental) #22315)
• Engine feature comparison table — new cross-engine capability reference added to engines.md

Issues Addressed

• Closes 🔍 Multi-Device Docs Testing Report - 2026-03-22 #22226 — Broken architecture link in homepage FeatureCard (/gh-aw/introduction/architecture → /gh-aw/introduction/architecture/)
• Closes [plan] Add engine feature comparison table to engines reference docs #22147 — Missing engine feature comparison table in engines.md
• Addresses [plan] Add frontmatter field name validation with did-you-mean suggestions for common mistakes #22092 — Add "Frontmatter Field Not Taking Effect" section with common field name mistakes to troubleshooting/common-issues.md

📝 Detailed Changes & References

Changes Made

• docs/src/content/docs/index.mdx:47 — Added trailing slash to FeatureCard architecture link to fix HTTP 404 (Astro trailingSlash: 'always' requires it)
• docs/src/content/docs/reference/safe-outputs.md — Added dispatch_repository to the Available Safe Output Types list and added a full reference section with configuration fields, example YAML, and security notes
• docs/src/content/docs/reference/engines.md — Added "Engine Feature Comparison" table covering max-turns, max-continuations, web-fetch, web-search, engine.agent, engine.api-target, and tools allowlist across Copilot/Claude/Codex/Gemini
• docs/src/content/docs/troubleshooting/common-issues.md — Added "Frontmatter Field Not Taking Effect" section with a table of common field name mistakes (agent: vs engine:, mcp-servers: vs tools:, etc.)

Merged PRs Referenced

• feat: add dispatch_repository safe-output type for repository_dispatch events (experimental) #22315 — feat: add dispatch_repository safe-output type for repository_dispatch events (experimental)
• Rename tools.github.repos to tools.github.allowed-repos #22311 — Rename tools.github.repos to tools.github.allowed-repos (docs already updated in that PR)
• Add per-handler staged mode to all safe output types #22284 — Add per-handler staged mode to all safe output types (implementation fix, docs already covered)

Notes

• The dispatch_repository feature is marked experimental in both the code and the docs.
• The engine comparison table is based on confirmed behavior from frontmatter-full.md schema comments and tools.md documentation.
• Issue [plan] Add frontmatter field name validation with did-you-mean suggestions for common mistakes #22092 (frontmatter validation with did-you-mean suggestions) is a compiler feature that has not landed yet; the docs addition addresses the documentation gap independently.

Note

🔒 Integrity filter blocked 5 items

The following items were blocked because they don't meet the GitHub integrity level.

• #22335 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #22296 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #20391 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #20207 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #16498 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Documentation Updater · ◷

• expires on Mar 24, 2026, 4:29 AM UTC