PR #457 intentionally drops chat/agent events with missing sessionKey instead of routing them into a synthetic main bucket. That avoids timeline corruption, but if the gateway ever regresses or a mixed-version deployment emits keyless events, users may see a missing reply with only log output.
Follow-up:
- Emit a one-shot user-visible notification or diagnostics/banner when keyless chat/agent events are dropped.
- Include enough context to guide the user toward updating/restarting the gateway, without logging message content.
- Keep the current safety property: do not silently route unknown events into
main.
Context: identified during review of #457.
PR #457 intentionally drops chat/agent events with missing
sessionKeyinstead of routing them into a syntheticmainbucket. That avoids timeline corruption, but if the gateway ever regresses or a mixed-version deployment emits keyless events, users may see a missing reply with only log output.Follow-up:
main.Context: identified during review of #457.