[github-actions]

Documentation Updates - 2026-11-13

Document four user-facing behaviors from recent merges in three existing pages. Reviewed 36 merged PRs and their corresponding main-branch commits from 2026-11-12 10:41 UTC through 2026-11-13 10:41 UTC, plus accessible open and recently closed documentation issues and recent cookie reports.

This PR is a draft because dependency certificate failures blocked the required repository gate and documentation build. Source checks, workflow-schema validation, and diff checks passed.

Features Documented

• Preview issues.types: [status_changed] syntax and event-availability limits (#77179).
• Comment-memory History retention, legacy attribution, and size-limit recovery (#77335).
• Terminal GitHub-inference cybersecurity-policy rejections across Copilot, Claude, and Codex (#77351).
• How to investigate report_incomplete when the agent job succeeds but conclusion fails (#77183).

Detailed Changes and References

Changes Made

• docs/src/content/docs/reference/triggers.md: add the supported status-change trigger and qualify GitHub preview availability.
• docs/src/content/docs/patterns/memory-ops.md: explain the managed History section, preservation across updates and clears, footer independence, and recovery when the comment becomes too large.
• docs/src/content/docs/troubleshooting/common-issues.md: describe policy-rejection classification and the diagnostic path through conclusion summaries, the agent artifact, and gh aw audit.

Already Documented Recent Changes

Logs JSONL streaming (#77304), ledger promotion (#77331), buffered review dependencies (#77232), model-routing guidance (#76985 and #77206), budget notices (#77087), shared safe-output defaults (#77050), and Atomic unified sessions (#77052) already have relevant content. Other reviewed changes concern internal refactoring, tests, dependency maintenance, or repository automation.

Validation

• Passed: both issue-trigger YAML examples validated against the current main_workflow_schema.json using PyYAML and jsonschema.
• Passed: source checks against the current compiler schema, comment-memory handler, shared provider-policy detector, three engine harnesses, and incomplete-task diagnostics.
• Passed: git diff --check; exactly three intended files committed; clean working tree.
• Blocked: make agent-report-progress stopped at the Go 1.27.4 toolchain download because TLS certificate validation failed. Unit tests and later gate stages were not reached.
• Blocked: make build-docs stopped during npm ci with DEPTH_ZERO_SELF_SIGNED_CERT; Astro compilation and link validation were not reached.
• Certificate checks were left unchanged. No workflows were dispatched.

Skipped Issues

Skipped Issues

• [cli-consistency] CLI Consistency Issues - 2026-11-12 #77161 — requires CLI implementation fixes for exit codes, unknown help topics, and repository parsing; outside this content update.
• Provider-based authentication for Claude, Copilot, Codex. #16498 — current authentication docs explicitly describe unsupported Claude OAuth tokens and supported API-key/WIF alternatives; broader provider and wizard changes require separate implementation work.
• Document how to Playwright-test a docker-compose stack running on the host from the firewalled agent #51273 — Compose-stack topology guidance requires confirmation against the current supported runtime. Docker execution is unavailable in this run, so no unverified topology example was added.
• Docs: guidelines for configuring Go module/build cache in a security-conscious way #27886 — basic Go cache examples already exist in the FAQ and sandbox reference; the broader request for cache-integrity and trust-boundary guidance remains open for a dedicated source-backed treatment.
• Add SOC-2 compliance patterns doc page #41746 — existing reference/compliance-patterns.md already covers human assignment, publishing identity, independent review, and evidence retention.
• OWASP Agentic Top 10 compliance evaluation: gap analysis across gh-aw, firewall, and mcpg #28770 — cross-project security evaluation and proposed runtime controls require a separate security review.
• 🔍 Multi-Device Docs Testing Report - 2026-11-09 #76154 — site-build/UI: needs Astro/site-build agent.
• 🔍 Multi-Device Docs Testing Report - 2026-11-07 #75616 — site-build/UI: needs Astro/site-build agent.
• docs: lead model-choice guidance with default routing and model: router #76983 and Update the token-steering and max-ai-credits docs for AWF's on-by-default budget notices #77053 — resolved by merged docs: lead model-choice guidance with default routing and model: router #76985 and docs: describe AWF's on-by-default budget notices for token-steering and max-ai-credits #77087 respectively; verified current content.
• [cli-consistency] CLI Consistency Issues - 2026-11-11 #76872, [cli-consistency] CLI Consistency Issues - 2026-11-10 #76525, and [cli-consistency] CLI Consistency Issues - 2026-11-05 #75181 — referenced CLI documentation gaps are already covered in the current CLI reference; remaining implementation findings are outside this documentation update.
• [workflow-style] Normalize report formatting for non-compliant workflows #76247, [workflow-style] Normalize report formatting for non-compliant workflows #75677, and [workflow-style] Normalize report formatting for non-compliant workflows #75172 — workflow-prompt formatting requests concern automation authoring rather than site content; deferred to the workflow-style updater.

Notes

The requested .github/instructions/documentation.instructions.md does not exist in this checkout; followed .github/skills/documentation/SKILL.md and the repository developer validation guidance. The PageIndex revision matched HEAD, and selected sections were checked against current source. Some issue content and PR file listings were unavailable under the integrity policy, so the review is limited to accessible results and current source. Steering issue #77416 had no comments at the final check.

AI dictionary alignment summary: reviewed agent, sub-agent, provider, and inference terminology using the supplied secondary reference; retained existing repository wording and introduced no new definitions. No terminology conflicts required resolution.

Next Actions

Rerun the repository gate and documentation build when dependency downloads have valid certificate trust, then review the draft. The skipped security, runtime, CLI, and site-build items remain separate follow-up work.

Generated by 📝 Daily Documentation Updater · codex · routed: gpt61 high · ~104 AIC · ⌖ ~2 AIC · ⊞ 640 · ◷

• expires on Nov 14, 2026, 2:50 AM UTC-08:00

[Copilot]

🟢 Approval recommended

No active review issues were identified, and the documentation changes clearly cover the newly implemented trigger, comment-memory, inference-policy, and incomplete-run behaviors.

No open issues 🎉

What changed in this PR

This PR updates three documentation pages to describe recently implemented trigger, comment-memory, inference-policy, and incomplete-run behaviors.

Changes:

• Documents the preview issues.types: [status_changed] trigger syntax and availability caveat.
• Explains comment-memory History retention, legacy attribution, and size-limit recovery.
• Adds troubleshooting guidance for cybersecurity-policy rejections and report_incomplete conclusions.

File	Description
docs/​src/​content/​docs/​troubleshooting/​common-issues.md	Adds diagnostics for GitHub inference policy rejections and incomplete agent-task results.
docs/​src/​content/​docs/​reference/​triggers.md	Documents the preview status_changed issue-trigger syntax and delivery limitations.
docs/​src/​content/​docs/​patterns/​memory-ops.md	Describes managed comment-memory History retention, legacy attribution, and oversized-comment recovery.

_{Review effort: Lite (dynamic)}