fix: 🐛 resolve Slack directives in section/mrkdwn (verbatim + non-verbatim)

Slack directives like `<@u123>`, `<#C123>`, `<!subteam^S1|@team>`,
`<!channel|here|everyone>`, and `<!date^…>` now fire the matching hooks
(`hooks.user`, `hooks.channel`, `hooks.usergroup`, `hooks.atHere` /
`atChannel` / `atEveryone`, `hooks.date`) in both `verbatim: true` and
`verbatim: false` modes — matching the behaviour of the rich_text path.

- Verbatim mode no longer early-returns. It splits the input by directive
  boundaries and renders each segment, preserving non-directive text
  literally (no markdown sugar expansion — that's the point of verbatim).
- Non-verbatim mode now masks fenced code, inline code, and directive
  atoms before the URL-rewrite / asterisk-doubling regex pass, then
  restores them before Yozora parses — so directives can't be mangled
  by the pre-pass and directive-shaped text inside code stays literal.
- Broadcast tokenizer recognises `<!here>` / `<!everyone>` / `<!channel>`
  natively, alongside the existing `@here` / `@everyone` / `@channel`.
- Yozora's `autolink` and `autolink-extension` are unmounted; bare URL
  autolinking is handled by the existing `<X>` / `<X|Y>` regex rewrite,
  and the autolink-extension was stealing directives like
  `<!subteam^S1|@team>` because of the embedded `@`.
- mrkdwn sub-element hook payloads now include `style: undefined` to
  match the rich_text path shape (`{ id, name, style }`).
- `<@U…|fallback>` and `<!subteam^S…|@team>` now split on `|` for data
  lookup + fallback display name (channel mention already did this).
- `&amp;` is decoded alongside `&gt;` / `&lt;` in text-object payloads
  so escaped ampersands don't leak into hrefs or visible text.

Adds a vitest test suite (the repo previously had none) covering the
directive × verbatim matrix, code-span suppression, escaped entities,
hook payload shape, data-map resolution, and non-directive regression.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: programad

.changeset/fix-mrkdwn-directives.md

@@ -0,0 +1,5 @@
+---
+"slack-blocks-to-jsx": patch
+---
+
+Resolve Slack directive atoms (`<@U…>`, `<#C…>`, `<!subteam^…>`, `<!channel|here|everyone>`, `<!date^…>`) in `section`/`mrkdwn` text and other mrkdwn-typed text. Directives now fire the same hooks as the rich_text path in both `verbatim: true` and `verbatim: false` modes. Code-span content stays literal (directives inside `` `…` `` or ` ```…``` ` are not resolved). `&amp;` is now decoded alongside the existing `&gt;` / `&lt;` decoding so link `href`s and visible text don't leak literal `&amp;`.

package.json

@@ -25,7 +25,8 @@
     "dev:css": "postcss ./src/style.css -o ./dist/style.css --watch",
     "dev": "tsup --watch",
     "lint": "tsc",
-    "test": "node --test \"test/**/*.test.mjs\"",
+    "test": "vitest run && node --test \"test/**/*.test.mjs\"",
+    "test:watch": "vitest",
     "release": "node scripts/release.mjs",
     "release:dry": "node scripts/release.mjs --dry-run",
     "release:beta": "node scripts/release.mjs prerelease --preid=beta",
@@ -44,19 +45,24 @@
     "react-dom": "^17 || ^18 || ^19"
   },
   "devDependencies": {
+    "@testing-library/jest-dom": "^6.9.1",
+    "@testing-library/react": "^16.3.2",
+    "@types/react": "^17 || ^18 || ^19",
+    "@types/react-dom": "^17 || ^18 || ^19",
+    "@vitejs/plugin-react": "^6.0.2",
     "@yozora/ast": "^2.3.2",
     "@yozora/character": "^2.3.2",
     "@yozora/core-tokenizer": "^2.3.2",
     "@yozora/parser": "^2.3.2",
-    "@types/react": "^17 || ^18 || ^19",
-    "@types/react-dom": "^17 || ^18 || ^19",
     "autoprefixer": "^10.4.17",
     "cssnano": "^6.0.3",
+    "happy-dom": "^20.9.0",
     "postcss": "^8.4.33",
     "postcss-cli": "^11.0.0",
     "postcss-nesting": "^12.0.2",
     "tailwindcss": "^3.4.1",
     "tsup": "^8.5.0",
-    "typescript": "^5.2.2"
+    "typescript": "^5.2.2",
+    "vitest": "^4.1.6"
   }
 }