/**
 * Remark plugin that walks markdown text leaves and replaces inline entity
 * mentions `@<marker>:<id>` (e.g. `@device:64f0a1`, `@kb:5`) with synthetic
 * `link` mdast nodes whose `url` is `mention://<marker>:<id>` (a non-standard
 * scheme). The downstream `<a>` component override in `chat-message-enhanced`
 * detects that scheme and renders an inline `<Tag>`-style chip, resolving the
 * display name from the message's `contextItems`.
 *
 * Sibling of `remark-card-links` (which handles the ASSISTANT-side
 * `[card://type:id]` markers). This one handles the USER-side `@marker:id`
 * tokens the composer commits when picking context via the `@`-mention flow.
 *
 * Why a remark plugin (NOT a regex on the raw markdown source): it splits only
 * TEXT leaves, so bold / italic / list / code wrappers around a mention stay
 * intact, and the marker disappears before any rehype-raw HTML pass.
 *
 * Grammar:
 *   - marker: `[a-zA-Z]+` — the backend `ContextItemType.marker()` short form
 *     (`device`, `script`, `ticket`, `organization`, `user`, `kb`, `policy`,
 *     `query`, `scheduledScript`, …). Mostly lowercase, but NOT guaranteed to be:
 *     the marker is matched verbatim by the backend's `MentionParser`, and
 *     `SCHEDULED_SCRIPT` ships as camelCase `scheduledScript` — a lowercase-only
 *     grammar silently dropped that whole token (no chip, raw text in the bubble).
 *   - id: charset `[A-Za-z0-9_.+/=-]` (UUIDs with hyphens, fleet numeric ids,
 *     base64 global ids, etc.; matches the composer's `MENTION_TOKEN`) — but the
 *     id may NOT END in `.` or `-`, so a trailing SENTENCE period/dash isn't
 *     swallowed into the id (`@script:38.` → id `38`, with the `.` left as text).
 *     Base64 padding `=` and `+`/`/` are still valid final chars.
 *   - A LEFT boundary (start-of-text or any non-word, non-`@` character) keeps
 *     `@marker:` from matching inside emails / mid-word (`user@host:1234` never
 *     starts a token because the `@` is preceded by a word char), while still
 *     firing when the agent wraps a mention in punctuation — parentheses,
 *     brackets, quotes — e.g. `(@device:64f0a1)`. The boundary character (if
 *     any) is captured as `lead` and re-emitted as text, so it is preserved.
 */
import type { Plugin } from 'unified';
import type { Root } from 'mdast';
export declare const remarkMentionChips: Plugin<[], Root>;
//# sourceMappingURL=remark-mention-chips.d.ts.map