message-worker: replicate thread subscriptions via outbox/inbox federation by general-lex · Pull Request #141 · hmchangw/chat

docs: spec for message-worker thread subscription outbox events

claude

committed

docs: implementation plan chunk 1 (tasks 1-3 — model+mention scaffolding)

claude

committed

docs: implementation plan chunk 2 (tasks 4-5 — publish helper + owner-site)

claude

committed

docs: implementation plan chunk 3 (tasks 6-7 — wire publish in reply paths)

claude

committed

docs: implementation plan chunk 4 (tasks 8-9 — mention publish + main wiring)

claude

committed

docs: implementation plan chunk 5a (task 10 — inbox-worker dispatch)

claude

committed

docs: implementation plan chunk 5b (task 11 — Mongo UpsertThreadSubscription)

claude

committed

docs: implementation plan chunk 5c (task 12 — inbox-worker integration tests)

claude

committed

docs: implementation plan chunk 5d (self-review + handoff)

claude

committed

model: add OutboxThreadSubscriptionUpserted event type constant

claude

committed

model+mention: add SiteID to Participant, propagate from Resolve

claude

committed

message-worker: plumb siteID and PublishFunc into Handler

claude

committed

message-worker: add publishThreadSubOutboxIfRemote helper

claude

committed

message-worker: ThreadSubscription.SiteID = owner site; lookup parent siteID

claude

committed

message-worker: emit outbox event on first-reply ThreadSubscription inserts

claude

committed

message-worker: wrap first-reply outbox publish errors with role context

claude

committed

message-worker: emit outbox event on subsequent-reply ThreadSubscription upserts

claude

committed

message-worker: emit outbox event on mention-marked ThreadSubscriptions

claude

committed

inbox-worker: dispatch thread_subscription_upserted to UpsertThreadSubscription

claude

committed

inbox-worker: Mongo UpsertThreadSubscription with monotonic hasMention merge

claude

committed

inbox-worker: integration tests for UpsertThreadSubscription monotonic merge

claude

committed

message-worker: add same-site subsequent-reply test case for symmetry

claude

committed

test+docs: subsequent-reply parent-not-found case + $max-on-bool comment

claude

committed

test: post-rebase fixups for upstream Publisher removal and userAccount arg

claude

committed

ThreadSubscription.SiteID stays as room site; route by owner site separately

claude

committed

docs: align spec/plan with post-review SiteID semantic

claude

committed

message-worker: fix outbox dedup-ID collision + don't drop parent sub on missing owner-site

claude

committed

docs: address CodeRabbit doc nits — code-fence langs, \$max example, plan banner

claude

committed

style: wrap publish-closure errors + assert on json.Marshal in integration tests

claude

committed

inbox-worker: collection name → thread_subscriptions; inline outbox dedup ID

claude

committed

docs+log: spec collection name; clarify lookupOwnerSiteID warn message

claude

committed

test: fixup upstream NewHandler call site after rebase

claude

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

message-worker: replicate thread subscriptions via outbox/inbox federation#141

message-worker: replicate thread subscriptions via outbox/inbox federation#141
mliu33 merged 32 commits into
mainfrom
claude/message-worker-outbox-events-D0eAA

Commits on May 4, 2026

docs: spec for message-worker thread subscription outbox events

docs: implementation plan chunk 1 (tasks 1-3 — model+mention scaffolding)

docs: implementation plan chunk 2 (tasks 4-5 — publish helper + owner-site)

docs: implementation plan chunk 3 (tasks 6-7 — wire publish in reply paths)

docs: implementation plan chunk 4 (tasks 8-9 — mention publish + main wiring)

docs: implementation plan chunk 5a (task 10 — inbox-worker dispatch)

docs: implementation plan chunk 5b (task 11 — Mongo UpsertThreadSubscription)

docs: implementation plan chunk 5c (task 12 — inbox-worker integration tests)

docs: implementation plan chunk 5d (self-review + handoff)

model: add OutboxThreadSubscriptionUpserted event type constant

model+mention: add SiteID to Participant, propagate from Resolve

message-worker: plumb siteID and PublishFunc into Handler

message-worker: add publishThreadSubOutboxIfRemote helper

message-worker: ThreadSubscription.SiteID = owner site; lookup parent siteID

message-worker: emit outbox event on first-reply ThreadSubscription inserts

message-worker: wrap first-reply outbox publish errors with role context

message-worker: emit outbox event on subsequent-reply ThreadSubscription upserts

message-worker: emit outbox event on mention-marked ThreadSubscriptions

inbox-worker: dispatch thread_subscription_upserted to UpsertThreadSubscription

inbox-worker: Mongo UpsertThreadSubscription with monotonic hasMention merge

inbox-worker: integration tests for UpsertThreadSubscription monotonic merge

message-worker: add same-site subsequent-reply test case for symmetry

test+docs: subsequent-reply parent-not-found case + $max-on-bool comment

test: post-rebase fixups for upstream Publisher removal and userAccount arg

ThreadSubscription.SiteID stays as room site; route by owner site separately

docs: align spec/plan with post-review SiteID semantic

message-worker: fix outbox dedup-ID collision + don't drop parent sub on missing owner-site

docs: address CodeRabbit doc nits — code-fence langs, \$max example, plan banner

style: wrap publish-closure errors + assert on json.Marshal in integration tests

inbox-worker: collection name → thread_subscriptions; inline outbox dedup ID

docs+log: spec collection name; clarify lookupOwnerSiteID warn message

test: fixup upstream NewHandler call site after rebase