[Daanish2003]

Summary

Three follow-ups from spec #1044 (Messaging Channels 1, Telegram):

• Messaging Channel links on a Host with no email or push #1066: a Host with only a messaging adapter now gets the same <appUrl>/bots/<botId> links. New Host option createBotSdk({ appUrl }), resolved once in appUrlOf (packages/botsdk/bot/src/bot/channels.ts): the Host's appUrl, else the email or push adapter's, with trailing slashes stripped.
• Resume a messaging delivery after a part fails #1067: a delivery that fails partway resumes after the last part sent, so the user gets each part once and a later button edit still finds the buttons message. The seam gains MessagingSendError (with SendProgress) and OutboundMessage.resume. The core keeps the progress as a sentOn key in message.parts jsonb, with no new column. Telegram and the fake adapter both skip parts already sent.
• Keep the "Linked to your account" notice when the token is rejected #1068: the Linked notice is kept. A token rejected while sending it marks the account needs_attention and stops its listener, through a shared rejected() in channel-listeners.ts.

How it was tested

• Each ticket was built test-first, and every new test was seen red. Each ticket ran its own code-review: Messaging Channel links on a Host with no email or push #1066 found 5 and fixed 2, Resume a messaging delivery after a part fails #1067 found 8 and fixed 5, and Keep the "Linked to your account" notice when the token is rejected #1068 found 0 to fix. Root pnpm check-types passed after each ticket's last commit.
• On the merged tip b743ac8: oxlint, oxfmt, root check-types, and the full vitest suite in 3 shards (283 files) all pass.
• Skipped: CI. At the owner's request, this PR is merged without waiting for it. No Playwright run (no UI change).

Decisions I made

• The Host option is createBotSdk({ appUrl }). The owner chose it after the first cut used channelAppUrl, because Hosts never build channel() themselves. It affects messaging links only; email and push still use their adapter's own appUrl.
• Resume a messaging delivery after a part fails #1067 resume state lives in message.parts jsonb (sentOn: platform, chat, body digest and progress), not in a new column. A retry resumes only when platform, chat and body digest all match; otherwise it resends the whole Message. The fake adapter now splits a Message into parts, so a Message with text and files reports one id per part.
• Keep the "Linked to your account" notice when the token is rejected #1068 uses option (a): stop the listener on a rejected token, without rethrowing.

Risk

• Resume a messaging delivery after a part fails #1067 changes the adapter seam that every messaging adapter implements: new optional resume and a new error type. Only Telegram exists today.
• sentOn isn't cleared after a full success. A rerun after a full success already resent everything before this change.

Closes #1066
Closes #1067
Closes #1068

🤖 Generated with Claude Code