Package-level declarations
Types
Dokka-generated HTML -> MDX (see blueprint.dokka.Html2Mdx), plus the Starlight frontmatter Html2Mdx deliberately doesn't add itself (it's a body-only converter — see its class KDoc). --in should point at the generated site's per-symbol subtree (e.g. tool/build/dokka/html/myst2mdx), not the whole dokka/html output — navigation.html/search-worker.json alongside it are pure site chrome. One exception: --in's own sibling index.html (one level up — the module's real "Packages" overview, not chrome) is also converted, into output/index.mdx — see run.
Dokka-generated HTML -> Typst (see blueprint.dokka.Html2Typst).
myst2mdx is one CLI with subcommands, not three separate binaries: they share this file, this jar, and (transpile / dokka2mdx) the same MdxEscaper escaping policy. transpile is the original, CI-invoked command. The two dokka2* subcommands are CLI-reachable and tested but not called from CI/Makefile: the live site instead copies Dokka's own generated HTML verbatim into site/public/api/ (see Makefile's api target) so it keeps its own theme/search/nav rather than being lossy-converted into MDX/Typst — dokka2mdx/dokka2typst stay available for whatever needs an actual MDX/Typst rendering of KDoc content (e.g. a future merged PDF).
Orchestrates one page: resolved MyST AST (JSON) -> a full MDX document with frontmatter, component imports, and a provenance banner. The MDX is a BUILD ARTIFACT — regenerated every build, never hand-edited — which is why baking resolved xrefs and numbers straight into it is safe.