slack-markdown-parser 2.2.1__tar.gz → 2.2.2__tar.gz

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/CHANGELOG.md

@@ -6,15 +6,22 @@ The format is based on Keep a Changelog, and the project follows Semantic Versio
 
 ## [Unreleased]
 
+## [2.2.2] - 2026-03-10
+
 ### Added
 
-- Added a contributor guide, issue templates, and a pull request template.
-- Added the `py.typed` marker and packaging rules for docs and tests in source distributions.
+- Added Slack render-test tooling, generated regression fixtures, and maintainer docs for validating real Slack client rendering across Web, desktop, and mobile.
 
 ### Changed
 
-- CI now runs the test suite on Python 3.10, 3.11, 3.12, and 3.13.
-- `.gitignore` no longer ignores the entire `tests/` directory, so new tests and sample fixtures can be tracked.
+- Refreshed the README and behavior spec to distinguish Slack renderer limitations from parser-owned normalization and repair behavior.
+- Clarified locale-aware formatting behavior and added public examples for the Slack render-test workflow.
+
+### Fixed
+
+- Stabilized nested inline-code emphasis rendering across English, Japanese, Chinese, and Korean contexts, including existing-ZWSP boundaries and CJK italic/strike cases.
+- Preserved user-authored spacing in fallback text while removing parser-inserted rendering-only padding.
+- Wrapped bare URLs into Slack-friendly autolink form before sending `markdown` blocks so adjacent lines no longer collapse into malformed angle-link text.
 
 ## [2.2.1] - 2026-03-07
 

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: slack-markdown-parser
-Version: 2.2.1
+Version: 2.2.2
 Summary: Convert LLM Markdown into Slack Block Kit markdown/table messages
 Author: darkgaldragon
 License-Expression: MIT
@@ -48,9 +48,12 @@ This library leans on Slack Block Kit's `markdown` block for standard Markdown a
 | Problem | Approach |
 |---|---|
 | Conversion overhead | Send standard Markdown through Slack `markdown` blocks without rewriting it into `mrkdwn`. |
-| Formatting instability | Insert zero-width spaces (ZWSP, U+200B) around formatting tokens when needed so Slack parses inline styling more reliably without visible extra spaces. |
+| Formatting instability | Prefer zero-width spaces (ZWSP, U+200B) around formatting tokens, and fall back to locale-aware visible-space padding for CJK nested inline-code cases where Slack rendering still breaks. |
 | No table syntax in `mrkdwn` | Detect Markdown tables and convert them into Slack `table` blocks, including repair of common LLM-generated table inconsistencies. |
 
+The target is natural rendering on Slack, not full CommonMark or HTML fidelity.
+If Slack itself does not support a construct in `markdown` blocks, this library prefers safe plain-text rendering or explicit `table` blocks over aggressive rewrites into old `mrkdwn`.
+
 ## Features
 
 - Convert standard Markdown into Slack `markdown` blocks
@@ -59,10 +62,38 @@ This library leans on Slack Block Kit's `markdown` block for standard Markdown a
 - Split output into multiple Slack messages when needed to satisfy Slack's "one table per message" constraint
 - Sanitize ANSI/control characters and neutralize invalid Slack angle-bracket tokens before block generation
 - Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks
+- Use locale-aware visible-space padding for nested inline-code emphasis in dense Japanese, Chinese, and Korean text when Slack requires stronger boundaries than ZWSP alone
 - Support Markdown and Slack-style links inside table cells
-- Build fallback text for `chat.postMessage.text` from generated blocks
+- Build fallback text for `chat.postMessage.text` from generated blocks, normalizing synthetic ZWSP and any parser-inserted visible-space padding used only for rendering stability
 - Accept raw LLM Markdown without tightly constraining the model prompt, using best-effort sanitize and table repair before Slack delivery
 
+## Observed Slack behavior
+
+The library is built around how Slack actually renders `markdown` and `table` blocks in practice.
+
+Reliable in current Slack rendering:
+
+- `**bold**`, `*italic*`, `~~strike~~`, inline code, and fenced code blocks
+- Bare URLs, autolinks, Markdown links, reference-style links, and mailto links
+- Bullet lists, ordered lists, task lists, and simple blockquotes
+- Explicit Slack `table` blocks generated from Markdown tables
+
+Known Slack-side limitations:
+
+- Heading syntax (`#`, setext headings) renders as plain text rather than true heading levels
+- Nested blockquotes are weak compared with full Markdown renderers
+- Horizontal rules render more like line text than semantic separators
+- Markdown image syntax does not become an embedded image in `markdown` blocks
+- Math, raw HTML, HTML comments, `<details>`, admonition syntax, and Mermaid are rendered as plain text or code, not as rich features
+
+What this library compensates for:
+
+- Normalizes underscore emphasis (`_..._`, `__...__`) into Slack-friendly asterisk emphasis
+- Wraps bare URLs into Slack-friendly autolink form before sending `markdown` blocks
+- Repairs malformed LLM-generated tables before converting them into Slack `table` blocks
+- Keeps table-like rows inside fenced code blocks out of table normalization
+- Neutralizes invalid Slack angle-bracket tokens such as raw HTML-like tags
+
 ## Requirements
 
 - Your Slack integration must support Block Kit payloads with `markdown` and `table` blocks.
@@ -175,6 +206,9 @@ These are also part of the public package surface:
 
 - Behavior spec: [docs/spec.md](docs/spec.md)
 - Japanese behavior spec: [docs/spec-ja.md](docs/spec-ja.md)
+- Slack render-test workflow: [docs/slack-render-test-workflow.md](docs/slack-render-test-workflow.md)
+- Nested-modifier findings: [docs/slack-nested-modifier-findings.md](docs/slack-nested-modifier-findings.md)
+- Desktop/mobile manual checklist: [docs/slack-client-manual-checklist.md](docs/slack-client-manual-checklist.md)
 - Non-goals:
   - Generating Slack `mrkdwn` strings
   - Supporting clients or MCP tools that can only send `mrkdwn`

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/README-ja.md

@@ -17,9 +17,12 @@ Slack Block Kit の `markdown` ブロック（標準 Markdown 構文をそのま
 | 課題 | 解決手段 |
 |---|---|
 | 変換コスト | `markdown` ブロックが標準 Markdown をそのまま受け付けるため、LLM 出力を変換せず利用可能 |
-| 装飾崩れ | 装飾記号の前後に ZWSP（ゼロ幅スペース U+200B）を自動挿入してレンダリングを安定化。通常の半角スペースではなくゼロ幅スペースを使うことで、見た目上の不自然な空白を生じさせずに Slack の装飾解析を補助する |
+| 装飾崩れ | 基本は ZWSP（ゼロ幅スペース U+200B）で装飾境界を補強し、CJK の密着文脈でインラインコードを内包する装飾が崩れる場合のみ、言語別ルールで可視スペースも使ってレンダリングを安定化する |
 | テーブル非対応 | Markdown テーブルを検知して `table` ブロックに変換。LLM の出力する多様なテーブル記法の揺れも自動補完し `invalid_blocks` エラーを回避 |
 
+このライブラリの目標は、CommonMark や HTML を完全再現することではなく、Slack 上で自然に読める表示を作ることです。
+Slack の `markdown` ブロック自体が対応していない構文は、古い `mrkdwn` へ無理に書き換えるより、安全なプレーンテキスト表示や `table` ブロック化を優先します。
+
 ## 主な機能
 
 - 標準 Markdown テキストを `markdown` ブロックに変換
@@ -28,10 +31,38 @@ Slack Block Kit の `markdown` ブロック（標準 Markdown 構文をそのま
 - テーブルごとにメッセージを自動分割（Slack の「1メッセージ1テーブル」制約に対応）
 - ANSI escape / 制御文字を除去し、不正な Slack 角括弧トークンを自動で無害化
 - 装飾記号の前後に ZWSP を付与して表示崩れを抑制（フェンスドコードブロック内は除外、インラインコードは付与対象）
+- 日本語・中国語・韓国語の密着文脈で、インラインコードを内包する装飾には可視スペースを補って Slack 表示を安定化
 - テーブルセル内の Markdown link / Slack link を認識
-- `chat.postMessage.text` 用の fallback テキストを生成（ブロック内容をプレーンテキスト化して通知プレビュー等に利用）
+- `chat.postMessage.text` 用の fallback テキストを生成（表示安定化のために入れた ZWSP や人工的な可視スペースは通知文では自然な形に正規化）
 - モデル側で Markdown を厳密に制御しなくてもよいよう、Slack 送信前にベストエフォートでサニタイズとテーブル補完を行う
 
+## 実測ベースの Slack 挙動
+
+本ライブラリは、Slack の `markdown` / `table` ブロックが実際にどう見えるかを前提に設計しています。
+
+現在の Slack で安定して表示されるもの:
+
+- `**bold**`, `*italic*`, `~~strike~~`, インラインコード, フェンスドコード
+- bare URL, autolink, Markdown link, 参照リンク, mailto link
+- 箇条書き, 番号付きリスト, タスクリスト, 単純な引用
+- Markdown テーブルを変換した明示的な Slack `table` ブロック
+
+Slack 側の制約として残るもの:
+
+- `#` 見出しや setext 見出しは、真の見出しレベルではなくプレーンテキスト寄りに表示される
+- 多段引用はフル Markdown レンダラほどきれいに出ない
+- 水平線は semantic な区切りではなく線テキスト寄りに見える
+- Markdown 画像記法は `markdown` ブロック内では埋め込み画像にならない
+- 数式, 生 HTML, HTML comment, `<details>`, admonition 記法, Mermaid はリッチ機能としては扱われず、テキストまたはコードとして表示される
+
+本ライブラリが吸収するもの:
+
+- underscore 装飾 (`_..._`, `__...__`) を Slack 互換の asterisk 装飾へ正規化
+- bare URL を Slack の `markdown` ブロックで安定する autolink 形式へ正規化
+- LLM が崩したテーブル記法を補完して Slack `table` ブロックへ変換
+- フェンスドコード内の table 風行をテーブル正規化対象から除外
+- 生 HTML 風タグなど、不正な Slack angle token を無害化
+
 ## 利用前提
 
 - Slack Block Kit の `blocks` で `markdown` / `table` ブロックを送信できる実装が必要です。
@@ -131,6 +162,10 @@ QA | ~~保留~~ | Team C
 ## 仕様
 
 - 挙動仕様: [docs/spec-ja.md](docs/spec-ja.md)
+- 英語仕様: [docs/spec.md](docs/spec.md)
+- Slack 実レンダリング検証手順: [docs/slack-render-test-workflow.md](docs/slack-render-test-workflow.md)
+- nested modifier 実測メモ: [docs/slack-nested-modifier-findings.md](docs/slack-nested-modifier-findings.md)
+- Desktop / mobile 手動確認: [docs/slack-client-manual-checklist.md](docs/slack-client-manual-checklist.md)
 - 非対応:
   - `mrkdwn` 文字列の生成
   - `mrkdwn` のみ送信可能なクライアント／MCP ツール

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/README.md

@@ -17,9 +17,12 @@ This library leans on Slack Block Kit's `markdown` block for standard Markdown a
 | Problem | Approach |
 |---|---|
 | Conversion overhead | Send standard Markdown through Slack `markdown` blocks without rewriting it into `mrkdwn`. |
-| Formatting instability | Insert zero-width spaces (ZWSP, U+200B) around formatting tokens when needed so Slack parses inline styling more reliably without visible extra spaces. |
+| Formatting instability | Prefer zero-width spaces (ZWSP, U+200B) around formatting tokens, and fall back to locale-aware visible-space padding for CJK nested inline-code cases where Slack rendering still breaks. |
 | No table syntax in `mrkdwn` | Detect Markdown tables and convert them into Slack `table` blocks, including repair of common LLM-generated table inconsistencies. |
 
+The target is natural rendering on Slack, not full CommonMark or HTML fidelity.
+If Slack itself does not support a construct in `markdown` blocks, this library prefers safe plain-text rendering or explicit `table` blocks over aggressive rewrites into old `mrkdwn`.
+
 ## Features
 
 - Convert standard Markdown into Slack `markdown` blocks
@@ -28,10 +31,38 @@ This library leans on Slack Block Kit's `markdown` block for standard Markdown a
 - Split output into multiple Slack messages when needed to satisfy Slack's "one table per message" constraint
 - Sanitize ANSI/control characters and neutralize invalid Slack angle-bracket tokens before block generation
 - Add ZWSP around inline formatting tokens to reduce rendering issues outside fenced code blocks
+- Use locale-aware visible-space padding for nested inline-code emphasis in dense Japanese, Chinese, and Korean text when Slack requires stronger boundaries than ZWSP alone
 - Support Markdown and Slack-style links inside table cells
-- Build fallback text for `chat.postMessage.text` from generated blocks
+- Build fallback text for `chat.postMessage.text` from generated blocks, normalizing synthetic ZWSP and any parser-inserted visible-space padding used only for rendering stability
 - Accept raw LLM Markdown without tightly constraining the model prompt, using best-effort sanitize and table repair before Slack delivery
 
+## Observed Slack behavior
+
+The library is built around how Slack actually renders `markdown` and `table` blocks in practice.
+
+Reliable in current Slack rendering:
+
+- `**bold**`, `*italic*`, `~~strike~~`, inline code, and fenced code blocks
+- Bare URLs, autolinks, Markdown links, reference-style links, and mailto links
+- Bullet lists, ordered lists, task lists, and simple blockquotes
+- Explicit Slack `table` blocks generated from Markdown tables
+
+Known Slack-side limitations:
+
+- Heading syntax (`#`, setext headings) renders as plain text rather than true heading levels
+- Nested blockquotes are weak compared with full Markdown renderers
+- Horizontal rules render more like line text than semantic separators
+- Markdown image syntax does not become an embedded image in `markdown` blocks
+- Math, raw HTML, HTML comments, `<details>`, admonition syntax, and Mermaid are rendered as plain text or code, not as rich features
+
+What this library compensates for:
+
+- Normalizes underscore emphasis (`_..._`, `__...__`) into Slack-friendly asterisk emphasis
+- Wraps bare URLs into Slack-friendly autolink form before sending `markdown` blocks
+- Repairs malformed LLM-generated tables before converting them into Slack `table` blocks
+- Keeps table-like rows inside fenced code blocks out of table normalization
+- Neutralizes invalid Slack angle-bracket tokens such as raw HTML-like tags
+
 ## Requirements
 
 - Your Slack integration must support Block Kit payloads with `markdown` and `table` blocks.
@@ -144,6 +175,9 @@ These are also part of the public package surface:
 
 - Behavior spec: [docs/spec.md](docs/spec.md)
 - Japanese behavior spec: [docs/spec-ja.md](docs/spec-ja.md)
+- Slack render-test workflow: [docs/slack-render-test-workflow.md](docs/slack-render-test-workflow.md)
+- Nested-modifier findings: [docs/slack-nested-modifier-findings.md](docs/slack-nested-modifier-findings.md)
+- Desktop/mobile manual checklist: [docs/slack-client-manual-checklist.md](docs/slack-client-manual-checklist.md)
 - Non-goals:
   - Generating Slack `mrkdwn` strings
   - Supporting clients or MCP tools that can only send `mrkdwn`

slack_markdown_parser-2.2.2/docs/slack-client-manual-checklist.md

@@ -0,0 +1,53 @@
+# Slack Client Manual Checklist
+
+Use this for quick smoke checks in Slack Desktop and mobile after parser changes.
+
+## How to run
+
+1. Open the link for each case in Slack Desktop or mobile.
+2. Confirm the expected visible text and formatting.
+3. Mark `PASS` only if all checks below hold.
+
+## Pass criteria
+
+- Outer emphasis is rendered for the whole target span.
+- Inline code remains monospace.
+- Raw markers such as `**`, `*`, or `~~` are not visible.
+- English cases do not show extra visible spaces before punctuation.
+- Japanese/Chinese/Korean nested-code cases may show visible spaces around the emphasized span when needed; that is expected.
+
+## Cases
+
+- `manual_en`
+  Expected: `Frontend (App.tsx)` is bold, `App.tsx` is code, no extra space before `:`
+  Link: paste your `manual_en` permalink here
+
+- `manual_ja`
+  Expected: `フロントエンド (App.tsx)` is bold, `App.tsx` is code, visible spaces around the bold span are acceptable
+  Link: paste your `manual_ja` permalink here
+
+- `manual_zh`
+  Expected: `外侧(内侧)` span is bold, inner code remains code, visible spaces around the bold span are acceptable
+  Link: paste your `manual_zh` permalink here
+
+- `manual_ko`
+  Expected: `바깥(내부)강조` span is bold, inner code remains code, trailing visible space before `입니다.` is acceptable
+  Link: paste your `manual_ko` permalink here
+
+- `manual_mix_ja_en`
+  Expected: `Frontend (App.tsx)` is bold inside Japanese text, `App.tsx` is code
+  Link: paste your `manual_mix_ja_en` permalink here
+
+- `manual_mix_ko_en`
+  Expected: `Frontend (App.tsx)` is bold inside Korean text, `App.tsx` is code
+  Link: paste your `manual_mix_ko_en` permalink here
+
+- `manual_mix_en_ja`
+  Expected: `機能A (ID-1)` is bold inside English text, `ID-1` is code, no extra visible spaces are introduced
+  Link: paste your `manual_mix_en_ja` permalink here
+
+## Recording
+
+- `PASS`: rendering matches the expectation above
+- `FAIL`: capture which marker leaked or which style was missing
+- If Desktop and mobile differ, record the client and version separately

slack_markdown_parser-2.2.2/docs/slack-nested-modifier-findings.md

@@ -0,0 +1,59 @@
+# Slack Nested Modifier Findings
+
+Observed on Slack Web against `#bot-test` on 2026-03-09.
+
+## Variants
+
+- `plain`: inner content without surrounding punctuation
+- `parens`: inner content wrapped in parentheses
+- `quotes`: inner content wrapped in quotes
+
+## Source fixtures
+
+- `tests/fixtures/slack_nested_modifier_matrix.md`
+- `tests/fixtures/slack_nested_modifier_matrix_parens.md`
+- `tests/fixtures/slack_nested_modifier_matrix_quotes.md`
+- `tests/fixtures/slack_cjk_inner_code_matrix.md`
+
+## Note on private artifacts
+
+The concrete Slack permalinks used during validation are intentionally omitted from the public repository. Re-run the workflow in `docs/slack-render-test-workflow.md` inside your own workspace if you want message-level links for manual verification.
+
+## Shared result before locale-aware fallback
+
+Before the locale-aware visible-space fallback was introduced, all three content variants produced the same high-level outcome:
+
+- English boundaries succeeded in `raw` and `parser`
+- Japanese `spaces_both` succeeded in `raw` and `parser`
+- Japanese `outer_zwsp` succeeded in `raw` and `parser`
+- Japanese `tight`, `space_left`, and `space_right` failed in `raw`
+- `parser` improved those Japanese boundary buckets from `0/5` to `4/5`
+- The remaining failures were concentrated in `inner_code`
+
+## Focused CJK result
+
+Fixture:
+
+- `tests/fixtures/slack_cjk_inner_code_matrix.md`
+
+This focused matrix contained `ja`, `zh`, and `ko`, testing only:
+
+- inner `plain`
+- inner `code`
+
+Boundary behavior after improvement:
+
+- `ja`, `zh`, and `ko` all still succeeded for `outer_zwsp`
+- `ja`, `zh`, and `ko` all still succeeded for `spaces_both`
+- raw `tight` and raw `space_left` remained fragile across all three locales
+- raw `space_right` remained fragile for `ja` and `zh`, but was already stable for `ko`
+- after the locale-aware fallback, `parser` reached `2/2` success in every tested bucket for `ja`, `zh`, and `ko`
+
+Current takeaway:
+
+- Treating Chinese like Japanese is reasonable based on current Slack Web behavior.
+- Korean still differs at the raw-rendering level, but the parser can now normalize all tested Korean buckets successfully with a lighter right-side spacing rule.
+- The current parser strategy for nested inline code is:
+  - `ja` / `zh`: add visible spaces on whichever outer side is missing
+  - `ko`: ensure a visible trailing space when needed
+  - English-like boundaries: preserve the original outer formatting span

slack_markdown_parser-2.2.2/docs/slack-render-test-workflow.md

@@ -0,0 +1,117 @@
+# Slack Render Test Workflow
+
+This repository includes a minimal local workflow for validating how Slack
+actually renders generated Block Kit `markdown` and `table` output.
+
+## Files
+
+- `docs/slack-render-test-app-manifest.yaml`
+  - Minimal Slack App manifest for a test-only bot
+- `.env.example`
+  - Example local environment variables
+- `scripts/post_slack_render_test.py`
+  - Local CLI for posting test messages to Slack
+
+## Local environment
+
+Expected local-only environment variables:
+
+```bash
+SLACK_BOT_TOKEN=xoxb-...
+SLACK_TEST_CHANNEL_ID=CXXXXXXXX
+```
+
+`SLACK_BOT_TOKEN` is loaded from `.env` by default when using the script.
+
+## Test channel
+
+- Workspace: your Slack workspace
+- Channel: your dedicated render-test channel
+- Channel ID: e.g. `CXXXXXXXX`
+
+The bot must already be installed and invited to the channel.
+
+## Commands
+
+Post a raw Slack `markdown` block without parser processing:
+
+```bash
+python scripts/post_slack_render_test.py \
+  --mode raw \
+  --text 'from **bold**.'
+```
+
+Post using `slack_markdown_parser`:
+
+```bash
+python scripts/post_slack_render_test.py \
+  --mode parser \
+  --text 'from **bold**.'
+```
+
+Preview generated payloads without calling Slack:
+
+```bash
+python scripts/post_slack_render_test.py \
+  --mode parser \
+  --text 'from **bold**.' \
+  --dry-run
+```
+
+Post a markdown file:
+
+```bash
+python scripts/post_slack_render_test.py \
+  --mode parser \
+  --input-file tests/fixtures/llm_markdown_p0_corpus.md
+```
+
+Generate nested modifier matrix fixtures:
+
+```bash
+python scripts/generate_nested_modifier_matrix.py --content-variant plain
+python scripts/generate_nested_modifier_matrix.py --content-variant parens
+python scripts/generate_nested_modifier_matrix.py --content-variant quotes
+```
+
+Generate focused CJK nested-code fixtures:
+
+```bash
+python scripts/generate_nested_modifier_matrix.py \
+  --content-variant plain \
+  --locales ja,zh,ko \
+  --inners plain,code \
+  --output tests/fixtures/slack_cjk_inner_code_matrix.md
+```
+
+## Output
+
+Each posted message prints JSON like:
+
+```json
+{
+  "message_index": 1,
+  "channel": "CXXXXXXXX",
+  "ts": "1773051865.764719",
+  "mode": "parser",
+  "permalink": "https://your-workspace.slack.com/archives/CXXXXXXXX/p1234567890123456"
+}
+```
+
+Use the `permalink` to open the exact message in Slack and verify rendering in the
+web UI or via Playwright.
+
+## Recommended comparison flow
+
+1. Post the same markdown once with `--mode raw`.
+2. Post the same markdown once with `--mode parser`.
+3. Open both permalinks in Slack.
+4. Compare visible rendering, especially for:
+   - bold/italic/strike recognition
+   - punctuation boundaries
+   - Japanese vs English surrounding text
+   - fallback text behavior when relevant
+
+For desktop/mobile spot checks, use:
+
+- `docs/slack-client-manual-checklist.md`

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/docs/spec-ja.md

@@ -12,6 +12,13 @@
 - Slack Block Kit ブロック（`markdown` / `table`）
 - 複数テーブル入力時は「1メッセージ1テーブル」を満たすメッセージ群
 
+## 設計上の到達点
+
+このパーサーは、CommonMark 全体や HTML / リッチドキュメントの完全再現を目標にはしません。
+目的は、Slack Block Kit の `markdown` / `table` ブロックで送ったときに自然に読めるメッセージを作ることです。
+
+Markdown としての厳密さより Slack 上での読みやすさが優先される場合は、Slack 側で安定して読める表現を優先します。
+
 ## 変換パイプライン
 
 `convert_markdown_to_slack_blocks` の処理順序:
@@ -28,6 +35,35 @@
 `convert_markdown_to_slack_messages` は上記の結果を「1メッセージ1テーブル」制約に沿って分割します。
 `convert_markdown_to_slack_payloads` は、同じ分割結果に `chat.postMessage.text` 用 fallback を付けた payload 群を返します。
 
+## 実測ベースの Slack レンダラ挙動
+
+以下は、生成された Block Kit payload を実際の Slack クライアントで確認したときの挙動です。
+
+### Slack が比較的きれいに表示できるもの
+
+- asterisk 装飾: `*italic*`, `**bold**`
+- 取消線: `~~strike~~`
+- インラインコードとフェンスドコード
+- bare URL, autolink, Markdown link, 参照リンク, mailto link
+- 箇条書き, 番号付きリスト, タスクリスト, 単純な1段引用
+- Slack `table` ブロック
+
+### Slack 自体の制約として残るもの
+
+- `#`, `##`, `###` や setext 見出しは、本当の見出しレベルではなくプレーンテキスト寄りに表示される
+- 多段引用はフル Markdown レンダラほどきれいに出ない
+- 水平線は semantic な区切りではなく、線テキスト寄りの見え方になる
+- Markdown 画像記法は `markdown` ブロック内では埋め込み画像にならない
+- 数式, 生 HTML, HTML comment, `<details>`, admonition 記法, Mermaid は特別なリッチ表示にならない
+
+### このパーサーが補正するもの
+
+- `_..._` / `__...__` を Slack 互換の `*...*` / `**...**` に正規化する
+- bare URL は Slack の `markdown` ブロックで安定する autolink 形式（`<https://...>`）へ正規化する
+- 崩れた Markdown テーブルを補完して `table` ブロックへ変換する
+- フェンスドコード内の table 風行をテーブル解析対象から除外する
+- `<foo>` や生 HTML 風タグのような不正な Slack angle token を無害化する
+
 ## Slack 向けサニタイズルール
 
 `sanitize_slack_text` の挙動:
@@ -105,7 +141,7 @@ LLM は外枠パイプの省略、セパレータ行の欠落、列数の不一
 
 ### 目的
 
-日本語等の語間スペースがない文で装飾記号が隣接文字と結合し、Slack のレンダリングが崩れる問題を回避します。通常の半角スペースではなくゼロ幅スペースを使うことで、見た目上の不自然な空白を生じさせずに Slack の装飾解析を補助します。
+日本語等の語間スペースがない文で装飾記号が隣接文字と結合し、Slack のレンダリングが崩れる問題を回避します。基本はゼロ幅スペースで境界を補強し、CJK の密着文脈でインラインコードを内包する装飾だけは、Slack 実表示を優先して可視スペースへフォールバックします。
 
 ### 対象パターン
 
@@ -120,6 +156,10 @@ LLM は外枠パイプの省略、セパレータ行の欠落、列数の不一
 
 - **フェンスドコードブロック**（`` ``` ... ``` `` および `~~~ ... ~~~`）内は一切変更しない
 - インラインコード（`` `...` ``）は除外**しない**（付与対象）
+- `**bold**`、`*italic*`、`~~strike~~` の内側にネストしたインラインコードには個別の ZWSP を付与しない
+- 英語系の境界では外側の装飾トークンはそのまま維持する
+- 日本語・中国語の密着境界では、外側の装飾トークンの前後で不足している側に可視スペースを補う
+- 韓国語の密着境界では、必要に応じて後ろ側の可視スペースを補い、右側に空白があるケースはそのまま維持する
 
 ## ZWSP 除去ルール
 
@@ -144,6 +184,7 @@ LLM は外枠パイプの省略、セパレータ行の欠落、列数の不一
 `build_fallback_text_from_blocks` は `chat.postMessage.text` に設定する通知プレビュー用テキストを生成:
 
 - `markdown` ブロック → ZWSP を除去したテキスト
+- nested inline code の表示安定化のために一時的に入れた可視スペースは、fallback では自然な文に戻す
 - `table` ブロック → 各行のセルテキストを ` | ` で連結
 - 各ブロックの出力を空行で区切って結合
 
@@ -158,3 +199,4 @@ LLM は外枠パイプの省略、セパレータ行の欠落、列数の不一
 - `mrkdwn` 文字列の生成
 - 完全な Markdown AST の再現
 - HTML レンダリング互換
+- Slack `markdown` ブロックが本来対応していない構文に、独自のリッチ表示を与えること

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/docs/spec.md

@@ -12,6 +12,13 @@ This document defines the conversion behavior of `slack-markdown-parser`.
 - Slack Block Kit blocks (`markdown` / `table`)
 - When the input contains multiple tables, a list of messages that satisfies the "one table per message" rule
 
+## Design target
+
+This parser does not try to reproduce full CommonMark, HTML, or rich-document rendering.
+Its goal is to produce Slack messages that read naturally when delivered through Slack Block Kit `markdown` and `table` blocks.
+
+When Markdown fidelity and Slack readability conflict, readable Slack output takes priority.
+
 ## Conversion pipeline
 
 Processing order in `convert_markdown_to_slack_blocks`:
@@ -28,6 +35,35 @@ Processing order in `convert_markdown_to_slack_blocks`:
 `convert_markdown_to_slack_messages` then splits the resulting block list to satisfy the "one table per message" constraint.
 `convert_markdown_to_slack_payloads` returns the same split blocks plus fallback `text` values ready for `chat.postMessage`.
 
+## Observed Slack renderer behavior
+
+The following behaviors are based on practical validation against real Slack clients using the generated Block Kit payloads.
+
+### Behaviors that Slack currently renders well
+
+- Asterisk emphasis: `*italic*`, `**bold**`
+- Strikethrough: `~~strike~~`
+- Inline code and fenced code blocks
+- Bare URLs, autolinks, Markdown links, reference-style links, and mailto links
+- Bullet lists, ordered lists, task lists, and simple one-level blockquotes
+- Slack `table` blocks
+
+### Behaviors limited by Slack itself
+
+- ATX headings (`#`, `##`, `###`) and setext headings render as plain text rather than true heading levels
+- Nested blockquotes are weaker than in full Markdown renderers
+- Horizontal rules render more like visible line text than semantic separators
+- Markdown image syntax does not become an embedded image inside `markdown` blocks
+- Math, raw HTML, HTML comments, `<details>`, admonition syntax, and Mermaid do not receive special rich rendering
+
+### Behaviors this parser compensates for
+
+- `_..._` and `__...__` are normalized into Slack-friendly `*...*` and `**...**`
+- Bare URLs are wrapped into Slack-friendly autolink form (`<https://...>`) before `markdown` block delivery
+- Malformed Markdown tables are repaired before `table` block generation
+- Table-like rows inside fenced code blocks are kept out of table parsing
+- Unsupported Slack angle-bracket tokens such as `<foo>` or raw HTML-like tags are neutralized
+
 ## Slack text sanitize rules
 
 Behavior of `sanitize_slack_text`:
@@ -104,7 +140,7 @@ Behavior of `add_zero_width_spaces_to_markdown`:
 
 ### Purpose
 
-In languages such as Japanese that do not use spaces between words, formatting markers can attach directly to surrounding characters and break Slack rendering. This library inserts zero-width spaces instead of visible spaces so Slack gets clearer formatting boundaries without changing the visible layout.
+In languages such as Japanese that do not use spaces between words, formatting markers can attach directly to surrounding characters and break Slack rendering. This library primarily inserts zero-width spaces so Slack gets clearer formatting boundaries without changing the visible layout. For some nested inline-code emphasis cases in dense CJK text, it falls back to visible spaces because current Slack rendering is more reliable with explicit spacing.
 
 ### Target patterns
 
@@ -119,6 +155,10 @@ For each formatting token below, if either adjacent side is not a space, tab, ne
 
 - Fenced code blocks (both `` ``` ... ``` `` and `~~~ ... ~~~`) are never modified
 - Inline code (`` `...` ``) is not excluded; it is part of the target set above
+- Inline code nested inside `**bold**`, `*italic*`, or `~~strike~~` is left untouched.
+- For English-like boundaries around those nested combinations, the outer formatting span is preserved as-is.
+- For dense Japanese/Chinese boundaries, visible spaces are inserted on the missing outer side(s) around the outer formatting span.
+- For dense Korean boundaries, a visible trailing space is inserted when needed, while right-space cases are otherwise preserved because Slack already renders them more reliably.
 
 ## ZWSP removal rules
 
@@ -143,6 +183,7 @@ For each formatting token below, if either adjacent side is not a space, tab, ne
 `build_fallback_text_from_blocks` generates preview text for `chat.postMessage.text` as follows:
 
 - `markdown` blocks: text with ZWSP removed
+- Parser-inserted visible spaces used only to stabilize nested inline-code emphasis are normalized back out when building plain fallback text
 - `table` blocks: join each row's cell text with ` | `
 - Join block outputs with blank lines between them
 
@@ -157,3 +198,4 @@ For the same input, the library always returns the same output regardless of env
 - Generating Slack `mrkdwn` strings
 - Reconstructing a full Markdown AST
 - Matching HTML rendering behavior
+- Recreating rich rendering for constructs Slack does not natively support in `markdown` blocks

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "slack-markdown-parser"
-version = "2.2.1"
+version = "2.2.2"
 description = "Convert LLM Markdown into Slack Block Kit markdown/table messages"
 readme = "README.md"
 requires-python = ">=3.10"

{slack_markdown_parser-2.2.1 → slack_markdown_parser-2.2.2}/slack_markdown_parser/__init__.py

@@ -1,6 +1,6 @@
 """slack-markdown-parser public package API."""
 
-__version__ = "2.2.1"
+__version__ = "2.2.2"
 __license__ = "MIT"
 
 from .converter import (