Skip to content

feat(connectors): relay decision cards to Telegram and Slack - #1569

Merged
lilyshen0722 merged 6 commits into
mainfrom
kai/decision-card-relay
Sep 6, 2026
Merged

lilyshen0722 merged 6 commits into
mainfrom
kai/decision-card-relay

Conversation

@lilyshen0722

Copy link
Copy Markdown
Contributor

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 reviewed 155ae12a head. 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.

@lilyshen0722
lilyshen0722 merged commit 1337beb into main Sep 6, 2026
14 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