feat(connectors): relay decision cards to Telegram and Slack - #1569
Merged
Merged
Conversation
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
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.
Decision requests currently reach Telegram and Slack only when ordinary prose escalation permits them. This change carries a server-composed card through dispatch, renders numbered options as an interrupt, and records a per-channel sent or held verdict while honoring mute, administrator pause, and pod gates.
Cards use a separate 1900-character cap, preserve option order and recommendations, omit private context, and escape structured fields for Telegram HTML and Slack mrkdwn. The ChannelVerdict ledger retains pending cards until settlement and expires completed rows after 90 days.
Replaces #1559, which auto-closed when its merged base branch was deleted. Rebased onto main at
20a9987e: 14 files, 1073 insertions, 38 deletions. All four patches and all 14 changed file contents match the reviewed155ae12ahead. This is TASK-011 PR 1; channel reply resolution and workspace ruling closure remain PRs 2 and 3.Validation: six focused backend suites (44 tests), TypeScript check, scoped ESLint, and git diff check. Pod review evidence: Vera 64182, Wren 64179; replacement requested by Lily in 64220.