feat: implement native Antigravity CLI adapter and bump version to 8.0.4

[9thLevelSoftware]

No description provided.

[gemini-code-assist]

Code Review

This pull request introduces native integration and support for the brand new Antigravity CLI (agy), the successor to Google Gemini CLI. It adds a comprehensive adapter configuration, updates the installer script to handle the new plugin surface, registers the runtime metadata, and updates relevant documentation, tests, and checklists. The review feedback highlights a potential TypeError in bin/install.js when accessing properties of pkg.author and pkg.repository without optional chaining, as well as a minor grammatical typo in docs/index.html.

[gemini-code-assist]

Accessing nested properties of pkg.author and pkg.repository directly can cause a TypeError if these fields are undefined or null in package.json. Since Node.js 18+ is required, we should use optional chaining (?.) to safely access these properties and prevent potential installer crashes.

Suggested change

	const manifest = {
	name: "legion",
	version: pkg.version,
	description: pkg.description,
	author: pkg.author.name || pkg.author,
	repository: pkg.repository.url || pkg.repository,
	keywords: pkg.keywords,
	license: pkg.license
	};
	const manifest = {
	name: "legion",
	version: pkg.version,
	description: pkg.description,
	author: pkg.author?.name || pkg.author,
	repository: pkg.repository?.url || pkg.repository,
	keywords: pkg.keywords,
	license: pkg.license
	};

[gemini-code-assist]

The phrase 'execute coordinate parallel waves' contains a grammatical typo. It should be updated to 'execute coordinated parallel waves' or 'coordinate parallel waves' for better readability.

                    <p>Leverages Antigravity's native subagent spawn mechanics to execute coordinated parallel waves with filesystem-based result polling.</p>

[kilo-code-bot]

Code Review Roast 🔥

Verdict: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
🚨 critical	1
⚠️ warning	0
💡 suggestion	0
🤏 nitpick	0

Issue Details (click to expand)

File	Line	Roast
skills/workflow-common/SKILL.md	523-534	Division counts are stale — claiming Engineering has 7 agents when there are actually 9, Product has 3 when there are 4, Marketing has 8 when there are 4, Testing has 7 when there are 6, Support has 6 when there are 4, Specialized has 3 when there are 4. TOTAL_AGENTS = 52 is wrong; the actual count is 49.

---

🏆 Best part: The Antigravity CLI adapter implementation is clean and follows established patterns from other certified adapters. The plugin.json manifest structure and installation flow are well-thought-out.

💀 Worst part: The Division Constants table in skills/workflow-common/SKILL.md (lines 519-534) is a museum piece. It predates this PR and hasn't been updated to match reality.

📊 Overall: Like a restaurant menu where the prices changed but nobody told the kitchen — the code serves 49 agents but the docs still think it's running a buffet for 52.

Files Reviewed (15 files)

• adapters/antigravity-cli.md - 0 issues (new file, well-formed)
• bin/install.js - 0 issues (new case added correctly)
• bin/runtime-metadata.js - 0 issues (runtime config added correctly)
• skills/workflow-common/SKILL.md - 1 issue (stale division counts)
• tests/installer-smoke.test.js - 0 issues (test updated correctly)
• tests/adapter-conformance.test.js - 0 issues (updated to 12 adapters correctly)
• Various doc files - 0 issues (version bumps and updates)

Fix these issues in Kilo Cloud

---

_{Reviewed by laguna-m.1-20260312:free · 2,262,947 tokens}

[kilo-code-bot]

Correction to previous review: Upon re-checking the diff, the Division Constants section (lines 519-534 in SKILL.md) was NOT modified in this PR. That stale data is pre-existing technical debt, not a regression. This PR is actually clean for its intended changes — adding Antigravity CLI support. I withdraw my previous criticism and recommend merge.