add multi-reaction support for operator cancellation - #182
Merged
Conversation
dembrane-sam-bot
enabled auto-merge
July 27, 2026 09:27
spashii
approved these changes
Jul 27, 2026
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this change?
Adds support for multiple cancel reactions in the Slack event handler. In addition to
:no_entry:, the daemon now listens for::x:(❌):no_entry_sign:(🚫):octagonal_sign:(🛑):heavy_multiplication_x:(✖️)The specific reaction used to trigger the cancel is captured, logged, and syntactically recorded in the tool-call audit log (
args.reaction). The terminal lifecycle reaction posted by the bot remains:no_entry:to maintain the semantic distinction between a cancelled state and an errored state (:x:).Also updates
src/capabilities/slack.mdto document the newly supported reactions and adds a dedicated suite of unit tests intests/runtime/test_multi_reaction_cancel.py.What did Sam notice that led to this?
The principal operator requested supporting
:x:and other related cancel reactions in addition to:no_entry:during a Slack conversation (thread1785142142.371049).Tier?
Tier 3 (daemon-level event handler logic in
src/runtime/daemon.py).Confidence?
Highly confident. All 512 tests passed successfully, and the newly added unit tests specifically exercise the multi-reaction cancellation flow across positive, negative, and self-reaction boundaries.