[docs] Update documentation for features from 2026-06-02

[github-actions]

Documentation Updates - 2026-06-02

This PR documents two frontmatter fields that existed in the JSON Schema but had no entry in the curated frontmatter reference, and aligns them with recent code changes from the last 24 hours.

Features Documented

• check-for-updates (top-level, default true) — controls the compile-time version update check in the activation job. Previously undocumented in curated docs.
• runtimes.<runtime>.run-install-scripts (default false) — now the only valid form for this field after the top-level variant was removed in Remove deprecated top-level run-install-scripts frontmatter field #36387. Documented under the existing Runtimes section.

Both new headings use the bare field-name slug so the in-schema anchor links (#check-for-updates, #run-install-scripts) emitted in main_workflow_schema.json descriptions now resolve to real headings.

📝 Detailed Changes & References

Changes Made

• docs/src/content/docs/reference/frontmatter.md:
  • Added an h3 check-for-updates reference section after Strict Mode, describing the default-on activation-job version check and the strict-mode restriction.
  • Added an h4 run-install-scripts subsection inside the Runtimes section, documenting the per-runtime supply-chain install-script opt-in, its compile-time warning / strict-mode error, and noting that the removed top-level form must now be configured under a runtime block.

Triggering Code Change

• Remove deprecated top-level run-install-scripts frontmatter field #36387 — Remove deprecated top-level run-install-scripts frontmatter field. The field is now valid only under runtimes.*; the docs were updated to reflect the runtime-scoped model.

Pre-existing Gap Addressed

• [deep-report] [quick-win] Document 3 undocumented top-level frontmatter fields + fix broken in-schema anchors #36275 ([deep-report] [quick-win] Document 3 undocumented top-level frontmatter fields + fix broken in-schema anchors) was closed as completed, but a direct content check showed check-for-updates and run-install-scripts were still absent from the curated reference and their in-schema anchors were still broken. This PR resolves both. (Issue already closed; not re-closing via keyword.)

Last-24h merged PRs reviewed (no user-doc change required)

• Emit daily ET guardrail by default; disable only on explicit -1 #36392 — daily ET guardrail emission made default-on with runtime gating; the user-facing contract ("disabled when omitted", "-1 disables") is unchanged, so existing docs in frontmatter.md / compiler-enterprise-environment-controls.md remain accurate.
• Remove deprecated top-level run-install-scripts frontmatter field #36387 — top-level run-install-scripts removal (documented here).
• [q] Update chaos-pr-bundle-fuzzer schedule to weekly #36385/Remove vestigial applyTo from parser validFields allowlist #36309 — removed permissions.copilot-requests: write recommendation / vestigial applyTo: no remaining recommendation or workflow-frontmatter usage in curated docs.
• Make timeout-minutes a templatable integer in schema + custom job compilation #36314 — timeout-minutes made a templatable integer (schema/compiler internal; expression usage already implied by templatable-integer docs).
• Clarify push_to_pull_request_branch behavior for multi-checkout workflows #36238 — push_to_pull_request_branch multi-checkout clarification was an agent-prompt file change, not user docs.
• [log] Add debug logging to 5 sparsely-logged Go files #36403/Remove estimated cost from audit-workflows report #36356/Add on-demand token audit workflow with date-range dispatch input #36412 and others — internal logging, workflow/CI, and lock-file changes with no user-facing surface.

Skipped Issues

• [deep-report] [quick-win] Document 3 undocumented top-level frontmatter fields + fix broken in-schema anchors #36275 — disable-model-invocation: the third field named in this issue is left undocumented in this run. Its schema description ("Controls whether the custom agent should disable model invocation") is ambiguous about scope and behavior, and it has no broken anchor link to fix. Documenting it accurately needs maintainer clarification rather than a guessed description.
• [cli-tools-test] compile: --workflow-name CLI flag undocumented/incorrect (should be --workflows) #36076 — compile --workflow-name vs --workflows: the incorrect flag appears only in an internal workflow-prompt example (Daily CLI Tools Tester), not in user-facing docs under docs/src/content/docs/. No curated-doc change applies.

Notes

• The two new headings deliberately use code-formatted bare field names (### \check-for-updates`, #### `run-install-scripts`) rather than the page's usual descriptive ### Name (`field:`)style. This is required so the heading slugs exactly match the#check-for-updates/#run-install-scriptsanchors hard-coded in the schema descriptions. If maintainers prefer descriptive headings, the alternative is a one-line update to theSee:links inpkg/parser/schemas/main_workflow_schema.json(plus a regeneration of the generatedfrontmatter-full.md`), which was kept out of scope for this docs-only run.
• No schema or generated files were modified, so the schema-consistency check is unaffected.

Generated by 📝 Daily Documentation Updater · opus48 2.6M · ◷

• expires on Jun 3, 2026, 4:09 AM UTC-08:00

[github-actions]

@copilot please rerun checks and summarize any remaining blockers.

Generated by 👨‍🍳 PR Sous Chef · gpt54 12M · ◷