DDUw keeps re-processing the 3x-rejected antigravity engine-catalog direction
The Daily Documentation Healer re-encountered the recurring antigravity engine catalog drift again this run. It remains a rejected fix direction, yet drift detectors keep re-filing it and each DDUw/healer cycle re-derives the same rejected conclusion.
Evidence (verified on main, 2026-07-22)
$ grep -ci antigravity docs/src/content/docs/reference/engines.md
0
$ grep -c antigravity pkg/parser/schemas/main_workflow_schema.json
0
$ grep -n 'NewAntigravityEngine' pkg/workflow/agentic_engine.go
500: NewAntigravityEngine(),
The engine is registered and used in production (.github/workflows/smoke-antigravity.md sets engine.id: antigravity) but intentionally kept out of the reference/schema. Nothing in code records this exclusion, so detectors keep flagging it.
Root cause
DDUw (.github/workflows/daily-doc-updater.md:164) handles not_planned issues by cross-referencing against recent commits, but it has no memory of a rejected fix direction. It cannot tell that "add antigravity to engines.md/schema" was already rejected 3x, so it re-investigates every duplicate re-filing.
Proposed fixes
1. Land the inverse code fix from #45017 (stops the re-filing at the source).
- Add an
undocumented (or hidden) boolean to the engine base config, default false, set true in NewAntigravityEngine() (pkg/workflow/antigravity_engine.go).
- Teach the DeepReport / schema-consistency drift checks (which compare registered engines vs engines listed in
engines.md / main_workflow_schema.json) to skip engines where undocumented == true.
- No
engines.md / schema edit required — the exclusion becomes documented, enforced intent.
2. Give DDUw a rejected-direction skip list. Add a step to daily-doc-updater.md that, before acting on a documentation issue, checks a persisted list of rejected drift signatures (e.g. antigravity + engines.md/schema). If matched, skip and do not re-file — mirroring the healer's site-build-ui-issues cache pattern.
Decision needed
@pelikhan — this direction has been rejected at least 3 times but keeps being re-filed (currently open: #47014). Please either (A) approve fix #1 (mark antigravity undocumented in code so detectors stop flagging), or (B) confirm the exclusion is permanent so we can encode a hard skip. Without a durable record, DDUw and the detectors will keep re-filing indefinitely.
Related
Generated by 📝 Daily Documentation Healer · sonnet46 293.5 AIC · ⌖ 35.9 AIC · ⊞ 8K · ◷
DDUw keeps re-processing the 3x-rejected antigravity engine-catalog direction
The Daily Documentation Healer re-encountered the recurring antigravity engine catalog drift again this run. It remains a rejected fix direction, yet drift detectors keep re-filing it and each DDUw/healer cycle re-derives the same rejected conclusion.
Evidence (verified on
main, 2026-07-22)Add antigravity engine to schema examples and engines.md documentation, opened 2026-07-21) requests the identical docs/schema edit that was already rejected.not_plannedduplicates in the last 7 days alone: [Code Quality] Add antigravity engine to docs and schema built-in engine catalog #46915, [Code Quality] Add engine.extensions section to concise frontmatter reference docs #46843, [Code Quality] Add antigravity engine to schema built-in engine catalog and reference docs #46842, [Code Quality] Document engine.extensions key in frontmatter reference #46573, [Code Quality] Add Antigravity engine to engines reference documentation #46572, [Code Quality] Add Antigravity engine to docs/src/content/docs/reference/engines.md #46434 (plus [Code Quality] Add antigravity engine to docs/reference/engines.md and JSON schema #45808, [Code Quality] Add antigravity engine to docs and fix dispatch_repository deprecated alias in frontmatter-full.md #46299, [Code Quality] Add missing engine to schema built-in engine catalog and remove deprecated alias examples #46075, [Code Quality] Add missing engine to schema built-in engine catalog and remove deprecated alias examples #46324 earlier). All are the same "add antigravity toengines.md+ schema" direction.antigravityandpi#44649 both closed-unmerged by admin@pelikhan; escalation [doc-healer] Decision needed: antigravity engine docs-fix direction was rejected — record exclusion in code #42847 auto-expired without a decision). [doc-healer] DDUw improvement: stop re-attempting the rejected antigravity engine catalog sync (3rd rejection: PR #44649) #45017 itself auto-expirednot_plannedon 2026-07-15 without a maintainer decision.The engine is registered and used in production (
.github/workflows/smoke-antigravity.mdsetsengine.id: antigravity) but intentionally kept out of the reference/schema. Nothing in code records this exclusion, so detectors keep flagging it.Root cause
DDUw (
.github/workflows/daily-doc-updater.md:164) handlesnot_plannedissues by cross-referencing against recent commits, but it has no memory of a rejected fix direction. It cannot tell that "add antigravity to engines.md/schema" was already rejected 3x, so it re-investigates every duplicate re-filing.Proposed fixes
1. Land the inverse code fix from #45017 (stops the re-filing at the source).
undocumented(orhidden) boolean to the engine base config, defaultfalse, settrueinNewAntigravityEngine()(pkg/workflow/antigravity_engine.go).engines.md/main_workflow_schema.json) to skip engines whereundocumented == true.engines.md/ schema edit required — the exclusion becomes documented, enforced intent.2. Give DDUw a rejected-direction skip list. Add a step to
daily-doc-updater.mdthat, before acting on adocumentationissue, checks a persisted list of rejected drift signatures (e.g.antigravity + engines.md/schema). If matched, skip and do not re-file — mirroring the healer'ssite-build-ui-issuescache pattern.Decision needed
@pelikhan— this direction has been rejected at least 3 times but keeps being re-filed (currently open: #47014). Please either (A) approve fix #1 (mark antigravityundocumentedin code so detectors stop flagging), or (B) confirm the exclusion is permanent so we can encode a hard skip. Without a durable record, DDUw and the detectors will keep re-filing indefinitely.Related
antigravityandpi#44649 (rejected fix attempts)