docs: add note about templatable fields in safe outputs

[Copilot]

The safe-outputs.md user guide had no explanation of templatable fields, leaving users unaware they could supply GitHub Actions expressions (e.g., ${{ inputs.foo }}) in place of literal values for certain config fields.

Adds a Templatable Fields section under ## Global Configuration Options covering:

• Templatable booleans — footer, group, close-older-issues, hide-older-comments, close-older-discussions, draft, allow-empty, auto-merge, report-as-issue, unassign-first
• Templatable integers — max on all safe output types
• Runtime error semantics (non-boolean → false; non-integer → operation fails)
• Compile-time rejection of free-form strings that aren't ${{ ... }} expressions

safe-outputs:
  create-issue:
    group: ${{ inputs.group-issues }}     # boolean expression
    close-older-issues: true              # literal boolean
    max: ${{ inputs.max-issues }}         # integer expression
  create-pull-request:
    draft: ${{ inputs.draft-pr }}         # boolean expression

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /opt/hostedtoolcache/node/24.13.0/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Add note about templetable fields in safe outputs

Custom agent used: technical-doc-writer
AI technical documentation writer for GitHub Actions library using GitHub Docs voice

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Pull request overview

This PR adds documentation about templatable fields in safe outputs, explaining that certain configuration fields can accept GitHub Actions expressions (e.g., ${{ inputs.foo }}) in addition to literal values. This enables dynamic runtime configuration through workflow inputs and other GitHub Actions context values.

Changes:

• Added a new "Templatable Fields" section to the safe-outputs.md documentation explaining templatable booleans and integers
• Included examples showing both literal values and GitHub Actions expressions
• Documented runtime error semantics for invalid values
• Added an unrelated entry to the agent-factory-status table

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
docs/src/content/docs/reference/safe-outputs.md	Added comprehensive documentation for templatable fields, including boolean and integer field types with clear examples and error handling semantics
docs/src/content/docs/agent-factory-status.mdx	Added "Weekly Editors Health Check" workflow entry to the status table (appears unrelated to PR purpose)

---

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

[Copilot]

This change appears to be unrelated to the PR's stated purpose of adding documentation about templatable fields in safe outputs. The addition of the "Weekly Editors Health Check" workflow to the status table seems like an auto-generated update that was included inadvertently. Consider whether this should be in a separate PR or if the PR description should be updated to mention this workflow addition.