Demo connect-subgraph redeploy + botsConnect alert isolation follow-up

Follow-up from Richie Slack thread 2026-05-22 21:31 UTC. Investigation found #bots-connect ECONNREFUSED alerts were from demo domains-connect running stale image sha-112be1c9 and still sharing prod botsConnect webhook behavior. Attempted kube-live workflow dispatch failed because demo/domains-connect/values.demo.yaml had malformed YAML; opened TextureHQ/kube-live#298 to fix YAML and bump demo image to latest connect main sha-cfc004ed. Next: get kube-live#298 reviewed/merged, rerun deploy-service for demo/domains-connect, then verify demo no longer posts prod-looking connection queue/worker alerts to #bots-connect; coordinate with PR #11017 env-backed Slack webhook migration for longer-term isolation.