Ethan a1e912a763 fix(chatd): deliver retry control events via pubsub (#23349) ...

> **PR Stack**
> 1. #23351 ← `#23282`
> 2. #23282 ← `#23275`
> 3. #23275 ← `#23349`
> 4. **#23349** ← `main` *(you are here)*

---

Retry events were published only to the local in-process stream via
`publishEvent()`. When pubsub is active, `Subscribe()`'s merge loop only
forwarded durable events (messages, status, errors) from pubsub
notifications,
so retry events were silently dropped for cross-replica subscribers.

This adds a `publishRetry()` helper that publishes both locally and via
pubsub,
and extends the `Subscribe()` notification handler to forward retry
events.

**Changes:**
- `coderd/pubsub/chatstreamnotify.go`: add `Retry` field to notify
message
- `coderd/chatd/chatd.go`: add `publishRetry()`, update `OnRetry`
callback,
  extend `Subscribe()` to forward `notify.Retry`
- `coderd/chatd/chatd_internal_test.go`: focused pubsub delivery test
- `enterprise/coderd/chatd/chatd_test.go`: cross-replica end-to-end test

2026-03-20 15:19:41 +00:00

..

chatevent.go

fix: resolve bugs in pubsub and codersdk chat packages (#22717)

2026-03-06 17:37:55 +00:00

chatstreamnotify.go

fix(chatd): deliver retry control events via pubsub (#23349)

2026-03-20 15:19:41 +00:00

inboxnotification.go

feat(coderd): add inbox notifications endpoints (#16889)

2025-03-18 00:02:47 +01:00