fix(comark): harden auto-close for code spans, math, escapes, and link text

[antfubot]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Hardens autoCloseMarkdown() against several inline edge cases that mangled partial streaming output. The inline closer scans the last line counting markers (*, _, ~, `, $, …); it previously miscounted markers that are actually literal text, which corrupted marker parity and emitted stray closers.

1. Inline code spans and math are now literal regions

Emphasis markers inside an inline code span (`…`) or inline math ($…$) are literal text, not delimiters. They were being counted, throwing off bold/italic parity:

text `a*b` and **bold   →   text `a*b` and **bold*    ❌  (was)  — stray `*`
text `a*b` and **bold   →   text `a*b` and **bold**   ✅  (now)

$a * b$ and *italic     →   $a * b$ and *italic       ❌  (was)  — left open
$a * b$ and *italic     →   $a * b$ and *italic*      ✅  (now)

When a line ends inside an unclosed code/math region, only that region is closed and emphasis closers are suppressed, so nothing leaks into the span:

`x * y     →   `x * y*    ❌  (was)
`x * y     →   `x * y`    ✅  (now)

2. Escaped markers are no longer counted

A backslash escapes the following marker, so \* / \_ / \` are literal:

a \* b *it   →   a \* b *it    ❌  (was)  — left open
a \* b *it   →   a \* b *it*   ✅  (now)

3. Inline code inside unclosed link text (earlier commit)

A streaming [`foo skipped all inline markers inside link text, dropping the unclosed backtick and emitting only the bracket closer — landing ] inside the code span:

[`foo   →   [`foo]    ❌  (was)
[`foo   →   [`foo`]   ✅  (now)

Genuinely nested emphasis of mixed marker types (e.g. **_text) needs CommonMark flanking resolution and remains a documented limitation, tracked by it.todo cases (the downstream markdown-it parser does the real resolution). Complete links, attribute scopes, and block math ($$) are unaffected.

📝 Checklist

• I have linked an issue or discussion.
• I have run pnpm verify and it passes. (comark: 1055/1055 + 2 todo, lint + format clean; 2 pre-existing comark-vue typecheck errors are unrelated)
• I have updated the documentation accordingly. (no docs change — internal streaming behavior)

---

This PR was created with the help of an agent.

[vercel]

@antfubot is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

[antfu]

Reviewed

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
comark-sveltekit	Ready	Preview	Jun 10, 2026 8:16am

[pkg-pr-new]

Open in StackBlitz

comark

npm i https://pkg.pr.new/comark@233

@comark/ansi

npm i https://pkg.pr.new/@comark/ansi@233

@comark/html

npm i https://pkg.pr.new/@comark/html@233

@comark/nuxt

npm i https://pkg.pr.new/@comark/nuxt@233

@comark/react

npm i https://pkg.pr.new/@comark/react@233

@comark/svelte

npm i https://pkg.pr.new/@comark/svelte@233

@comark/vue

npm i https://pkg.pr.new/@comark/vue@233

commit: f56a714

[farnabaz]

👍