Description

Google Chat agents stop responding to messages after upgrading from v2026.2.26 to v2026.3.2. Rolling back to v2026.2.26 immediately restores message delivery.

This is similar to #32275 (BlueBubbles webhook broken in 2026.3.1).

Steps to Reproduce

1. Running v2026.2.26 with Google Chat plugin (webhook-based, multi-account: andy and april)
2. Upgrade to v2026.3.2
3. Send a message to any Google Chat agent

Expected Behavior

Agent receives the message and responds.

Actual Behavior

Agent does not respond. No errors in gateway logs — the googlechat plugin loads normally, webhooks register, startup looks clean.

• Gateway health endpoint (GET /) returns 200
• Google Chat webhook endpoint (GET /googlechat) returns 405 (route exists)
• POST /googlechat with fake payload returns 400 "invalid payload" (plugin is processing)
• But real Google Chat messages get no response

Additional Context

• Working version: v2026.2.26
• Broken version: v2026.3.2
• Channel: Google Chat (webhook-based via Cloudflare Tunnel)
• Config: Multi-account googlechat with audienceType: "app-url", each account has its own service account file
• Previously reported v2026.3.2 issues: openclaw doctor --fix auto-migrates googlechat config into accounts.default breaking it; webhook handler returns 404 after config hot-reloads
• Platform: macOS (Apple Silicon), Node.js via homebrew

Workaround

Stay on v2026.2.26.