@gmickel/gno 2.9.2 → 2.10.1

package/README.md

@@ -139,7 +139,7 @@ See the [guide](docs/COMPILED-CONTEXT.md).
 
 <!-- public-truth:current-version -->
 
-> Current source version: **v2.9.2**. See [CHANGELOG.md](./CHANGELOG.md).
+> Current source version: **v2.10.1**. See [CHANGELOG.md](./CHANGELOG.md).
 
 <!-- /public-truth -->
 
@@ -332,7 +332,7 @@ Manage the detached process with `gno daemon --status` and `gno daemon --stop`.
 
 <!-- public-truth:runtime -->
 
-Requires [Bun](https://bun.sh/) >=1.3.0.
+Requires [Bun](https://bun.sh/) >=1.4.1.
 
 <!-- /public-truth -->
 

package/browser-extension/artifacts/gno-browser-clipper-v2.10.1.zip.sha256

@@ -0,0 +1 @@
+e42897b28d0fc0fca7d1d7aca6ab016255cc3b5bf20d38bcac51535499eb7f25  gno-browser-clipper-v2.10.1.zip

package/browser-extension/dist/manifest.json

@@ -21,5 +21,5 @@
   "content_security_policy": {
     "extension_pages": "script-src 'self'; object-src 'none'; connect-src http://127.0.0.1:*"
   },
-  "version": "2.9.2"
+  "version": "2.10.1"
 }

package/bunfig.toml

@@ -2,6 +2,10 @@
 plugins = ["bun-plugin-tailwind"]
 
 [test]
-preload = ["./test/preload/happy-dom.ts", "./test/preload/env-guard.ts"]
+preload = [
+  "./test/preload/temp-dir.ts",
+  "./test/preload/happy-dom.ts",
+  "./test/preload/env-guard.ts",
+]
 # Frozen evidence and local experiments are not the executable regression suite.
 pathIgnorePatterns = [".flow/artifacts/**", "notes/**"]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gmickel/gno",
-  "version": "2.9.2",
+  "version": "2.10.1",
   "description": "Local semantic search for your documents. Index Markdown, PDF, and Office files with hybrid BM25 + vector search.",
   "keywords": [
     "embeddings",
@@ -72,6 +72,7 @@
     "test:e2e:install": "bunx playwright install chromium",
     "test:package": "bun scripts/package-smoke.ts",
     "test:package:clipper": "bun scripts/package-smoke-clipper-cli.ts",
+    "test:tmp-check": "bun scripts/test-tmp-check.ts",
     "test:watch": "bun test --watch",
     "test:coverage": "bun test --coverage",
     "test:coverage:html": "bun test --coverage --html",
@@ -268,7 +269,7 @@
     "file-type": "22.0.2"
   },
   "engines": {
-    "bun": ">=1.3.0"
+    "bun": ">=1.4.1"
   },
   "trustedDependencies": [
     "bun",

package/spec/cli.md

@@ -242,8 +242,10 @@ the model with `id`, `model`, `dimensions`, `state` (`active`|`shadow`),
 Terminal output prints a `Vector partitions:` block
 unless there is exactly one healthy partition. `collections`, `totalDocuments`
 and `totalChunks` cover configured collections only: a collection removed from
-config (for example by `gno collection remove`) is not reported even while its
-rows remain in the index until the next `gno update`. `totalChunks` counts the
+config is not reported even while its rows remain in the index until the next
+command that syncs collections (`gno update`, `gno index`, `gno cleanup`). The
+embedding backlog likewise counts chunks of configured collections only.
+`gno collection remove` syncs at once, so no rows remain. `totalChunks` counts the
 distinct chunks of active documents; chunks left by deleted documents do not
 count. Per-collection chunk totals remain deduplicated by canonical chunk;
 embedded counts require matching current inputs for every active owner within
@@ -393,6 +395,13 @@ is alive but did not answer its status request within 500ms). Each resident is
 asked once with that 500ms budget, so `gno status` never waits on a hung
 resident. Terminal output lists the same issues under `Background issues:`.
 
+When an MCP client registration or a running resident uses a missing, old or
+other Bun, JSON output adds `runtimeIssues` (absent otherwise) and terminal
+output lists them under `Bun runtime:`. Each item has `kind`
+(`registration` or `resident`), `severity` (`error`, `warn` or `info`),
+`subject`, `message` and `repair`, the same findings as the doctor checks
+`mcp-runtime` and `resident-runtime` below.
+
 Local activation fingerprints use active-document identifiers and source/mirror
 hashes plus schema, tokenizer, and owned FTS synchronization metadata. Passive
 status never selects or compares stored markdown or FTS bodies. On a receipt
@@ -1090,12 +1099,12 @@ for `updateCmd`; without it the command is stopped after 10 minutes.
 
 ### gno collection remove
 
-Remove a collection from the index.
+Remove a collection from the config and the index.
 
 **Synopsis:**
 
 ```bash
-gno collection remove <name>
+gno collection remove <name> [--lock-wait <duration>] [--no-wait]
 ```
 
 **Arguments:**
@@ -1106,12 +1115,19 @@ gno collection remove <name>
 **Behavior:**
 
 - Removes collection from config
-- Marks documents as inactive (does not delete DB rows until `cleanup`)
+- Syncs the index in the same config write: the collection row and its
+  documents are deleted at once, so status, search and the embedding backlog
+  stop counting them without another command
+- Content, chunks and vectors no longer referenced by any document stay until
+  `gno cleanup`
+- Waits for the index write lease (`--lock-wait`, default 120s; `--no-wait`
+  fails at once)
 
 **Exit Codes:**
 
 - 0: Success
-- 1: Collection not found
+- 1: Collection not found or referenced by contexts
+- 2: Config save or index sync failure, or write lease busy
 
 ---
 
@@ -1122,7 +1138,7 @@ Rename a collection.
 **Synopsis:**
 
 ```bash
-gno collection rename <old> <new>
+gno collection rename <old> <new> [--lock-wait <duration>] [--no-wait]
 ```
 
 **Arguments:**
@@ -1131,10 +1147,22 @@ gno collection rename <old> <new>
 | `<old>` | string | Current collection name |
 | `<new>` | string | New collection name |
 
+**Behavior:**
+
+- Renames the collection in config and rewrites contexts scoped to it
+- Syncs the index in the same config write. Documents are keyed by collection
+  name, so the old name's documents are deleted at once and the collection is
+  empty until the next `gno update` (or `gno index`) indexes its files under
+  the new name; content and vectors not yet removed by `gno cleanup` are reused
+- Prints `Run: gno update to index it under the new name`
+- Waits for the index write lease (`--lock-wait`, default 120s; `--no-wait`
+  fails at once)
+
 **Exit Codes:**
 
 - 0: Success
-- 1: Old name not found or new name already exists
+- 1: Old name not found, new name already exists, or new name invalid
+- 2: Config save or index sync failure, or write lease busy
 
 ---
 
@@ -1507,7 +1535,12 @@ executable, which cannot start the worker, runs the phases in a child process
 of itself (internal environment flag) under the same limits; the child's
 resident memory counts toward `conversion.maxMemoryMb` (Linux `/proc`, `ps`
 elsewhere; time only on Windows). A processor that cannot start fails the file
-with `ISOLATION_UNAVAILABLE`; nothing is prepared without the budget. The
+with `ISOLATION_UNAVAILABLE`; nothing is prepared without the budget. A
+message to or from the processor that cannot be deserialized fails the file
+with `PROCESSOR_MESSAGE_FAILED` (details: `direction` `job`, `result`, or
+`unknown` for the child backend, whose channel Bun closes on both ends;
+`backend`; `phase`), replaces the processor, and writes one stderr line naming
+the direction, backend, `<collection>/<relPath>` and phase. The
 child is SIGKILLed on process exit, SIGTERM, SIGINT (via the CLI's exit
 path) and resident shutdown; on Linux it also carries a parent-death signal,
 so it dies with a SIGKILLed parent, and elsewhere it exits at its next step
@@ -2932,12 +2965,13 @@ included, is refused. JSON output is
 
 ### gno cleanup
 
-Remove orphaned content, chunks, and vectors not referenced by active documents.
+Remove documents of collections no longer in the config, then orphaned
+content, chunks, and vectors not referenced by active documents.
 
 **Synopsis:**
 
 ```bash
-gno cleanup
+gno cleanup [--lock-wait <duration>] [--no-wait]
 ```
 
 **Exit Codes:**
@@ -3019,6 +3053,30 @@ gno doctor [--json|--md]
 }
 ```
 
+The `mcp-runtime` check reads every MCP client registration GNO can install
+(all targets and scopes) and reports one `error` when a registration's Bun or
+GNO entrypoint no longer exists or its Bun is below the supported minimum
+(`engines.bun`), and `info` when it resolves to a different Bun than the one
+running doctor. A Bun version comes from a version manager's install path when
+the interpreter resolves into one, else from `<interpreter> --version` under a
+2-second limit; a probe that fails or times out reports the version as unknown.
+The registered MCP command itself is never started. A registration that runs
+the `gno` launcher finds Bun on `PATH` and is only checked for existence. Each
+detail names the client, scope and file, and the repair
+`gno mcp install --target <target> --scope <scope> --force`.
+
+The `resident-runtime` check reads the `serve` and `daemon` pid-files. A live
+resident's Bun comes from the pid-file's `bun_version` (written since this
+release) or, when absent, from `bootstrap.runtime.currentVersion` of
+`GET /api/status` on its recorded port (2-second limit; trusted only when the
+response is a GNO status payload). It is an `error` below the supported
+minimum, a `warn` when older than the Bun running doctor, and `info` when a
+resident from another GNO version does not report its Bun. The check never
+signals a process. Its repair restarts the resident: `gno <kind> --stop` then
+start it again, or, for a resident started by another GNO version (which
+`--stop` refuses), `kill <pid>` (`taskkill /PID <pid>` on Windows) and start it
+again.
+
 The `findings-pass` check reports the daemon's scheduled findings pass from
 its persisted run state: `ok` when disabled or the last run succeeded, `warn`
 on `skipped_lease` / `overdue` / no recorded run, `error` on `failed` or a
@@ -3093,7 +3151,7 @@ gno mcp install [--target <target>] [--scope <scope>] [--force] [--dry-run] [--e
 | ---------------- | ------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `--target`       | string  | claude-desktop | Target client (see table below)                                                                                                                             |
 | `--scope`        | string  | target default | Scope: `user` or `project`; LibreChat defaults to project                                                                                                   |
-| `--force`        | boolean | false          | Overwrite existing gno configuration                                                                                                                        |
+| `--force`        | boolean | false          | Repair an existing gno entry: rewrite its Bun and GNO paths, keep its other arguments, environment and keys, and apply only the options passed explicitly   |
 | `--dry-run`      | boolean | false          | Show what would be done without changes                                                                                                                     |
 | `--enable-write` | boolean | false          | Start the registered server with write tools enabled                                                                                                        |
 | `--tool-profile` | string  | full           | Advertised tool set written into the registration: `core` (7 read tools, plus capture and remember with `--enable-write`) or `full`; omitted writes no flag |
@@ -3132,6 +3190,25 @@ gno mcp install [--target <target>] [--scope <scope>] [--force] [--dry-run] [--e
 | lmstudio       | user    | `~/.lmstudio/mcp.json`                                            | `~/.lmstudio/mcp.json`                        | `~/.lmstudio/mcp.json`                        |
 | librechat      | project | `./librechat.yaml`                                                | `./librechat.yaml`                            | `./librechat.yaml`                            |
 
+**Launch paths and repair:** the command is the running Bun, the first
+argument after `run` the running package's `src/index.ts`. When either sits in
+a version manager's versioned install directory (mise, asdf or proto
+`installs/bun/<version>/` or `tools/bun/<version>/`, Homebrew
+`Cellar/bun/<version>/`), the manager's version-independent link
+(`installs/bun/latest/...`, `opt/bun/...`) is written instead, but only if it
+resolves to the same file; otherwise the versioned path is kept, the text
+output adds a note, and `--json` adds `installed.pinnedPaths`. Shims that pick
+a version from the shell environment are never written. A standalone compiled
+executable is written as is. With `--force` over an existing entry that
+launches GNO (`run <entrypoint> ... mcp ...`, or a `gno` executable), only the
+launch prefix is rewritten; `--index`, `--config`, `--tool-profile` and
+`--enable-write` change only when passed in this invocation, existing
+environment values win over the installer's data and cache directories, and
+keys GNO does not write are kept in every format, Codex TOML included;
+`installed.repaired` is `true`. A Codex key that the TOML writer cannot express
+stops the command before anything is written. An entry that does not launch GNO
+is replaced as before. Without `--force` an existing entry is refused.
+
 **Config Formats:**
 
 - JSONC-compatible (`mcpServers` key): Claude Desktop, Claude Code, Cursor, Windsurf, LM Studio
@@ -3352,6 +3429,19 @@ MCP Server Status
 }
 ```
 
+An entry is reported (and offered to the connector verifier) only when its
+keys are the launch keys (`command`, `args`, `env`; OpenCode `type: "local"`,
+`command`, `environment`) plus inert client settings: `type: "stdio"`, numeric
+`timeout` / `startup_timeout_sec` / `tool_timeout_sec`, a string
+`description`, string-array `autoApprove` / `alwaysAllow`, and boolean
+`enabled` / `disabled` (OpenCode: numeric `timeout` and `enabled`).
+`serverEntry` carries only the launch keys. An entry with `enabled: false` or
+`disabled: true` is `configured: false` without an error. Any other key or
+value, including `cwd`, another transport `type`, `url`, `headers`, and
+environment variables other than `GNO_DATA_DIR` / `GNO_CACHE_DIR`, makes the
+entry `configured: false` with `error: "Malformed MCP server entry"`, and the
+connector verifier reports it as `connector_unsupported_config`.
+
 **Exit Codes:**
 
 - 0: Success

package/spec/mcp.md

@@ -2830,7 +2830,7 @@ Full index: sync files + generate embeddings (write-enabled). Runs as background
 
 ### gno_remove_collection
 
-Remove a collection from config (write-enabled). Indexed data is retained.
+Remove a collection from config and delete its documents from the index (write-enabled). Content, chunks and vectors stay until `gno cleanup`; `indexedDataRetained` is always `true` for that reason.
 
 **Input Schema:**
 

package/spec/output-schemas/mcp-remove-result.schema.json

@@ -28,12 +28,12 @@
     },
     "indexedDataRetained": {
       "type": "boolean",
-      "description": "Indexed data retention flag",
+      "description": "Always true: the collection's documents are deleted, but content, chunks and vectors stay in the index until gno cleanup",
       "const": true
     },
     "note": {
       "type": "string",
-      "description": "Explanation of retained data"
+      "description": "What was deleted and what stays until gno cleanup"
     }
   }
 }

package/src/app/bun-runtime.ts

@@ -0,0 +1,41 @@
+/**
+ * Minimum supported Bun (fn-213).
+ *
+ * `engines.bun` in package.json is the single source of truth. Bun 1.4.0
+ * and 1.4.1 fixed structured-clone bugs in the path worker messages take,
+ * which can crash a long-running process; older runtimes still start, but
+ * `serve`, `daemon` and `mcp` say so once on stderr.
+ *
+ * @module src/app/bun-runtime
+ */
+
+import pkg from "../../package.json";
+
+/** Supported Bun range, e.g. `>=1.4.1`. */
+export const BUN_ENGINE_RANGE: string = pkg.engines.bun;
+
+/** The minimum version in that range, e.g. `1.4.1`. */
+export const BUN_FLOOR: string = BUN_ENGINE_RANGE.replace(/^>=\s*/, "");
+
+/** Whether a Bun version is within the supported range. */
+export function bunMeetsFloor(version: string = Bun.version): boolean {
+  return Bun.semver.satisfies(version, BUN_ENGINE_RANGE);
+}
+
+/** One-line warning for a command started on an unsupported Bun, else null. */
+export function bunFloorWarning(
+  command: string,
+  version: string = Bun.version
+): string | null {
+  if (bunMeetsFloor(version)) return null;
+  return `gno ${command}: running on Bun ${version}, older than the supported minimum ${BUN_FLOOR}; older runtimes can crash long-running processes. Upgrade Bun and restart.`;
+}
+
+/** Print the warning for `command` when the running Bun is unsupported. */
+export function warnIfBunBelowFloor(
+  command: string,
+  write: (line: string) => void = console.warn
+): void {
+  const warning = bunFloorWarning(command);
+  if (warning) write(warning);
+}

package/src/cli/commands/cleanup.ts

@@ -1,6 +1,7 @@
 /**
  * gno cleanup command implementation.
- * Remove orphaned content, chunks, vectors not referenced by active documents.
+ * Remove documents of collections no longer configured, then orphaned
+ * content, chunks and vectors not referenced by active documents.
  *
  * @module src/cli/commands/cleanup
  */
@@ -61,6 +62,13 @@ export async function cleanup(
   }
 
   try {
+    // Drop collections no longer in the config first (their documents follow
+    // by cascade), so their content, chunks and vectors count as orphans.
+    const syncResult = await store.syncCollections(config.collections);
+    if (!syncResult.ok) {
+      return { success: false, error: syncResult.error.message };
+    }
+
     const cleanupResult = await store.cleanupOrphans();
     if (!cleanupResult.ok) {
       return { success: false, error: cleanupResult.error.message };

package/src/cli/commands/collection/remove.ts

@@ -3,43 +3,62 @@
  */
 
 import { removeCollection } from "../../../collection";
-import { applyConfigFileChange } from "../../../core/config-mutation";
+import { applyConfigChange } from "../../../core/config-mutation";
 import { CliError } from "../../errors";
+import { initStore } from "../shared";
 
 export async function collectionRemove(
   name: string,
-  options: { configPath?: string } = {}
+  options: { configPath?: string; indexName?: string } = {}
 ): Promise<void> {
-  const mutation = await applyConfigFileChange(
-    { configPath: options.configPath },
-    (config) => {
-      const result = removeCollection(config, { name });
-      return result.ok
-        ? {
-            ok: true as const,
-            config: result.config,
-            value: result.collection,
-          }
-        : {
-            ok: false as const,
-            error: result.message,
-            code: result.code,
-          };
+  // Open the index so the removal reaches the store in the same locked
+  // boundary: syncing collections deletes the collection row, and its
+  // documents follow by cascade. A config-only edit left them active (and
+  // counted in the embedding backlog) until some later command synced.
+  const initialized = await initStore({
+    configPath: options.configPath,
+    indexName: options.indexName,
+    syncConfig: false,
+    allowEmptyCollections: true,
+  });
+  if (!initialized.ok) {
+    throw new CliError("RUNTIME", initialized.error);
+  }
+
+  try {
+    const mutation = await applyConfigChange(
+      { store: initialized.store, configPath: initialized.actualConfigPath },
+      (config) => {
+        const result = removeCollection(config, { name });
+        return result.ok
+          ? {
+              ok: true as const,
+              config: result.config,
+              value: result.collection,
+            }
+          : {
+              ok: false as const,
+              error: result.message,
+              code: result.code,
+            };
+      }
+    );
+
+    if (!mutation.ok) {
+      // Map collection error codes to CLI error codes
+      const cliCode =
+        mutation.code === "VALIDATION" ||
+        mutation.code === "NOT_FOUND" ||
+        mutation.code === "HAS_REFERENCES"
+          ? "VALIDATION"
+          : "RUNTIME";
+      throw new CliError(cliCode, mutation.error);
     }
-  );
 
-  if (!mutation.ok) {
-    // Map collection error codes to CLI error codes
-    const cliCode =
-      mutation.code === "VALIDATION" ||
-      mutation.code === "NOT_FOUND" ||
-      mutation.code === "HAS_REFERENCES"
-        ? "VALIDATION"
-        : "RUNTIME";
-    throw new CliError(cliCode, mutation.error);
+    process.stdout.write(
+      `Collection "${mutation.value?.name}" removed successfully\n`
+    );
+  } finally {
+    await initialized.store.close();
   }
-
-  process.stdout.write(
-    `Collection "${mutation.value?.name}" removed successfully\n`
-  );
 }

package/src/cli/commands/collection/rename.ts

@@ -3,19 +3,51 @@
  */
 
 import { CollectionSchema, getCollectionFromScope } from "../../../config";
-import { applyConfigFileChange } from "../../../core/config-mutation";
+import { applyConfigChange } from "../../../core/config-mutation";
 import { CliError } from "../../errors";
+import { initStore, type InitStoreResult } from "../shared";
 
 export async function collectionRename(
   oldName: string,
   newName: string,
-  options: { configPath?: string } = {}
+  options: { configPath?: string; indexName?: string } = {}
 ): Promise<void> {
   const oldCollectionName = oldName.toLowerCase();
   const newCollectionName = newName.toLowerCase();
 
-  const mutation = await applyConfigFileChange(
-    { configPath: options.configPath },
+  // Documents are keyed by collection name (URIs, FTS paths, links), so the
+  // index cannot rename them in place. Sync in the same locked boundary: the
+  // old name's documents go now instead of at some later sync, and the next
+  // update indexes the files under the new name.
+  const initialized = await initStore({
+    configPath: options.configPath,
+    indexName: options.indexName,
+    syncConfig: false,
+    allowEmptyCollections: true,
+  });
+  if (!initialized.ok) {
+    throw new CliError("RUNTIME", initialized.error);
+  }
+
+  try {
+    await renameAndSync(initialized, oldCollectionName, newCollectionName);
+  } finally {
+    await initialized.store.close();
+  }
+
+  process.stdout.write(
+    `Collection "${oldCollectionName}" renamed to "${newCollectionName}"\n` +
+      "Run: gno update to index it under the new name\n"
+  );
+}
+
+async function renameAndSync(
+  initialized: Extract<InitStoreResult, { ok: true }>,
+  oldCollectionName: string,
+  newCollectionName: string
+): Promise<void> {
+  const mutation = await applyConfigChange(
+    { store: initialized.store, configPath: initialized.actualConfigPath },
     (config) => {
       const collection = config.collections.find(
         (item) => item.name === oldCollectionName
@@ -70,8 +102,4 @@ export async function collectionRename(
       mutation.error
     );
   }
-
-  process.stdout.write(
-    `Collection "${oldCollectionName}" renamed to "${newCollectionName}"\n`
-  );
 }

package/src/cli/commands/daemon.ts

@@ -5,6 +5,7 @@ import type { FindingsPassResult } from "../../serve/findings-pass";
 import type { ResidentRuntime } from "../../serve/resident-runtime";
 import type { SessionAutomationRunResult } from "../../sessions/types";
 
+import { warnIfBunBelowFloor } from "../../app/bun-runtime";
 import {
   enforceCollectionEgress,
   EGRESS_DENIED_MESSAGE,
@@ -203,6 +204,8 @@ export async function daemon(
     },
   };
 
+  warnIfBunBelowFloor("daemon", logger.error);
+
   const runtimeResult: BackgroundRuntimeResult = await (
     deps.startBackgroundRuntime ?? startBackgroundRuntime
   )({

package/src/cli/commands/doctor.ts

@@ -45,6 +45,12 @@ import {
 import { getStoredEmbeddingFingerprint } from "../../store/vector/freshness";
 import { currentOwnerCount } from "../../store/vector/runtime-compat";
 import { storedVectorPartition } from "../../store/vector/status";
+import {
+  checkRegistrationRuntimes,
+  checkResidentRuntimes,
+  formatRuntimeIssue,
+  type RuntimeIssue,
+} from "../runtime-health";
 import {
   buildDoctorActivation,
   checkConnectorActivation,
@@ -622,6 +628,58 @@ async function checkSqliteExtensions(): Promise<DoctorCheck[]> {
  * Report the daemon's scheduled findings pass from its persisted state so a
  * misconfigured, starved, or failing scheduler is visible without the daemon.
  */
+const SEVERITY_RANK: Record<RuntimeIssue["severity"], number> = {
+  info: 0,
+  warn: 1,
+  error: 2,
+};
+
+function runtimeCheck(
+  name: string,
+  issues: RuntimeIssue[],
+  okMessage: string
+): DoctorCheck {
+  if (issues.length === 0) {
+    return { name, status: "ok", message: okMessage };
+  }
+  const worst = issues.reduce((current, issue) =>
+    SEVERITY_RANK[issue.severity] > SEVERITY_RANK[current.severity]
+      ? issue
+      : current
+  );
+  return {
+    name,
+    status: worst.severity,
+    message:
+      issues.length === 1
+        ? `${worst.subject}: ${worst.message}`
+        : `${issues.length} need attention; first: ${worst.subject}: ${worst.message}`,
+    details: issues.map(formatRuntimeIssue),
+  };
+}
+
+/** Bun used by MCP registrations and by running residents. */
+export async function checkRuntimes(
+  overrides: { cwd?: string; homeDir?: string } = {}
+): Promise<DoctorCheck[]> {
+  const [registrations, residents] = await Promise.all([
+    checkRegistrationRuntimes(overrides),
+    checkResidentRuntimes(),
+  ]);
+  return [
+    runtimeCheck(
+      "mcp-runtime",
+      registrations,
+      "MCP registrations launch an existing, supported Bun"
+    ),
+    runtimeCheck(
+      "resident-runtime",
+      residents,
+      "No running resident is on an older Bun"
+    ),
+  ];
+}
+
 export async function checkFindingsPass(
   config: Config,
   indexName?: string
@@ -727,6 +785,9 @@ export async function doctor(
   // Scheduled findings pass (daemon-only, opt-in)
   checks.push(await checkFindingsPass(config, options.indexName));
 
+  // Which Bun client registrations and running residents use (fn-213)
+  checks.push(...(await checkRuntimes()));
+
   const activation = await buildDoctorActivation(config, options);
   checks.push(checkRetrievalActivation(activation));
   const connectorActivation = checkConnectorActivation(activation);