blume 0.5.3 → 0.5.4

package/dist/types/migrate/shared.d.ts

@@ -1,153 +0,0 @@
-import type { BlumeConfig } from "../core/schema.ts";
-/**
- * Whether `candidate` resolves to a path inside `root` (or is `root` itself).
- * Guards migrators against `../` traversal in author-controlled source paths
- * (`pages` entries, `<include>` targets) that would otherwise read or move
- * files outside the docs tree.
- */
-export declare const isInsideRoot: (root: string, candidate: string) => boolean;
-/**
- * Framework-agnostic helpers shared by more than one migrator. Each piece here
- * was generalized from a migrator-specific implementation so Mintlify, Nextra,
- * and future migrators converge on a single copy.
- */
-/** Serialize a `BlumeConfig` to a `blume.config.ts` at the project root. */
-export declare const writeBlumeConfig: (root: string, config: BlumeConfig) => Promise<void>;
-/**
- * Rewrite a migrated project's npm scripts off the old framework's CLI. A
- * `dev`/`build`/`start` script whose command invokes `cli` (e.g. `/\bnext\b/`)
- * is repointed at the matching Blume command (`start` -> `blume preview`); a
- * script whose command matches `remove` (e.g. a `fumadocs-mdx` postinstall) is
- * dropped. Scripts that don't match either are left untouched, so custom tasks
- * survive. Returns true when `package.json` changed.
- */
-export declare const rewriteFrameworkScripts: (root: string, cli: RegExp, remove?: RegExp) => Promise<boolean>;
-/** Of the candidate project-relative paths, the ones that still exist — the old
- * framework files a migration leaves behind for the user to remove by hand. */
-export declare const leftoverFiles: (root: string, candidates: string[]) => string[];
-/**
- * Scaffold a minimal, runnable `package.json` when the migrated project has
- * none. Config-only sources (e.g. a Mintlify `docs.json`) ship no npm manifest,
- * so a fresh migration has nothing to run `blume dev` with; this writes a stub
- * with `blume` as a dependency and `dev`/`build`/`doctor` scripts, making
- * `npm install && npm run dev` work immediately. A pre-existing `package.json`
- * is left untouched — {@link rewriteFrameworkScripts} repoints those instead.
- * Returns true when a file was created.
- */
-export declare const ensurePackageJson: (root: string) => Promise<boolean>;
-/**
- * Remove every match of an import pattern, collapsing the blank gap each
- * removal leaves behind — without touching blank runs elsewhere in the
- * document (double blank lines inside code fences are real content that a
- * whole-document `\n{3,}` collapse used to corrupt).
- */
-export declare const stripImports: (source: string, pattern: RegExp) => string;
-export interface CalloutRewriteOptions {
-    /** Directive for a type-bearing tag with no `type` attribute (e.g. bare `<Callout>`). */
-    defaultDirective: string;
-    /** Tag names whose directive is fixed by the tag itself (e.g. `<Warning>`). */
-    tagDirectives: Record<string, string>;
-    /** Component tag names to convert. */
-    tags: string[];
-    /** `type="…"` values mapped to Blume directive names. */
-    typeDirectives: Record<string, string>;
-}
-/** Read a quoted string attribute (`name="…"` or `name='…'`) from a tag. */
-export declare const attribute: (attrs: string, name: string) => string | undefined;
-/**
- * Find the `>` that closes an opening JSX tag, honoring quotes and `{…}`
- * expression attributes (so a `>` inside `icon={"<svg…>"}` is not mistaken for
- * the tag end). Returns -1 if unterminated.
- */
-export declare const findOpenTagEnd: (source: string, from: number) => number;
-/**
- * Convert callout-style JSX components into Blume `:::` directives. Uses a
- * quote/brace-aware tag scanner so callouts carrying JSX-expression attributes
- * (e.g. inline-SVG icons) convert cleanly; non-convertible attributes (icons,
- * colors, emoji) are dropped. A tag whose resolved directive is unknown is left
- * untouched.
- */
-export declare const rewriteCallouts: (source: string, options: CalloutRewriteOptions) => string;
-/**
- * Remove frontmatter keys Blume's strict page schema would reject (e.g. stray
- * `og:*`/`twitter:*` metatags) so the migrated page validates, reporting what
- * was dropped. Validation errors other than stray keys are left for `blume dev`
- * to surface.
- */
-export declare const stripUnknownPageMeta: (data: Record<string, unknown>) => {
-    data: Record<string, unknown>;
-    removed: string[];
-};
-/**
- * Rename a JSX tag (open and close) while preserving its attributes. The
- * trailing lookahead means a longer tag (e.g. `CardGrid`) is never matched by a
- * rule for its shorter prefix (`Card`), so prefix-sharing renames can be chained
- * — run the item-level rename before the container rename.
- */
-export declare const renameTag: (source: string, from: string, to: string) => string;
-/**
- * Static readers for JS/TS config files (Nextra `_meta`, Starlight
- * `astro.config`). Config is parsed by walking the source as text — quote-,
- * comment-, and bracket-aware — rather than executing user code, matching the
- * other migrators (which never eval). Values that aren't pure literals (an
- * identifier, call, JSX, or interpolated template) are reported as `UNPARSEABLE`
- * so the caller can drop the field and warn.
- */
-/** Index of a string within a JS source: the close quote matching `s[open]`. */
-export declare const findStringEnd: (s: string, open: number) => number;
-export declare const unescapeString: (inner: string) => string;
-export interface ObjectScanResult {
-    end: number;
-    entries: string[];
-}
-/**
- * Walk a `{…}` object literal starting at `openIndex`, returning the matching
- * close-brace index and the raw `key: value` text of each top-level entry.
- * Quote-, comment-, and bracket-aware so commas/braces nested in strings,
- * arrays, or child objects don't split entries. Returns null if unterminated.
- */
-export declare const scanObject: (source: string, openIndex: number) => ObjectScanResult | null;
-export interface ArrayScanResult {
-    elements: string[];
-    end: number;
-}
-/**
- * Walk a `[…]` array literal starting at `openIndex`, returning the matching
- * close-bracket index and the raw text of each top-level element. The sibling of
- * {@link scanObject}; a trailing comma yields no empty element.
- */
-export declare const scanArray: (source: string, openIndex: number) => ArrayScanResult | null;
-/**
- * Strip `//` and block comments so they don't leak into entry text (the scanner
- * splits on slices, so an inter-entry comment would otherwise attach to the next
- * entry). String literals are preserved verbatim.
- */
-export declare const stripJsComments: (source: string) => string;
-export interface KeyValue {
-    key: string;
-    value: string;
-}
-/** Split a raw `key: value` entry at its top-level colon. */
-export declare const splitKeyValue: (entry: string) => KeyValue | null;
-/** Read an object key, unquoting it when it is a string literal. */
-export declare const parseKey: (key: string) => string;
-/** Read a clean string literal value, or null if it's an expression. */
-export declare const readString: (value: string) => string | null;
-/** A value that isn't a pure literal (identifier, call, JSX, computed, …). */
-export declare const UNPARSEABLE: unique symbol;
-export type LiteralValue = LiteralValue[] | boolean | null | number | string | typeof UNPARSEABLE | {
-    [key: string]: LiteralValue;
-};
-/**
- * Evaluate a JS literal expression (string / number / boolean / null / array /
- * object) into its value without executing it. Anything else resolves to
- * {@link UNPARSEABLE}; inside arrays the sentinel keeps the element's position,
- * inside objects it stays as the field's value so the caller can warn and drop.
- */
-export declare const parseLiteral: (source: string) => LiteralValue;
-/** Narrow a parsed literal to a string. */
-export declare const asLiteralString: (value: LiteralValue | undefined) => string | undefined;
-/** Narrow a parsed literal to a plain object (not an array or `UNPARSEABLE`). */
-export declare const isLiteralObject: (value: LiteralValue | undefined) => value is Record<string, LiteralValue>;
-/** Narrow a parsed literal to an array. */
-export declare const asLiteralArray: (value: LiteralValue | undefined) => LiteralValue[] | undefined;

package/docs/advanced/bridge.mdx

@@ -1,76 +0,0 @@
----
-title: Bridge
-description: Run blume dev directly on a Mintlify codebase — no config, no migration, no file changes. Blume detects docs.json and serves it in place.
----
-
-Bridge mode lets you point Blume at a **Mintlify** project and run it as-is. There's no config to write and no migration to commit: drop `blume dev` into a directory that has a `docs.json` (or legacy `mint.json`) and Blume detects it, synthesizes an equivalent config in memory, and serves your existing MDX — transformed to Blume idiom on the fly, on disk untouched.
-
-```bash
-cd my-mintlify-docs
-npx blume dev
-```
-
-```txt
-ℹ Detected docs.json — running in Mintlify bridge mode (no migration).
-  Run "blume migrate mintlify" to convert permanently.
-```
-
-It's the zero-commitment way to see what your docs look like on Blume — you can keep running `mintlify dev` in one terminal and `blume dev` in another, side by side, and decide later.
-
-## When it activates
-
-Bridge mode is entirely automatic, gated on two conditions:
-
-- **No Blume config.** There's no `blume.config.{ts,js,mjs}` at the project root. An explicit Blume config always wins — the moment one exists, Blume runs a normal project and bridge mode never triggers.
-- **A Mintlify config is present.** A `docs.json` or `mint.json` sits at the root.
-
-With both true, Blume treats the Mintlify config as its source of truth for that run.
-
-:::note
-Bridge mode applies to `blume build` too, not just `blume dev` — you can produce a static site from an unconverted Mintlify project. Only `blume dev` prints the detection notice.
-:::
-
-## What happens under the hood
-
-Bridge mode is the **read-only twin** of [`blume migrate mintlify`](/docs/advanced/migrate#mintlify): the same translation, without writing anything back.
-
-- **Config is synthesized in memory.** `docs.json` is translated to a Blume config — navigation, theme, and chrome mapped across — exactly as the migrator would, but nothing is written to disk.
-- **Content is served through a Mintlify source.** The config's content block is rewired to a single [`mintlify` content source](/docs/content/sources) rooted at the project. Each MDX page is transformed to Blume markup **at scan time** as it's read, so your files never change.
-- **Variables are inlined at scan time.** `docs.json` `variables` (`{{name}}`) are substituted into content as it's scanned — Blume has no runtime substitution.
-- **Assets are served in place.** Referenced folders like `images/` are served through [`content.assets`](/docs/content/sources) rather than moved to `public/`, so nothing is relocated.
-- **Languages map to i18n.** A multi-language `docs.json` maps to Blume's [`i18n`](/docs/content/i18n), with the language switch handled by Blume's locale routing instead of a nav selector.
-
-Because it reads the same `docs.json` and runs the same transforms, what you see in bridge mode is what you'd get from a full migration.
-
-## Bridge vs. migrate
-
-<CardGroup cols={2}>
-  <Card title="Bridge mode" icon="cable">
-    **Try Blume with zero changes.** Nothing is written; your Mintlify project
-    stays exactly as it is. Ideal for evaluating Blume, running both dev servers
-    side by side, or a reversible spike.
-  </Card>
-  <Card title="Migrate" href="/docs/advanced/migrate" icon="arrow-right">
-    **Convert for good.** [`blume migrate mintlify`](/docs/advanced/migrate)
-    rewrites your pages, config, and assets in place so Blume becomes the source
-    of truth. Do this once you've decided to switch.
-  </Card>
-</CardGroup>
-
-Everything you can do in bridge mode, you can do permanently by migrating — bridge is the preview, migrate is the commit.
-
-## Limitations
-
-- **Mintlify only.** Bridge detection is Mintlify-specific. The other frameworks — Fumadocs, Nextra, Starlight — need a [one-shot migration](/docs/advanced/migrate).
-- **Same idiom gaps as the migrator.** Components without a Blume equivalent are transformed on a best-effort basis; when you hit one, [migrate](/docs/advanced/migrate) and address the warnings, or switch that page to a Blume-native equivalent such as the [OpenAPI reference](/docs/advanced/api-reference).
-- **No runtime variables.** As with a migration, `{{variable}}` values are inlined at scan time rather than substituted at runtime.
-
-<CardGroup cols={2}>
-  <Card title="Migrate" href="/docs/advanced/migrate" icon="arrow-right">
-    Convert a Mintlify, Fumadocs, Nextra, or Starlight project permanently.
-  </Card>
-  <Card title="Content sources" href="/docs/content/sources" icon="folder-tree">
-    How the `mintlify` source and `content.assets` fit into Blume's content
-    graph.
-  </Card>
-</CardGroup>

package/docs/advanced/migrate.mdx

@@ -1,124 +0,0 @@
----
-title: Migrate
-description: Convert a Mintlify, Fumadocs, Nextra, or Starlight project to Blume in one command — config, content, navigation, and assets translated to idiomatic Blume.
----
-
-Already have a docs site somewhere else? `blume migrate` is a one-shot codemod that converts a project from another docs framework into Blume — translating the config, rewriting each page to idiomatic Blume MDX, converting navigation files, and relocating assets, all in place. When it finishes you have a `blume.config.ts` and a tree that `blume dev` can serve.
-
-```bash
-npx blume migrate <tool>
-```
-
-The `<tool>` is the framework you're coming from:
-
-| Tool | Detects | Command |
-| --- | --- | --- |
-| [Mintlify](#mintlify) | `docs.json` / `mint.json` | `blume migrate mintlify` |
-| [Fumadocs](#fumadocs) | `content/docs` + `meta.json` | `blume migrate fumadocs` |
-| [Nextra](#nextra) | `content/` or `pages/` + `_meta` | `blume migrate nextra` |
-| [Starlight](#starlight) | `src/content/docs` + `astro.config.*` | `blume migrate starlight` |
-
-:::warning
-A migration **rewrites files in place** — pages, config, navigation, and assets. Commit (or stash) your work first so you can review the diff and roll back cleanly.
-:::
-
-## What a migration does
-
-Every migrator runs the same shape of work, tuned to the source framework:
-
-<Steps>
-  <Step title="Translate the config">
-    The framework's config — `docs.json`, a `starlight({...})` block, and so on — becomes a `blume.config.ts` at your project root, with navigation, theme, and site chrome mapped across.
-  </Step>
-  <Step title="Rewrite every page">
-    Each `.md`/`.mdx` file is rewritten to idiomatic Blume markup: framework callouts become [`:::` directives](/docs/content/syntax), components are renamed or converted, and frontmatter is mapped to Blume's [page schema](/docs/reference/frontmatter). Keys Blume doesn't recognize are dropped and reported.
-  </Step>
-  <Step title="Convert navigation">
-    Navigation files (`_meta.{js,ts,json}`, `meta.json`) become typed [`meta.ts`](/docs/content/meta) files, preserving order and titles.
-  </Step>
-  <Step title="Relocate assets and scripts">
-    Referenced asset folders are kept in place and served via [`content.assets`](/docs/content/sources); loose top-level files move under `public/`. Your `dev`/`build`/`start` npm scripts are repointed at the matching `blume` commands.
-  </Step>
-</Steps>
-
-When it's done the CLI prints how many files it touched, a list of **warnings** — anything that needs a human eye, like a component with no Blume equivalent or a dropped frontmatter key — and a reminder to review the generated config:
-
-```txt
-✔ Migrated 42 content file(s).
-⚠ Components without a Blume equivalent need manual review: <Frame>.
-⚠ Dropped unsupported page frontmatter keys: mode, "og:image".
-▶ Review blume.config.ts and run `blume dev`.
-```
-
-## Tools
-
-### Mintlify
-
-Reads `docs.json` (or legacy `mint.json`) and rewrites every page **in place** — content stays at the project root (`content.root` is `"."`).
-
-- Snippets under `/snippets` are inlined as includes; component snippets (e.g. `.jsx`) are kept and their imports rewritten to relative paths.
-- A Mintlify `openapi` spec — declared top-level or on a nav group (a path, URL, or `{ source, directory }`) — maps to Blume's [native OpenAPI reference](/docs/advanced/api-reference) (`openapi.sources`), which renders one real page per operation. A group's `directory` becomes the reference's route; endpoint refs like `GET /users` are dropped since Blume generates them from the spec.
-- `docs.json` `variables` are inlined into content — Blume has no runtime `{{variable}}` substitution.
-- The source `docs.json`/`mint.json` is removed once `blume.config.ts` is safely written. Leaving it around would keep the project a [Bridge mode](/docs/advanced/bridge) candidate — a later run without a Blume config would silently serve the un-migrated Mintlify site.
-- Multi-language projects map to [`i18n.locales`](/docs/content/i18n); the language nav selector is dropped in favor of Blume's locale switching.
-- Icons resolve against the real bundled libraries — Font Awesome (free), Lucide, and Tabler. The migrator sets [`icons.library: fontawesome`](/docs/content/components#default-library) (Mintlify's default), so Font Awesome names (`shield-halved`, `gauge-high`, `layer-group`, …) and `iconType` styles render unchanged. Pro-only FA styles (`light`/`thin`/`duotone`/`sharp-solid`) fall back to solid.
-- Fonts map to [`theme.fonts`](/docs/configuration/theming) when the family is one of Blume's curated Google Fonts (`fonts.family`, or a `heading`/`body` split); a family outside that set is warned about, not guessed. Header links (`navbar.links`/`navbar.primary`) and footer socials (`footer.socials`) have no `blume.config` equivalent yet, so they're reported as warnings rather than dropped silently — re-add them with [`navigation.tabs`](/docs/content/navigation) or a Header/Footer [layout override](/docs/advanced/custom-pages). The contextual page menu and last-updated timestamp are already Blume defaults.
-- Field components — [`<ParamField>`, `<ResponseField>`, `<RequestField>`](/docs/content/components#api-fields) — render natively via Blume's compat components, so hand-written CLI/SDK/endpoint field docs carry over unchanged. Any remaining component with no Blume equivalent (e.g. `<Update>`) is flagged for manual review.
-
-:::tip
-Want to preview Blume against a Mintlify codebase **without** rewriting anything? Run `blume dev` with no config and Blume serves `docs.json` as-is in [Bridge mode](/docs/advanced/bridge). Migrate when you're ready to commit.
-:::
-
-### Fumadocs
-
-Reads `content/docs` + `meta.json`. Moves pages into `docs/`, preserving the `/docs` route prefix, and rewrites Fumadocs MDX to Blume markup: callouts, `<Cards>`/`<Accordions>`/`<Files>`, `<Tabs items>`, and `<include>` directives are all converted. Each `meta.json` becomes a typed `meta.ts`.
-
-### Nextra
-
-Reads `content/` or `pages/` plus `_meta` files. Moves pages into `docs/`, rewrites `<Callout>`s to [directives](/docs/content/syntax), and converts every `_meta.{js,ts,json}` into a typed `meta.ts` — navigation order and titles preserved.
-
-### Starlight
-
-Reads `src/content/docs` + your `astro.config.*`. Translates the `starlight({...})` options into `blume.config.ts` and rewrites each page **in place** (content stays under `src/content/docs`): asides become directives, components are renamed, and frontmatter is mapped across.
-
-## After migrating
-
-<Steps>
-  <Step title="Review the config">
-    Open `blume.config.ts` and check the mapped navigation, theme, and site
-    settings. The migrator is thorough but conservative — some source options
-    have no Blume equivalent and are left out.
-  </Step>
-  <Step title="Read the warnings">
-    Each warning points at something the codemod couldn't fully translate. Work
-    through them before shipping.
-  </Step>
-  <Step title="Run the dev server">
-    Serve the migrated site. Blume [validates your content](/docs/reference/cli#validating-links) as it serves it, so broken links, missing anchors, and schema errors surface immediately.
-
-    ```bash
-    blume dev
-    ```
-
-  </Step>
-  <Step title="Delete leftovers">
-    Old framework files (lockfile entries, `astro.config`, `theme.config`,
-    framework dependencies) are left untouched so nothing is lost. Remove them
-    by hand once you've confirmed the site builds.
-  </Step>
-</Steps>
-
-<CardGroup cols={2}>
-  <Card title="Bridge mode" href="/docs/advanced/bridge" icon="cable">
-    Serve a Mintlify project with `blume dev` — no migration, no file changes.
-  </Card>
-  <Card title="CLI reference" href="/docs/reference/cli" icon="terminal">
-    Every command and flag, including `blume migrate`.
-  </Card>
-  <Card title="Content sources" href="/docs/content/sources" icon="folder-tree">
-    How Blume scans content, assets, and remote sources into a site.
-  </Card>
-  <Card title="Frontmatter" href="/docs/reference/frontmatter" icon="file-text">
-    The page schema your migrated frontmatter is mapped onto.
-  </Card>
-</CardGroup>

package/src/astro/static-assets.ts

@@ -1,124 +0,0 @@
-import { createReadStream, existsSync, statSync } from "node:fs";
-import type { Stats } from "node:fs";
-import { cp } from "node:fs/promises";
-import type { IncomingMessage, ServerResponse } from "node:http";
-
-import { extname, join, relative, resolve, sep } from "pathe";
-
-import type { AssetMount } from "../core/assets.ts";
-
-/** Content types for the asset extensions a docs project commonly serves. */
-const MIME_TYPES: Record<string, string> = {
-  ".avif": "image/avif",
-  ".css": "text/css; charset=utf-8",
-  ".gif": "image/gif",
-  ".ico": "image/x-icon",
-  ".jpeg": "image/jpeg",
-  ".jpg": "image/jpeg",
-  ".js": "text/javascript; charset=utf-8",
-  ".json": "application/json; charset=utf-8",
-  ".mp4": "video/mp4",
-  ".otf": "font/otf",
-  ".pdf": "application/pdf",
-  ".png": "image/png",
-  ".svg": "image/svg+xml",
-  ".ttf": "font/ttf",
-  ".txt": "text/plain; charset=utf-8",
-  ".webm": "video/webm",
-  ".webp": "image/webp",
-  ".woff": "font/woff",
-  ".woff2": "font/woff2",
-};
-
-const mimeType = (file: string): string =>
-  MIME_TYPES[extname(file).toLowerCase()] ?? "application/octet-stream";
-
-/** Whether `child` is `parent` itself or a path nested under it. */
-const isContained = (parent: string, child: string): boolean => {
-  const rel = relative(parent, child);
-  return rel === "" || (!rel.startsWith("..") && !rel.startsWith(sep));
-};
-
-/** Resolve a request URL to an on-disk file within one of the mounts, if any. */
-const resolveRequest = (url: string, mounts: AssetMount[]): string | null => {
-  let pathname: string;
-  try {
-    pathname = decodeURIComponent(
-      (url.split("?")[0] ?? "").split("#")[0] ?? ""
-    );
-  } catch {
-    // Malformed percent-encoding (`/images/%zz`) throws URIError; treat it as
-    // a plain miss (404) rather than a middleware exception.
-    return null;
-  }
-  for (const mount of mounts) {
-    if (pathname !== mount.url && !pathname.startsWith(`${mount.url}/`)) {
-      continue;
-    }
-    // `.` + rel keeps the join relative so an absolute-looking suffix can't
-    // escape the mount; the containment check rejects `..` traversal outright.
-    const file = resolve(mount.dir, `.${pathname.slice(mount.url.length)}`);
-    if (isContained(mount.dir, file)) {
-      return file;
-    }
-  }
-  return null;
-};
-
-/** `statSync` that returns null instead of throwing on a missing file. */
-const statFile = (file: string): Stats | null => {
-  try {
-    return statSync(file);
-  } catch {
-    return null;
-  }
-};
-
-/**
- * A dev-server middleware that serves `content.assets` mounts (top-level dirs
- * kept in place, e.g. a migrated `images/`) at their site URL. Astro only serves
- * `publicDir` in dev, so without this those references would 404. Non-matching
- * requests, and any path that isn't a real file, fall through to Astro. Stat is
- * synchronous — this is dev-only middleware and mirrors how sirv serves statics.
- */
-export const serveAssetMounts =
-  (mounts: AssetMount[]) =>
-  (req: IncomingMessage, res: ServerResponse, next: () => void): void => {
-    if ((req.method !== "GET" && req.method !== "HEAD") || !req.url) {
-      next();
-      return;
-    }
-    const file = resolveRequest(req.url, mounts);
-    const stats = file ? statFile(file) : null;
-    if (!(file && stats?.isFile())) {
-      next();
-      return;
-    }
-    res.setHeader("Content-Type", mimeType(file));
-    res.setHeader("Content-Length", String(stats.size));
-    if (req.method === "HEAD") {
-      res.end();
-      return;
-    }
-    createReadStream(file).pipe(res);
-  };
-
-/**
- * Copy every asset mount into the build output, mirroring what Astro does with
- * `publicDir`. Runs on `astro:build:done` so in-place asset dirs ship in the
- * final `dist/`. A missing source dir is skipped (it may be referenced but
- * absent); `cp` handles both directories and single files.
- */
-export const copyAssetMounts = async (
-  mounts: AssetMount[],
-  outDir: string
-): Promise<void> => {
-  for (const mount of mounts) {
-    if (!existsSync(mount.dir)) {
-      continue;
-    }
-    const dest = join(outDir, mount.url.replace(/^\/+/u, ""));
-    // oxlint-disable-next-line no-await-in-loop -- sequential fs copies
-    await cp(mount.dir, dest, { recursive: true });
-  }
-};

package/src/cli/commands/migrate.ts

@@ -1,39 +0,0 @@
-import { defineCommand } from "citty";
-
-import { migrators } from "../../migrate/migrate.ts";
-import { logger } from "../log.ts";
-
-const makeMigrateCommand = (source: keyof typeof migrators) =>
-  defineCommand({
-    meta: {
-      description: `Migrate a ${source} project to Blume.`,
-      name: source,
-    },
-    async run() {
-      const root = process.cwd();
-      logger.start(`Migrating ${source} project`);
-      const result = await migrators[source]?.(root);
-      if (!result) {
-        logger.error(`No migrator for ${source}.`);
-        process.exit(1);
-      }
-      logger.success(`Migrated ${result.moved} content file(s).`);
-      for (const warning of result.warnings) {
-        logger.warn(warning);
-      }
-      logger.box("Review blume.config.ts and run `blume dev`.");
-    },
-  });
-
-export const migrateCommand = defineCommand({
-  meta: {
-    description: "Migrate from another docs tool to Blume.",
-    name: "migrate",
-  },
-  subCommands: {
-    fumadocs: makeMigrateCommand("fumadocs"),
-    mintlify: makeMigrateCommand("mintlify"),
-    nextra: makeMigrateCommand("nextra"),
-    starlight: makeMigrateCommand("starlight"),
-  },
-});

package/src/components/content/ApiField.astro

@@ -1,75 +0,0 @@
----
-// Shared field row behind the Mintlify-compat <ParamField>/<ResponseField>/
-// <RequestField> components: a labeled name + type + badges, with the field's
-// description rendered from the slot (which may hold rich MDX, including nested
-// <Expandable> or further fields). Styled to match the native OpenAPI reference
-// rows (src/components/openapi/), so a migrated site reads consistently.
-interface Props {
-  default?: unknown;
-  deprecated?: unknown;
-  location?: string;
-  name?: string;
-  required?: unknown;
-  type?: string;
-}
-
-const {
-  default: defaultValue,
-  deprecated,
-  location,
-  name,
-  required,
-  type,
-} = Astro.props;
-
-// Booleans arrive as MDX shorthand (`required`) or strings (`required="true"`).
-const isTrue = (value: unknown): boolean => value === true || value === "true";
-const hasDefault =
-  defaultValue !== undefined && defaultValue !== null && defaultValue !== "";
-const hasDescription = Astro.slots.has("default");
----
-
-<div class="not-prose my-2 rounded-blume border border-border px-4 py-3">
-  <div class="flex flex-wrap items-baseline gap-x-2 gap-y-1">
-    {name && <code class="font-mono text-foreground text-sm">{name}</code>}
-    {
-      location && (
-        <span class="rounded bg-muted px-1.5 py-0.5 font-medium text-[0.625rem] text-muted-foreground uppercase tracking-wide">
-          {location}
-        </span>
-      )
-    }
-    {type && <span class="text-muted-foreground text-xs">{type}</span>}
-    {
-      isTrue(required) && (
-        <span class="font-medium text-[0.625rem] text-red-600 uppercase tracking-wide dark:text-red-400">
-          required
-        </span>
-      )
-    }
-    {
-      isTrue(deprecated) && (
-        <span class="font-medium text-[0.625rem] text-muted-foreground uppercase tracking-wide line-through">
-          deprecated
-        </span>
-      )
-    }
-  </div>
-  {
-    hasDefault && (
-      <div class="mt-1 text-muted-foreground text-xs">
-        Default:{" "}
-        <code class="rounded bg-muted px-1 py-0.5 text-foreground">
-          {String(defaultValue)}
-        </code>
-      </div>
-    )
-  }
-  {
-    hasDescription && (
-      <div class="mt-1.5 text-muted-foreground text-sm [&>:first-child]:mt-0 [&>:last-child]:mb-0">
-        <slot />
-      </div>
-    )
-  }
-</div>

package/src/components/content/ParamField.astro

@@ -1,39 +0,0 @@
----
-// Mintlify-compat <ParamField>. Mintlify encodes the parameter's location in the
-// attribute name (`<ParamField path="id" />`, `query`, `header`, `body`); the
-// attribute's value is the field name. Falls back to a plain `name` prop.
-import ApiField from "./ApiField.astro";
-
-const {
-  body,
-  default: defaultValue,
-  deprecated,
-  header,
-  name,
-  path,
-  query,
-  required,
-  type,
-} = Astro.props;
-
-const locations = [
-  { key: "path", value: path },
-  { key: "query", value: query },
-  { key: "header", value: header },
-  { key: "body", value: body },
-] as const;
-const located = locations.find((entry) => typeof entry.value === "string");
-const fieldName = located ? located.value : name;
-const location = located?.key;
----
-
-<ApiField
-  default={defaultValue}
-  deprecated={deprecated}
-  location={location}
-  name={fieldName}
-  required={required}
-  type={type}
->
-  <slot />
-</ApiField>

package/src/components/content/RequestField.astro

@@ -1,23 +0,0 @@
----
-// Mintlify-compat <RequestField>: same shape as <ResponseField> — a named field
-// (`name`, `type`, `required`, `default`, `deprecated`) with a slotted body.
-import ApiField from "./ApiField.astro";
-
-const {
-  default: defaultValue,
-  deprecated,
-  name,
-  required,
-  type,
-} = Astro.props;
----
-
-<ApiField
-  default={defaultValue}
-  deprecated={deprecated}
-  name={name}
-  required={required}
-  type={type}
->
-  <slot />
-</ApiField>