fix: slack mention-gating thread participation#77660
Conversation
|
Codex review: needs maintainer review before merge. Summary Reproducibility: yes. Source inspection gives a high-confidence path: current main can post through Next step before merge Security Review detailsBest possible solution: Land this PR or an equivalent Slack-owned fix after maintainer review and targeted Slack checks so every successful visible threaded send path seeds participation state consistently. Do we have a high-confidence way to reproduce the issue? Yes. Source inspection gives a high-confidence path: current main can post through Is this the best way to solve the issue? Yes. Centralizing the cache write after the shared Slack send returns a resolved channel is narrower and more maintainable than duplicating participation recording in each caller. What I checked:
Likely related people:
Remaining risk / open question:
Codex review notes: model gpt-5.5, reasoning high; reviewed against b546aa91e19b. |
|
Landed via admin rebase onto
Thanks @bek91! |
Summary
Root Cause
Slack inbound mention gating already supports implicit thread mentions through the bot thread participation cache, but not every visible outbound Slack path seeded that cache. In particular, sends routed through the shared message/outbound delivery path could visibly reply in a thread without recording participation, so later unmentioned thread replies could be dropped as no-mention despite documented bot participation behavior.
Fixes #77648.
Validation
AI-assisted: yes.