[Critical] Recursive .git Scan in User Root triggers 429 Account Ban & Infinite "Zombie" Context Loop

[wdsr4215]

Priority: P1 (Critical / Blocker)
Extension Version: (Pre-release / Antigravity latest)
OS: Windows

11

Summary:
I am encountering a critical severity bug in the "Antigravity" (Gemini Code Assist) engine.
A hidden .git folder accidentally existing in the Windows User Root (C:\Users\%USERNAME%) triggers a recursive file scan by repo.go covering the entire user directory.
This massive volume of requests is immediately flagged by Google Servers as abuse, resulting in a 429 Too Many Requests (Account Soft-ban).

The "Infinite Zombie Loop" (Unrecoverable State):

1. After the 429 ban, I attempted to clean the installation (deleted %APPDATA%, .gemini, reinstalled extension).
2. However, the default setting Workbench > Cloud Changes: Auto Resume (default: onReload) AUTOMATICALLY restores the previous "toxic" chat context from the cloud upon the very first launch.
3. This immediately re-triggers the 429 error, trapping the user in an infinite loop with no UI option to abort the resume or start fresh.

Steps to Reproduce:

1. Place a hidden .git folder in C:\Users\%USERNAME%.
2. Launch VS Code with Gemini Code Assist enabled.
3. Observe repo.go scanning unrelated cache/image files in the logs.
4. Account gets banned (429) within seconds.

Expected Behavior:

1. The indexer must have a safety guard to NEVER recursively scan the User Root (~) or system directories.
2. If the API returns 4xx/5xx errors on startup, "Cloud Resume" should be auto-disabled to allow recovery.

Impact:
My account is currently banned from the API, and the IDE is unusable due to the persistent cloud state restoration.