Integrate Antigravity CLI and Gemini CLI migration plan into OpenAI CLI

[knowledge0101010-lang]

We need a practical integration path to absorb the useful surface area of Google Antigravity CLI and Kali's gemini-cli packaging into OpenAI CLI, while standardizing around the OpenAI CLI architecture.

Current observations:

• openai-cli is a Go-based CLI for the OpenAI REST API with resource-oriented commands, API key / admin key auth, and file-argument handling.
• Antigravity CLI is a terminal-first agentic CLI with shared agent engine, permissioned edits, command execution, SSH support, and Google Sign-In / keyring auth.
• google-antigravity/antigravity-sdk-python exposes agent/session/tooling concepts, triggers, hooks, MCP integration, and a compiled runtime.
• gemini-cli in Kali appears to be packaging for a separate Gemini CLI distribution.

Requested work:

1. Define a migration boundary for what can be merged into OpenAI CLI directly versus what must remain an adapter or extension.
2. Add or formalize Codex/OpenAI-native telemetry signals for agent sessions, edits, tool calls, and command execution.
3. Rework auth/install/deploy paths to eliminate Google-specific assumptions.
4. Identify the minimum set of files/modules for an initial PR, then split follow-up PRs for telemetry, auth, and UX.
5. Document incompatibilities and non-goals clearly.

Suggested first milestone:

• Add a design doc or roadmap issue that maps Antigravity CLI and gemini-cli behaviors onto the OpenAI CLI command model, with a PR-sized implementation plan.