Skip to content

[doc-healer] DDUw improvement: converge recurring antigravity engines.md drift via consistency-check fix (docs PR #48678 rejecte [Content truncated due to length] #49227

Description

@github-actions

Overview

The antigravity engine is a fully-registered runtime engine (pkg/workflow/antigravity_engine.go, id: "antigravity", experimental: true, wired into the catalog at pkg/workflow/agentic_engine.go:511) with live workflow usage (.github/workflows/smoke-antigravity.md), yet it is absent from docs/src/content/docs/reference/engines.md. An automated schema-consistency check keeps re-filing this same drift (#48059, #48218, #48323, #48800, #48670 — "13 re-files in 7 days" per prior escalation #47875).

Rejection signal — do not re-attempt the docs-only fix

The obvious docs-only fix has already been tried and rejected:

  • PR fix(docs): add antigravity to engines reference doc + add engine-doc sync test #48678"fix(docs): add antigravity to engines reference doc + add engine-doc sync test" (author: Copilot). It added antigravity to the Available Coding Agents / Feature Comparison / version-pinning tables in engines.md and added a TestEngineDocSync CI gate enforcing parity between the runtime engine registry and the reference doc.
  • It was closed unmerged by @pelikhan (confirmed repository collaborator) on 2026-07-28 with no accompanying comment or review.

A closed-unmerged docs PR from a maintainer is a strong signal that "add every registered engine to the manual engines.md table" is not the desired direction. Two other attempts (#44480 WIP, #46367 refactor) also never merged. This healer is therefore not re-opening the docs edit.

Proposed inverse direction (code / consistency-check side)

The recurring re-files come from a schema/engine consistency check that flags any registered engine ID missing from engines.md. The engine in question is marked experimental: true. If maintainers intentionally omit experimental engines from the curated reference table, the fix belongs in the check, not the docs:

  1. Teach the consistency check to respect experimental — exclude engines with experimental: true (or otherwise not-yet-GA) from the "missing from engines.md" comparison, so it stops re-filing drift for engines that are deliberately undocumented.
  2. OR decide experimental engines do belong in the table — in which case merge a variant of fix(docs): add antigravity to engines reference doc + add engine-doc sync test #48678 and add the TestEngineDocSync gate so the drift is caught at PR time and never recurs.

Either path converges the loop; the current manual re-add cycle does not. The decision is a maintainer product/docs-policy call, not something this automated healer should guess at.

Next step — maintainer decision requested

@pelikhan — you closed #48678 unmerged. Could you confirm the intended direction so this drift stops recurring?

References

Generated by 📝 Daily Documentation Healer · haiku45 · 178.7 AIC · ⌖ 30.9 AIC · ⊞ 8.5K ·

  • expires on Aug 2, 2026, 4:08 PM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions