Skip to content

fix: bind IM message mutations to runtime bot identity#170

Merged
LIU9293 merged 1 commit intomainfrom
feat/multi-bot-message-routing-177221
Feb 28, 2026
Merged

fix: bind IM message mutations to runtime bot identity#170
LIU9293 merged 1 commit intomainfrom
feat/multi-bot-message-routing-177221

Conversation

@LIU9293
Copy link
Copy Markdown
Contributor

@LIU9293 LIU9293 commented Feb 27, 2026

Summary

  • move Slack, Discord, and Lark runtime construction to processor-scoped IM adapters so each bot runtime performs send/update/delete/history as itself
  • make message mutation paths prefer the current runtime bot identity first, with existing registry fallback only as a compatibility path
  • reduce multi-bot thread edit collisions that surface as cross-author update errors (for example Discord Cannot edit a message authored by another)

Validation

  • bun test packages/ims

Use processor-scoped adapters for Slack, Discord, and Lark so updates/deletes run as the owning bot in multi-bot threads and avoid cross-bot edit failures.
@LIU9293 LIU9293 merged commit 536511e into main Feb 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant