Parent: #76
Goal
Determine the correct Antigravity integration surface and add generated connector output only after the official path is known.
Research questions
- Does Antigravity consume VS Code Marketplace extensions directly?
- Does it support Open VSX or a separate extension registry?
- Does it have a documented MCP config path?
- Does it support rules, skills, plugins, or workspace instructions?
- Can the shared
wordpress-studio and wordpress-telemetry MCP setup be represented in its native format?
Implementation path
- Document official references before adding generated files.
- Add Antigravity generation to
scripts/build-plugins.mjs only for supported native artifacts.
- Add verifier coverage in
scripts/verify-plugins.mjs.
- Add docs and manual test steps for installation/configuration.
Acceptance criteria
- Official integration surface is documented with source links.
- Unsupported assumptions are explicitly ruled out.
- Generated output exists only if Antigravity has a documented native path.
pnpm build and pnpm verify pass after implementation.
AI assistance
- AI assistance: Yes
- Tool(s): OpenCode (GPT-5.5)
- Used for: Drafting issue scope and acceptance criteria from planning discussion.
Parent: #76
Goal
Determine the correct Antigravity integration surface and add generated connector output only after the official path is known.
Research questions
wordpress-studioandwordpress-telemetryMCP setup be represented in its native format?Implementation path
scripts/build-plugins.mjsonly for supported native artifacts.scripts/verify-plugins.mjs.Acceptance criteria
pnpm buildandpnpm verifypass after implementation.AI assistance