* feat(setup): implement antigravity integration setup and hook adapter for gitnexus
* docs(readme): list Antigravity in supported editors
* test(setup-antigravity): pin platform per-test to fix Windows CI failure
The MCP entry assertion expected `npx` directly, but on Windows
`getMcpEntry()` wraps it as `cmd /c npx ...`, which broke the Windows
runner. Pin platform to darwin in beforeEach so the existing assertion
is deterministic, restore the descriptor in afterEach, and add a
parity test for the win32 cmd-wrapper shape.
* fix(antigravity): align hook adapter to Gemini CLI schema + fix Windows CI
Rebase the Antigravity integration on the canonical Gemini CLI hooks
contract (https://geminicli.com/docs/hooks/reference/), which is the
documented schema Antigravity 2.0 inherits:
- Hook adapter: replace PreToolUse/PostToolUse with the single AfterTool
event. BeforeTool has no documented context-injection channel in the
Gemini contract, so augmentation runs in AfterTool where
hookSpecificOutput.additionalContext is the documented way to append
text to the tool result the agent reads. Stale-index hints land in the
same channel (so the agent sees them) and are mirrored to stderr for
terminal users. Tool-name matcher updated to Gemini CLI snake_case
(search_file_content|glob|run_shell_command).
- Setup: write hooks to ~/.gemini/settings.json under canonical
hooks.AfterTool[] (replaces the ad-hoc hooks.json top-level group).
Polite-neighbor merge preserves existing user hooks. Also copy
win-rm-list-json.ps1 alongside hook-db-lock-probe.cjs so the Windows
MCP server ownership probe doesn't silently fail open.
- Tests: 17 regression tests covering MCP write, win32 shape, hook
schema, polite-neighbor merge, idempotency, adapter context emission,
stale-index hint, and skill layout.
- README: footnote documenting the AfterTool design choice and a link
to the Gemini CLI hooks reference.
Windows CI fix: installSkillsTo previously used glob('*.md') +
glob('*/SKILL.md'), which returned zero matches under the Windows
runner's temp paths (8.3 short-name like RUNNER~1). Replace with
fs.readdir + dirent type checks — same behavior, no path quirks. This
fixes the only failing Windows job on the PR.
* fix(antigravity): address PR review — windowsHide, stale docs, dead code
Addresses the production-readiness review findings on PR #1730:
- F1 (blocker): add windowsHide:true to all four spawnSync sites in the
Antigravity hook adapter (findCanonicalRepoRoot, runGitNexusCli's two
branches, buildStaleIndexHint) so they don't flash console windows on
Windows. Matches the fix#1794 already on main for the Claude hook.
- F2 (blocker): update gitnexus/README.md editor table to say AfterTool
and link the Gemini CLI hooks reference. The published README had
drifted to the pre-c1872b4 PreToolUse + PostToolUse schema.
- F3: rewrite the stale ~/.gemini block comment in setup.ts. It still
described the old hooks.json + gitnexus group + grep_search design.
- F4: remove grep_search dead code from extractPattern and its doc
comment. The registered matcher is search_file_content|glob|run_shell_command,
so grep_search would never be invoked.
- F5: annotate timeout:10000 with a ms-unit comment noting Gemini CLI
uses milliseconds (Claude Code uses seconds).
- F6: add the GITNEXUS_DEBUG branch to extractAugmentContext for parity
with the Claude adapter, so suppressed augment stderr is recoverable.
- F7: stageAdapter test helper now copies win-rm-list-json.ps1 alongside
the .cjs helpers, so the adapter's Windows lock-probe path isn't a
silent fail-open in child-process smoke tests.
* test(antigravity): add integration tests and register in cross-platform matrix
Adds end-to-end coverage on top of the unit-level tests, per maintainer
request:
- test/integration/setup-antigravity.test.ts (10 tests): exercises the
real setupCommand() against a temp HOME with ~/.gemini/antigravity/
present. Verifies mcp_config.json shape, ~/.gemini/settings.json
AfterTool entry, adapter + helpers + win-rm-list-json.ps1 copy,
baked-in cliPath rewrite (issue #108 regression class), skill layout,
polite-neighbor merge against existing user hooks, idempotency,
skip-when-absent, corrupt-file safety, and key preservation.
- test/integration/antigravity-hook-e2e.test.ts (19 tests): runs the
full install-then-execute flow — invokes setupCommand to lay down
the adapter + helpers, then spawns the INSTALLED adapter as a real
child process against a temp git repo + .gitnexus/. The source
adapter cannot be spawned directly (it requires sibling .cjs helpers
that only live in hooks/claude/); install-then-spawn mirrors the
production codepath. Covers staleness detection across all five git
mutation types, --embeddings propagation, polite skip on
toolResponse.error / exit_code !== 0, augment crash-free behavior,
cwd validation, corrupted/missing meta.json, unknown event names,
empty stdin, and the no-.gitnexus deep-nested case.
- scripts/cross-platform-tests.ts: registers all three antigravity
test files (unit in PLATFORM_LOGIC, two integration files in
SPAWN_CLI) so Windows and macOS CI exercise them on every run.
* fix(antigravity): review fixes — dedup, silent-failure guard, type coercion, glob filter
- Delete mergeGeminiSettingsHooks (verbatim copy of mergeHooksJsonc),
replace call site with the original
- Unify geminiHasGitnexusHook into hasGitnexusHook with commandFragment
parameter; delete the duplicate
- Guard against silent adapter-copy failure: verify the adapter file
exists before registering the AfterTool hook entry in settings.json;
surface helper copy errors instead of swallowing
- Fix toolSucceeded type coercion: use Number() so string exit_code
values from Gemini CLI are handled correctly
- Align glob tool extractPattern with Claude adapter's restrictive
regex filter (/[*\/]([a-zA-Z][a-zA-Z0-9_-]{2,})/)
- Remove bounds-only toBeGreaterThan(0) assertion (DoD §2.7)
- Add antigravity adapter to HOOK_FILES windowsHide regression list
* chore(autofix): apply prettier + eslint fixes via /autofix command
* chore: trigger CI
---------
Co-authored-by: Gergő Magyar <gergomagyar@icloud.com>
Co-authored-by: Test <test@example.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
