## What I've Verified

### ClawdBot Side (All OK ✓)

| Check | Status | Details |
|-------|--------|---------|
| Gateway running | ✓ | PID active, listening on expected port |
| Google Chat channel started | ✓ | Logs show `[googlechat] [default] starting Google Chat webhook` |
| Webhook endpoint reachable | ✓ | External curl returns "invalid payload" (expected for test) |
| Tailscale Funnel active | ✓ | `tailscale serve status` shows funnel ON, routing `/googlechat` to local port |
| **Agent 2** (different project) works | ✓ | Logs show Agent 2 receiving and responding to messages in its spaces |
| Config binding correct | ✓ | `clawdbot.json` has correct space ID bound to Agent 1 |
| Service account file intact | ✓ | File exists, contains valid credentials, not recently modified |

### Google Cloud Console Side (All Appears OK)

| Check | Status | Details |
|-------|--------|---------|
| Chat API enabled | ✓ | API is enabled in project |
| App URL configured | ✓ | Shows correct Tailscale funnel URL (see screenshot) |
| Interactive features | ✓ | "Receive 1:1 messages", "Join spaces", "Receive messages" all enabled |
| Authentication audience | ✓ | Set to "App URL" |
| App status | ✓ | App appears to be live/published |

### Actions Taken (None Worked)

1. ❌ Re-added **Agent 1** app to the space (via @mention) — no effect
2. ❌ Clicked "Save" on Cloud Console config to re-register webhook — no effect
3. ❌ Removed and re-added app, verifying it's from correct project — no effect
4. ❌ Restarted ClawdBot gateway multiple times — no effect

## Key Observations

1. **Zero inbound webhooks** — Gateway logs show NO incoming Google Chat messages for **Agent 1's** space since the issue started, while **Agent 2's** spaces show normal activity

2. **Different projects, same ClawdBot** — Both apps route through the same Tailscale funnel URL, same ClawdBot instance. **Agent 2** works, **Agent 1** doesn't.

3. **No errors on receive** — Since no webhooks arrive, there are no receive-side errors. The 403 errors were from ClawdBot trying to SEND (typing indicators/responses) before realizing the app wasn't in the space.

## Configuration (Sanitized)

```json
// clawdbot.json - Google Chat channel config
{
  "channels": {
    "googlechat": {
      "enabled": true,
      "groupPolicy": "allowlist",
      "audienceType": "app-url",
      "audience": "https://[TAILSCALE_HOSTNAME]/googlechat",
      "accounts": {
        "default": {
          "name": "Agent 1",
          "serviceAccountFile": "[PATH]/agent1-service-account.json",
          "groups": {
            "spaces/[SPACE_ID_A]": {
              "allow": true,
              "requireMention": false
            }
          }
        },
        "agent2": {
          "name": "Agent 2",
          "serviceAccountFile": "[PATH]/agent2-service-account.json",
          "groups": {
            "spaces/[SPACE_ID_B]": {
              "allow": true,
              "requireMention": false
            }
          }
        }
      }
    }
  }
}
```

## Google Cloud Console Screenshot

The HTTP endpoint URL is correctly configured:
- Using "common HTTP endpoint URL for all triggers"
- URL matches ClawdBot's expected endpoint
- HTTPS with authenticated certificate (Tailscale)

## Questions for ClawdBot Support

1. **Is there any ClawdBot-side state that could cause it to silently ignore incoming webhooks for a specific space?**

2. **Could there be a mismatch between Google's expected JWT audience and what ClawdBot validates?** (Given `audienceType: "app-url"`)

3. **Is there a way to see raw incoming webhook requests in ClawdBot logs** to confirm whether Google is actually calling the endpoint?

4. **Any known issues with Google Chat webhook delivery after an app is removed and re-added to a space?**

5. **Should I try creating a fresh Chat app in Google Cloud Console** to rule out a corrupted app state?

## Suspected Root Cause

Google's webhook delivery system has stopped sending events for this specific Chat app/space combination. The ClawdBot side appears healthy (proven by **Agent 2** working), and the Cloud Console configuration appears correct.

This might be:
- A Pub/Sub delivery issue on Google's side
- A stale app registration that didn't fully re-register after re-adding
- An issue with the specific Google Cloud project's Chat API state

## Help Requested

Any insights on:
1. How to force Google to re-register the webhook for this Chat app
2. How to debug whether the issue is on Google's side vs ClawdBot's side
3. Whether there are any ClawdBot diagnostic commands that could help