amal66 makes Google's connector setup less fragile

This closed proposal aimed to turn a brittle Google connection flow into one that tells organisations exactly what they need before it breaks.

The work focused on the awkward but important reality that Google requires each deployment to bring its own connection credentials. Rather than letting an administrator hit a vague failure halfway through setup, it would have surfaced practical Google Cloud instructions and the correct return address at the start.

It also proposed several safeguards for a connection that needs to keep working after initial approval:

Request ongoing access, so a connection can renew rather than silently expire.
Wait for confirmed approval instead of treating the start of the process as success.
Let users cancel the waiting screen, with less aggressive checking over time.
Clear stale connection records and keep error details out of AI prompts and logs.

The proposal passed its reported checks, but was closed without merging, so none of this is part of Mike's main project.