[Daily Report] Documentation Quality Status Report - 2026-07-23

[github-actions]

Overview

Open issues this morning point to two documentation-quality gaps. Both are discoverability problems rather than runtime bugs: the canonical frontmatter reference is missing a supported field, and the engine catalog/docs understate supported engines.

Key Issues

• [Code Quality] Add engine.extensions field to frontmatter.md reference docs #47522 "[Code Quality] Add engine.extensions field to frontmatter.md reference docs". The field is already documented in the specialized engine reference at docs/src/content/docs/reference/engines.md:435-437, while the canonical frontmatter overview has engine: and engine.driver: but no engine.extensions section (docs/src/content/docs/reference/frontmatter.md:146-156). This is a documentation gap in the main reference.
• [Code Quality] Add Antigravity engine to user-facing docs and schema built-in engine catalog #47521 "[Code Quality] Add Antigravity engine to user-facing docs and schema built-in engine catalog". The feature is already discoverable in docs/src/content/docs/setup/cli.md:258-266 and docs/src/content/docs/reference/model-tables.md:59, but the canonical engine reference/catalog is still missing from docs/src/content/docs/reference/engines.md and pkg/parser/schemas/main_workflow_schema.json.
• Closely related duplicates: [Code Quality] Add engine.extensions section to docs/reference/frontmatter.md #47442, [Code Quality] Add antigravity engine to docs/reference/engines.md and main_workflow_schema.json #47441, [Code Quality] Add antigravity engine to schema built-in engine catalog and engine reference docs #47388, and [Code Quality] Add antigravity engine to docs and JSON schema engine catalog #47306 repeat the same two gaps across frontmatter, engine docs, and schema catalog wording.

Already Covered

• engine.extensions already has an explanation in the engine-specific docs, so the fix is to link it from the main frontmatter reference rather than rewrite the concept.
• antigravity already appears in CLI help and model tables, so the missing piece is the authoritative engine catalog/schema surface, not total absence from the repo.

Gaps

• No open issue surfaced a separate help/article page for these features; the current problems are concentrated in reference-doc discoverability and schema consistency.

Next Step

• Update the canonical reference pages so the main docs match the runtime/schema surfaces, then close the duplicate issues by pointing to the updated source of truth.

Generated by 💻 Dev · gpt54 5.93 AIC · ⌖ 0.365 AIC · ⊞ 34.2K · ◷
_{Add label dev to run again}

• expires on Jul 30, 2026, 1:36 AM UTC-08:00