Google Antigravity / agent task

# DevAgentRadar → Google Antigravity

Goal: turn this release signal into a safe pilot plan for my stack.

## Context
Assistant: Gemini CLI
Proposal: Upgrade Gemini CLI and retest ignore paths on symlink-linked trees
Summary: Gemini CLI nightly v0.56.0 fixes consistent symlink evaluation in ignore path handling. Upgrade, then re-run ignore-sensitive workflows on repos that use symlinks so excluded paths match the new resolution behavior.
Primary source: https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260821.g30573d2e4

## Why it matters
This release changes how ignore paths evaluate symlinks for consistency. Teams or developers whose projects mount linked directories, monorepo workspaces, or vendor trees via symlinks can see different include/exclude results after upgrading. The shellExecutionService refactor is internal cleanup and does not change product workflow, so the practical response is to pin/upgrade to v0.56.0-nightly.20260821.g30573d2e4 and validate ignore behavior on real symlink layouts rather than assuming prior path matching still holds.

## Suggested actions
1. Install or pin Gemini CLI to v0.56.0-nightly.20260821.g30573d2e4 (release: https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260821.g30573d2e4).
2. In a repo that uses symlinks (e.g. linked packages, nested workspaces, or vendor dirs), run your usual Gemini CLI ignore-sensitive flow twice: once with the symlink present and once after replacing the symlink with a real copy of the same tree; record which paths are ignored each time.
3. Paste to your coding agent: "Using Gemini CLI ignore path handling after the consistent symlink evaluation fix, list every path under $PROJECT_ROOT that is reached via a symlink and state whether current ignore rules exclude it; flag any path whose ignore status depends on following vs not following the symlink."
4. Paste to your coding agent: "Diff our ignore config (.gitignore, .geminiignore, and any CLI ignore flags we pass) against symlink targets in this repo; propose the minimal rule edits so intentional secrets/build artifacts stay ignored whether a path is accessed through a symlink or its real path."
5. If ignore results changed after upgrade, commit the updated ignore rules alongside a short note that Gemini CLI ignore path handling now evaluates symlinks consistently (PR #28915).


Please:
1. Map the change to concrete pilot steps
2. Flag security / permission implications
3. Keep the pilot reversible