[deep-report] Restore frontmatter anchor coverage for update-check and runtime flags

[Copilot]

frontmatter schema text linked to #check-for-updates, but the curated reference page had no matching heading. The same page also had zero curated coverage for run-install-scripts.

• Curated frontmatter coverage additions

  • Added a dedicated check-for-updates section to docs/src/content/docs/reference/frontmatter.md so the schema link target now exists.
  • Added a minimal, user-facing run-install-scripts section with concise behavior notes.

• Curated docs alignment with current fields

  • Removed the disable-model-invocation section from the curated reference page because that field has been removed.

• Anchor + schema-link alignment

  • The heading format (### \check-for-updates`) creates the expected #check-for-updates` doc anchor used by schema descriptions.

• Docs content style

  • Kept additions intentionally minimal and reference-oriented: one-paragraph semantics + small YAML example per field.

check-for-updates: true

runtimes:
  node:
    run-install-scripts: true

[pelikhan]

@copilot this field is removed and should be removed from the docs

[Copilot]

Removed from the curated frontmatter docs in commit e62eed4.

[github-actions]

Hey @Copilot 👋 — thanks for this documentation fix! Restoring the #check-for-updates anchor and adding the run-install-scripts section keeps the frontmatter reference properly aligned with the schema links — that's a solid housekeeping win.

One thing would help before this lands:

• Split out the lock file changes — .github/workflows/dead-code-remover.lock.yml contains a batch of hash-token rotations (heredoc delimiter strings like GH_AW_PROMPT_18306a05ecb4d558_EOF → GH_AW_PROMPT_78a1d3ec5c7dcc5e_EOF) that are unrelated to the frontmatter docs work. These look like an incidental workflow regeneration. Keeping them in a separate commit or PR makes it easier for reviewers to confirm the docs change in isolation.

If you would like a hand tidying this up:

In PR branch `copilot/deep-report-fix-check-for-updates-anchor`, the file `.github/workflows/dead-code-remover.lock.yml` contains hash-token rotations (heredoc delimiter renames) that are unrelated to the frontmatter documentation changes in `docs/src/content/docs/reference/frontmatter.md`.

Please:
1. Revert the changes to `.github/workflows/dead-code-remover.lock.yml` in this branch so the PR contains only the frontmatter documentation additions.
2. If the lock file regeneration is genuinely needed, open it as a separate PR with a clear explanation of why the hashes changed.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• patchdiff.githubusercontent.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "patchdiff.githubusercontent.com"

See Network Configuration for more information.

Generated by ✅ Contribution Check · sonnet46 4.2M · ◷

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.