[Bug]: Antigravity shows misleading "Needs attention" warning when binary is healthy but Google auth is unchecked

Start with apps/desktop and the AntigravityProvider.ts logic shown in the report, then reproduce the provider health-check flow in Settings → Providers → Antigravity. Trace how ACP initialize(), auth.status, errorMessage, and the existing chat-triggered OAuth flow determine the displayed state. Done means a healthy but unchecked binary is not presented as an alert and the provider settings card exposes the reported sign-in action.

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Configure Antigravity with a working binary (either managed or custom binaryPath).
2. Navigate to Settings -> Providers -> Antigravity.
3. Observe provider status after the health check completes.

Expected behavior

When the binary passes ACP initialize(), the status should show a neutral/informational state (e.g. "Installed · Sign-in required" or a blue/gray badge) with an explicit "Sign in with Google" button directly in the provider settings card.

Actual behavior

The UI displays an amber warning badge:
Needs attention · Antigravity is installed. Google account access is not checked yet.

Because this is styled as an alert/warning with "Needs attention", users assume the installation or health check failed and spend time unnecessarily troubleshooting working setups. Furthermore, there is no action button in Settings to trigger sign-in; the user must know to open a chat and send a message with the model selected to initiate OAuth.

Impact

Minor bug or occasional failure

Version or commit

0.0.42 (and main)

Environment

Windows 11 x64, T3 Code Desktop 0.0.42

Logs or stack traces

// In AntigravityProvider.ts:
const authenticated = draft.auth.status === "authenticated";
const message = errorMessage ?? (authenticated ? void 0 : draft.auth.status === "unauthenticated" ? SIGN_IN_MESSAGE : AUTH_UNCHECKED_MESSAGE);
// Binary probe only calls initialize and does not check auth, leaving draft.auth.status unchecked and displaying AUTH_UNCHECKED_MESSAGE as a warning alert.

Workaround

Ignore the warning, open a new chat thread, select Antigravity, and send a message to trigger the Google OAuth browser login.

Suggested Fix

1. Differentiate unauthenticated/unchecked state from actual errors: use a neutral status indicator rather than an amber "Needs attention" alert when errorMessage is undefined.
2. Add a "Sign in with Google" action button directly in the Antigravity provider settings card so users can complete authentication without having to guess the chat workflow.