Best possible solution:

Land the Telegram fix only after maintainer review and redacted live Telegram proof, then track any shared-channel command-output consistency cleanup separately.

Do we have a high-confidence way to reproduce the issue?

Yes, source-level: current main routes Telegram command-output progress through the raw renderer while docs/config say commandText status should hide command text in progress previews. I did not run a live Telegram reproduction in this read-only review.

Is this the best way to solve the issue?

Yes for the Telegram bug: using buildChannelProgressDraftLineForEntry matches the existing tool/item event path and keeps the fix inside the channel renderer boundary. The only unresolved shape question is whether sibling channels should be fixed in a separate shared cleanup.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 53541b2141c6.

Label changes:

• add P2: This is a normal-priority Telegram progress-rendering bugfix with limited blast radius and no evidence of emergency data loss or runtime outage.
• add merge-risk: 🚨 message-delivery: The PR changes visible Telegram draft-message rendering for command progress, and native Telegram behavior is not proven by the supplied synthetic tests.
• add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body lists local test commands and git diff check, but it does not include after-fix real Telegram proof such as a redacted recording, live output, or logs showing the changed draft preview behavior. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• add mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram progress draft output and is well suited to a short Telegram Desktop proof recording.

Label justifications:

• P2: This is a normal-priority Telegram progress-rendering bugfix with limited blast radius and no evidence of emergency data loss or runtime outage.
• merge-risk: 🚨 message-delivery: The PR changes visible Telegram draft-message rendering for command progress, and native Telegram behavior is not proven by the supplied synthetic tests.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body lists local test commands and git diff check, but it does not include after-fix real Telegram proof such as a redacted recording, live output, or logs showing the changed draft preview behavior. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• mantis: telegram-visible-proof: Mantis should capture Telegram visible proof. The PR changes visible Telegram progress draft output and is well suited to a short Telegram Desktop proof recording.

PR surface:

Source +35, Tests +135. Total +170 across 4 files.

What I checked:

• Repository policy applied: Root and scoped policies require full review beyond the diff, scoped extension/channel boundary checks, and sibling-surface awareness for shared channel changes. (AGENTS.md:28, 53541b2141c6)
• Current Telegram gap: On current main, Telegram tool starts and item events use buildChannelProgressDraftLineForEntry, but command-output events still call buildChannelProgressDraftLine directly, so channel config such as commandText is not applied there. (extensions/telegram/src/bot-message-dispatch.ts:2436, 53541b2141c6)
• Documented behavior: The public streaming docs say setting streaming.preview.commandText or streaming.progress.commandText to status keeps progress visible while hiding raw command/exec text across compact progress channels, including Telegram. Public docs: docs/concepts/streaming.md. (docs/concepts/streaming.md:213, 53541b2141c6)
• PR diff shape: The PR changes Telegram command-output dispatch to use buildChannelProgressDraftLineForEntry and updates shared command-output line construction so status and command title can render separately in text/rich previews. (src/channels/streaming.ts:427, 0f916b236793)
• Telegram proof requirement: The Telegram maintainer note says streaming-visible Telegram behavior needs real Telegram proof, preferably bot-to-bot QA or an equivalent live probe, over synthetic-only validation. (.agents/maintainer-notes/telegram.md:37, 53541b2141c6)
• Sibling-surface check: Matrix already uses the entry-aware command-output path, while Discord and Slack still call the raw command-output renderer; this PR is a narrow Telegram fix, not a full shared-channel cleanup. (extensions/matrix/src/matrix/monitor/handler.ts:1996, 53541b2141c6)

Likely related people:

• obviyus: Authored and merged the recent Telegram rich HTML rendering PR that touched the same Telegram dispatch/rich preview area now being adjusted. (role: recent Telegram rich-rendering contributor; confidence: high; commits: da92615816b6; files: extensions/telegram/src/bot-message-dispatch.ts)
• vincentkoc: Git history attributes the shared streaming helper surface, docs, and Telegram config hints for commandText/progress behavior to this commit. (role: shared channel streaming introducer; confidence: medium; commits: efbefceb0e2e; files: src/channels/streaming.ts, docs/concepts/streaming.md, docs/channels/telegram.md)
• bdjben: Authored the recent Matrix command-progress identity fix that changed shared progress-line merge keys and added Telegram-adjacent progress assertions. (role: recent command-progress contributor; confidence: high; commits: 3fc850fe8685; files: src/channels/streaming.ts, src/plugin-sdk/channel-streaming.test.ts, extensions/telegram/src/bot-message-dispatch.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.