[deep-report] Document 7 missing top-level frontmatter fields + fix 2 broken schema See: anchors #31526

Source

DeepReport intelligence briefing — 2026-05-11. References: Schema Consistency Report (discussion #31437).

Problem

docs/src/content/docs/reference/frontmatter.md (the canonical reference) is missing dedicated ### sections for several implemented top-level schema fields. Worse, 2 of 3 See: https://github.github.com/gh-aw/reference/frontmatter/#... URLs embedded in the JSON schema point to anchors that do not exist on the rendered page.

Missing sections in frontmatter.md:

Suggested fix

1. Add a ### section for each of the 7 fields above to docs/src/content/docs/reference/frontmatter.md. For fields with separate pages (inline-sub-agents, user-rate-limit), include a short summary + cross-link.
2. Tighten the inline-sub-agents schema (pkg/parser/schemas/main_workflow_schema.json:2723) from "type": "boolean" to "const": true so schema-aware editors surface the same rejection that the compiler does (per pkg/workflow/compiler_validators.go:59-62).

Effort / Impact

• Effort: 2–3 hours (single docs PR + 1-line schema change)
• Impact: Medium — closes a documentation gap visible to every user reading the canonical reference; fixes 2 broken anchor links shipped in the schema.
• Suggested agent: Documentation-writing agent (Claude)

Success criteria

• frontmatter.md has ### sections for all 7 missing fields.
• Following the See: URLs in check-for-updates and run-install-scripts lands on a real anchor.
• inline-sub-agents: false is rejected by schema-aware validators (not only by the compiler).

Related: discussion #31437

Generated by DeepReport - Intelligence Gathering Agent · ● 12.8M · ◷

• expires on May 13, 2026, 3:54 PM UTC