Alem Tuzlak d6b01d379a feat(bot): typed Renderable, durable <Message onReaction>, and richer JSX props ...

Type the bot UI surface and broaden the cross-platform component vocabulary,
adding only capabilities that more than one adapter can express.

- bot-ui: type the `Thread` interface's `ui` params (`post`/`update`/
  `awaitChoice`/`postEphemeral`) as `Renderable` instead of `unknown`, so JSX
  is checked at the call site and the `{ raw }` escape hatch is explicit.
- `<Message onReaction>`: per-message reaction callback `(emoji, { added, user,
  rawEmoji, messageId })`. Stripped from the IR before it reaches the adapter,
  routed from reaction ingress by message id. Durable on the same terms as a
  component `onClick` — a `{ component, props }` snapshot is persisted and the
  component is re-rendered to re-derive the handler after a restart; inline
  handlers route in-process only.
- `Button.url` link buttons — Slack, Discord, Teams, Telegram.
- `Field.label` — typed (Discord and Telegram already consumed it untyped);
  newly rendered on Slack.
- `Select.multi` multi-select — Slack (`multi_static_select` in an input block
  + `selected_options` decode), Discord (min/max values + `component` bounds
  decode), Teams (`isMultiSelect`); Telegram/WhatsApp degrade to single-select.

Slack-only capabilities (Button.confirm, Image.title, Input label/initialValue/
required, Select.initialValue) were intentionally left out.

2026-06-26 13:11:20 +02:00

..

render

feat(bot): typed Renderable, durable <Message onReaction>, and richer JSX props

2026-06-26 13:11:20 +02:00

adapter.test.ts

…

adapter.ts

…

conversation-store.test.ts

…

conversation-store.ts

…

download-files.test.ts

…

download-files.ts

…

event-renderer.test.ts

…

event-renderer.ts

…

graph-files.test.ts

…

graph-files.ts

…

index.ts

…

interaction.test.ts

…

interaction.ts

…

listener.test.ts

…

listener.ts

…

message-stream.test.ts

…

message-stream.ts

…

sanitizing-http-agent.ts

…

types.ts

…