Hi maintainers,

I encountered the same plugin not found issue being discussed in the community since updating to 2026.2.23. I dug into my Windows machine and found the root cause for why the official fix (openclaw plugins enable google-antigravity-auth) crashes:

1. The Auth Plugin Source is Missing in the Release Bundle:
When running:
openclaw plugins enable google-antigravity-auth
It errors with: Config validation failed: plugins.entries.google-antigravity-auth: plugin not found: google-antigravity-auth

Checking the installed path node_modules\openclaw\extensions\google-antigravity-auth, it is basically an empty husk. It only contains an empty node_modules folder. All the actual javascript source code and package.json for the plugin are completely missing from the npm Windows bundle.

2. The Fallback JSON.parse Crash in pi-ai:
Because the plugin logic is missing, the gateway relies on the old hardcoded provider fallback (google-antigravity). However, in buildOAuthApiKey, the code is missing the condition for google-antigravity:
return provider === "google-gemini-cli" ? JSON.stringify({ token: credentials.access, projectId: credentials.projectId }) : credentials.access;

It passes a raw string token to the google-gemini-cli.js consumer, which strictly expects a JSON object. Calling JSON.parse on the raw token string causes a hard crash, throwing the misleading "Invalid Credentials" error instead of a parsing error.

Repro Info:

• openclaw --version: 2026.2.23
• Installed via: standard npm install -g openclaw
• OS: Windows 11

Could you please check the build pipeline for the NPM Windows release?