🤖 We're reviewing this PR with Aisle

We're running a security check on the changes in this PR now. This usually takes a few minutes. ⌛
We'll post the results here as soon as they're ready.

Progress:

• Analysis
• Triage
• Finalization

Latest run failed. Keeping previous successful results. Trace ID: 019ccb589dacf8b1fd43f80e23700122.

_{Last updated on: 2026-03-08T02:48:45Z}

Landed via temp rebase onto main.

• Gate: targeted only per request:

[email protected] test /Users/obviyus/Developer/clawdbot
node scripts/test-parallel.mjs -- src/telegram/draft-stream.test.ts src/telegram/lane-delivery.test.ts src/telegram/bot-message-dispatch.test.ts

RUN v4.0.18 /Users/obviyus/Developer/clawdbot

✓ src/telegram/draft-stream.test.ts (27 tests) 63ms
✓ src/telegram/lane-delivery.test.ts (14 tests) 8ms
✓ src/telegram/bot-message-dispatch.test.ts (59 tests) 25ms

Test Files 3 passed (3)
Tests 100 passed (100)
Start at 08:24:00
Duration 2.42s (transform 1.71s, setup 368ms, import 2.44s, tests 96ms, environment 0ms)

• Source branch head: b6ad588
• Landed commit: 722c5e5

Greptile Summary

This PR surgically narrows the DM preview transport workaround originally introduced in #33453. The previous fix forced "message" transport for all DM lanes when answer streaming was active, which inadvertently prevented native sendMessageDraft from being used on the answer lane. This PR restores "auto" (native draft) transport for the answer lane in DMs, while keeping "message" transport only for the reasoning lane — which still needs a tracked messageId for later deletion.

Key changes:

• bot-message-dispatch.ts: Renamed and rescoped useMessagePreviewTransportForDm → useMessagePreviewTransportForDmReasoning to apply only when laneName === "reasoning". This allows the answer lane to use efficient native draft streaming while the reasoning lane retains message-based transport.
• Draft materialization handling: The answer lane's "auto" transport in DMs is handled correctly via the existing canMaterializeDraftFinal → tryMaterializeDraftPreviewForFinal pathway in lane-delivery-text-deliverer.ts, which calls stream.materialize() to atomically convert the live draft into a permanent sendMessage and then clears the draft.
• Regression test: Added a targeted test proving the materialization path fires exactly once (materialize called once) and neither deliverReplies nor editMessageTelegram is triggered (confirming no duplicate final message).

The production materialize() implementation in draft-stream.ts correctly: calls stop() to flush the final draft text, sends a real sendMessage with the last rendered text (preserving parse_mode), then clears the draft as a best-effort cleanup to avoid a stale draft appearing alongside the real message.

Safety assessment: This PR is safe to merge. It replaces an over-broad workaround with a more precise, targeted fix backed by a direct regression test that validates the draft materialization behavior.

Confidence Score: 4/5

• Safe to merge — replaces an over-broad workaround with a more precise fix, backed by direct regression testing.
• The logic is sound: the answer lane's "auto" transport in DMs is handled correctly via the existing canMaterializeDraftFinal → tryMaterializeDraftPreviewForFinal path, verified end-to-end in the new test. The reasoning lane correctly retains "message" transport for messageId tracking. The one-point deduction from 5/5 is because this partially reverts a prior fix ([Bug]: Telegram Duplicate Messages with Partial Streaming #33453) and relies on the materialize() production path being robust. However, the implementation in draft-stream.ts handles stop-flush, fallback retry with thread-param handling, and draft-clear correctly, making this a well-engineered change.
• No files require special attention — all changes are correctly scoped and tested. The draft-stream.ts materialize() implementation (not directly modified in this PR) was verified to correctly handle the materialization flow.

_{Last reviewed commit: b6ad588}

Landed via temp rebase onto main.

• Gate: targeted only per request: pnpm test -- src/telegram/draft-stream.test.ts src/telegram/lane-delivery.test.ts src/telegram/bot-message-dispatch.test.ts
• Source branch head: b6ad588
• Landed commit: 722c5e5

🤖 We're reviewing this PR with Aisle

We're running a security check on the changes in this PR now. This usually takes a few minutes. ⌛
We'll post the results here as soon as they're ready.

Progress:

• Analysis
• Triage
• Finalization

Latest run failed. Keeping previous successful results. Trace ID: 019ccb5d03e376138199af53d353709d.

_{Last updated on: 2026-03-08T02:56:35Z}