Description
The antigravity engine is registered in the runtime (pkg/workflow/agentic_engine.go:494-501) and used in real workflows (.github/workflows/smoke-antigravity.md), but it is completely absent from:
pkg/parser/schemas/main_workflow_schema.json — no antigravity string anywheredocs/src/content/docs/reference/engines.md — not listed as a supported enginedocs/src/content/docs/reference/frontmatter-full.md — engine catalog is out of date
This causes schema validation to miss or reject valid workflows using antigravity, and confuses users looking at the documentation.
Suggested Changes
- Add
antigravity to built-in engine ID descriptions/enum-like surfaces in pkg/parser/schemas/main_workflow_schema.json
- Update
docs/src/content/docs/reference/engines.md to include antigravity in the available engine list with a description and example
- Regenerate/update
docs/src/content/docs/reference/frontmatter-full.md to reflect current runtime engine support
- Consider constraining built-in engine IDs with an explicit
enum in the schema to prevent future drift
- Demote
dispatch_repository deprecated alias to a clearly labeled migration note (not a peer of canonical engine IDs)
Files Affected
pkg/parser/schemas/main_workflow_schema.jsondocs/src/content/docs/reference/engines.mddocs/src/content/docs/reference/frontmatter-full.md
Success Criteria
antigravity appears in schema engine list and docs- Schema validation accepts workflows with
engine: antigravity
dispatch_repository is clearly marked deprecated in docs- All schema tests pass
Source
Extracted from Schema Consistency Check - 2026-07-24
Priority
High — schema and docs disagree with runtime; affects correctness of schema validation.
🔍 Task mining by Discussion Task Miner - Code Quality Improvement Agent · sonnet46 · 51.1 AIC · ⌖ 8.26 AIC · ⊞ 7.1K · ◷
Description
The
antigravityengine is registered in the runtime (pkg/workflow/agentic_engine.go:494-501) and used in real workflows (.github/workflows/smoke-antigravity.md), but it is completely absent from:pkg/parser/schemas/main_workflow_schema.json— noantigravitystring anywheredocs/src/content/docs/reference/engines.md— not listed as a supported enginedocs/src/content/docs/reference/frontmatter-full.md— engine catalog is out of dateThis causes schema validation to miss or reject valid workflows using
antigravity, and confuses users looking at the documentation.Suggested Changes
antigravityto built-in engine ID descriptions/enum-like surfaces inpkg/parser/schemas/main_workflow_schema.jsondocs/src/content/docs/reference/engines.mdto includeantigravityin the available engine list with a description and exampledocs/src/content/docs/reference/frontmatter-full.mdto reflect current runtime engine supportenumin the schema to prevent future driftdispatch_repositorydeprecated alias to a clearly labeled migration note (not a peer of canonical engine IDs)Files Affected
pkg/parser/schemas/main_workflow_schema.jsondocs/src/content/docs/reference/engines.mddocs/src/content/docs/reference/frontmatter-full.mdSuccess Criteria
antigravityappears in schema engine list and docsengine: antigravitydispatch_repositoryis clearly marked deprecated in docsSource
Extracted from Schema Consistency Check - 2026-07-24
Priority
High — schema and docs disagree with runtime; affects correctness of schema validation.