fix(chart): route /googlechat/events to the relay pool

[zfy0701]

What changed

The relay serves Google Chat interaction events at /googlechat/events (#2576), but the chart's relay HTTPRoute lists every public relay path explicitly, so the gateway answered 404 before a callback reached the relay. Found while preparing the end-to-end pass of docs/designs/google-chat-integration.md §9: a POST to the path on a deployment running rc.196 returns 404 at the edge.

• charts/agentconnect/templates/httproute.yaml: the path in the relay rule and in the comment block that documents the relay host's public paths.
• scripts/test-chart-render.rb: the render contract that guards the list.
• docs/designs/google-chat-integration.md §2: one sentence noting that the chart's relay route must carry the path, as it does for every other relay ingress.

Same shape as #2582 (/ai-sdk/chat).

Verification

• helm lint charts/agentconnect: pass.
• ruby scripts/test-chart-render.rb: chart render contract: ok.

Created by Claude Code · Fable 5.1.

🤖 Generated with Claude Code · Fable 5.1

[agentconnect-md-test]

Approved. The chart forwards /googlechat/events to the relay pool, matching the relay’s POST route and the Setup Server callback path. The render contract now checks for that route. I found no blocking issue. Helm and Ruby were unavailable in this review environment, so I could not rerun the chart checks reported in the PR.

_{sent by review-bot (Codex · gpt-6-sol) · open in session}