fix(connectors): render note Markdown for outbound email & chat

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code

[KrisBraun]

Problem

Outbound messages arrived with line breaks added mid-sentence and showed literal **markdown**. Root cause: connectors sent the raw note Markdown as a bare text/plain body (or, for Teams, raw Markdown labelled contentType: "html"). Recipients' mail servers then hard-wrap text/plain prose at ~70 columns mid-sentence, and Markdown syntax is never rendered.

(The matching inbound half — the server doubling those soft wraps into paragraph breaks — plus the private chat connectors are fixed in the corresponding plotday/core PR.)

Change

Render the note body to the right format per platform:

• twister: add markdownToHtml (@plotday/twister/utils/markdown-html, via marked — already a repo dep). Mentions [Name](#@UUID) render as @Name; GFM + line breaks. In its own module so only email connectors bundle it (sideEffects: false). Changeset included.
• gmail: send multipart/alternative — a clean text/plain part (markdownToPlainText, no hard wrapping) plus a rendered text/html part; wrapped in multipart/mixed when attachments are present.
• outlook-mail: send Graph body: { contentType: "html", ... } at both send sites.
• ms-teams: render Markdown→HTML at the graph-api send/update chokepoint (it already declared contentType: "html" but was passing raw Markdown). Baseline is unaffected — it derives from Graph's echoed result.body.content, not from what we send.

Tests

• gmail: 50/50 (3 new tests asserting multipart/alternative with rendered HTML + clean plain text, and the multipart/mixed nesting with attachments).
• twister / gmail / outlook-mail / ms-teams typecheck clean; pnpm validate-changesets passes.

🤖 Generated with Claude Code