- Shipped
- September 28, 2026 at 11:30 AM UTC
- Author
- Kamo
- Commit
- 9e9357c
**************** asserted expectedStream(<own stream>) on every subject, so a subject another stream captures was refused with "expected stream does not match [10060]" and dropped. SecurityService's lead notes (media.feed.*, stream MEDIA) never reached a viewer. The assertion now applies only inside the service's own nats.jetstream.stream.subjects; any other subject is routed by subject, as publishRouted does. MediaService announces a post-session event (COMMENT_ADDED, POST_CREATED) after the caller's commit, so a viewer's reload finds the note Hot Reassign writes before it marks the lead. Ids go out as text. The note's text is no longer published to media.post.<guid>: nothing subscribes to it, and the MEDIA stream keeps what it captures with no age limit.