Retire the Gemini CLI / Antigravity preview

[Astro-Han]

Problem

Maka still maintains a Gemini CLI / Antigravity account-provider surface that has never been executable. The provider has no Runtime OAuth enrollment contract or runnable adapter, and Desktop only retains disabled IPC, preload, copy, metadata, and compatibility branches.

The project has decided to retire this preview instead of completing it.

Scope

• Remove gemini-cli from the maintained provider registry and generated metadata.
• Remove the Antigravity Desktop IPC, preload bridge, typed contract, settings branches, fixtures, and current documentation.
• Reject creation of new gemini-cli connections.
• Retire legacy persisted gemini-cli entries without preventing the remaining connection catalog from loading; clear the default target when it referenced a retired entry.
• Preserve the ordinary google Gemini API-key provider unchanged.

Acceptance criteria

• gemini-cli is no longer a supported provider type.
• No Antigravity login or disabled preview bridge remains in current product surfaces.
• A legacy persisted entry cannot block supported connections from loading.
• The ordinary Google Gemini API-key path remains available.
• Focused tests, affected typechecks, and formatting checks pass.

Non-goals

• Changing the ordinary Google Gemini API-key provider.
• Adding a replacement Google account OAuth integration.
• Removing historical references that only document upstream Gemini CLI behavior or archived architecture.

---

This issue was identified and updated with AI assistance (Codex). A human contributor reviewed the decision and owns the submission.

[Astro-Han]

I’d like to take this. I’ll retire the Gemini CLI / Antigravity preview while preserving the ordinary Google Gemini API-key provider. I’ll first make the legacy persisted-record behavior explicit, then remove the unavailable Runtime, Core, Desktop, metadata, and bridge surfaces as one focused change.

Posted by Codex after human approval.