fix(ci): restore Telegram and plugin SDK guard checks#99355
Merged
Conversation
openclaw-barnacle
Bot
added
channel: telegram
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix(ci): restore Telegram and plugin SDK guard checks This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
This was referenced Jul 3, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 3, 2026
sheyanmin
pushed a commit
to sheyanmin/openclaw
that referenced
this pull request
Jul 8, 2026
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
1 participant
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 Problem This Solves
Resolves a problem where the main CI workflow failed in the Telegram extension boundary check, the channel history-window guardrail, and the plugin SDK surface-budget tests after recent changes landed.
Why This Change Was Made
Telegram tests now verify the plugin-owned context payload without importing core prompt internals. Telegram session history selection again reads through
createChannelHistoryWindowwhile preserving watermark-before-truncation behavior, and the plugin SDK budget is pinned to the four intended exports added by the ambient transcript work.User Impact
No user-visible behavior changes. Maintainers regain green CI coverage for extension boundaries, Telegram history-window ownership, and plugin SDK surface growth.
Evidence
node --import tsx scripts/check-no-extension-test-core-imports.tsnode scripts/run-vitest.mjs src/channels/turn/message-turn-guardrails.test.ts test/scripts/plugin-sdk-surface-report.test.ts extensions/telegram/src/bot-message-context.prompt-context.test.ts extensions/telegram/src/bot-message-dispatch.test.tsnode scripts/run-oxlint.mjs --tsconfig extensions/telegram/tsconfig.json extensions/telegram/src/bot-message-context.prompt-context.test.ts extensions/telegram/src/bot-message-context.session.ts extensions/telegram/src/bot-message-dispatch.test.tsnode scripts/run-tsgo.mjs -p extensions/telegram/tsconfig.json --noEmit