Telegram vs Slack

One agent answer, converted for two channels. What you see is exactly what goes over the wire — the text you would pass to Telegram with parse_mode: "HTML", and to Slack as markdown_text.

The examples come from the corpus: each one is a failure that actually happened. Edit the input to try your own.

Telegram gets tags — its HTML mode has no headings or tables, so a table goes out as a monospace block. Slack markdown_text reads standard Markdown, so the output stays Markdown, repaired. In both, unclosed emphasis and fences are closed before sending, and the counts under each output say what the normalizer repaired and what it rewrote for the channel.

import { renderWithReport } from "@minjun0219/mdwire";

for (const channel of ["telegram-html", "slack-markdown"]) {
  const out = renderWithReport(input, channel, { from: "markdown" }); // or "slack-mrkdwn"
  out.parts;   // what you send — one string unless the limit splits it
  out.repairs; // closedEmphasis · closedFence · … · convertedMarker — ten counts
  out.free();  // the result lives in WASM memory; free it when done
}