You do not have a valid license of this product.

### What happened?

Failed to sign in. Message: You do not have a valid license of this product. Please contact your administrator to request a license. If you are not an enterprise user and believe you are receiving this message as an error, please try using the latest version and logging in again. (#3501)

### What did you expect to happen?

Logging in like usual and using the CLI.

### Client information

Client Information
(Unable to get /about, the CLI won't let me go further than the notice) v0.55.1

### Login information

Through google+project id.

### Anything else we need to know?

I guess it's this time of the year again when someone does this. I already created issue like this before few months back in 2025, first dev's said "it's suppose to be like that" than other devs came and said "we are working on it" before it got fixed.

I remind you that this way of logging in has been same for me and many others for practically two years by now, even after so called "shutting down" on Gemini CLI. Therefore, this is intended to work, otherwise it wouldn't been a thing to begin with.

Related regression / Prior incident:
See #19216 where the exact same error (#3501) occurred under identical conditions and was confirmed to be an unintended breaking change (subsequently rolled back by the team).

Start by reproducing the Google sign-in with a project ID on CLI v0.55.1, then compare the behavior and resolution documented in issue #19216. Done means the CLI accepts this established login flow instead of showing the invalid-license error and allows normal use.

Written by the indexing model from the issue text.