DigitalTolk / ex / 37478647286

100%

push

github

Webhooks: reply in threads via root_id, return the message id (#287)

Incoming webhooks could only post top-level messages and answered a plain
"ok", so an integration had no way to keep follow-ups for one event
together. Alert bots (event-radar) flood channels as a result.

- Payload accepts an optional root_id (JSON and form). The root must be a
  live, top-level, non-system post by the same webhook author in the
  target parent, so a webhook URL can never write into a human thread.
  Invalid roots answer 400 invalid_root; a deleted thread answers 409.
- Replies go through the same thread bookkeeping as human replies (reply
  metadata, participation, notifications, root republish), extracted into
  MessageService.applyThreadReply and shared with sendRun. Replies do not
  bump channel/conversation unread, matching the human path.
- A caller sending Accept: application/json gets {"id": "<msgId>"};
  everyone else still gets "ok".

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

8937 of 8937 branches covered (100.0%)

Branch coverage included in aggregate %.

81 of 81 new or added lines in 3 files covered. (100.0%)

41063 of 41069 relevant lines covered (99.99%)

2219.36 hits per line