@feniix/bridgekit 0.10.0 → 0.12.0

package/CHANGELOG.md

@@ -4,7 +4,65 @@ All notable changes to `@feniix/bridgekit` are documented here. The format
 follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [0.10.0] - Unreleased
+## [0.12.0] - 2026-05-27
+
+### Documentation
+
+- `README.md` gets a full `bin-wrapper` adapter section under "API
+  reference" — usage example, options breakdown, `runServer`
+  contract, trusted-literal security note, and the missing-entry
+  behavior matrix. Previously the subpath had a single line in the
+  entrypoint table and zero body documentation. Closes the largest
+  gap surfaced by the post-0.11.0 doc audit.
+- `README.md` "Why" bullet and "Packaging" section updated for the
+  four-entrypoint shape and the `runBinWrapper` recommendation
+  (replaces the pre-0.11.0 manual checked-in-wrapper recipe).
+- `llms.txt` rewrites the "Mixed source-loaded hosts and compiled
+  MCP bins" section to lead with `runBinWrapper`. The 8-bullet
+  manual-wrapper recipe is demoted to a fallback bullet for
+  authors writing their own wrapper.
+- `dist/src/bin-wrapper.d.ts` added to the published-declarations
+  lists in `README.md` and `llms.txt`.
+- `docs/README.md` lists `docs/rfc-host-extras.md` in the
+  maintainer-docs catalog. The RFC is JSDoc-linked from
+  `src/core/define-tool.ts` and was missing from the catalog.
+- `src/adapters/mcp.typecheck.ts` fixes a wrong version stamp on
+  the `signalFromExtra` adversarial-pin comment (was `0.10.0 (#3)`,
+  should be `0.11.0 (#3)`). The pin's code is correct; only the
+  comment was wrong.
+
+No API or behavior changes.
+
+## [0.11.0] - 2026-05-27
+
+### Added
+
+- New subpath export `@feniix/bridgekit/bin-wrapper` shipping
+  `runBinWrapper({ metaUrl, mcpEntry, buildScript, ... })`. Eliminates
+  the ~25-line "resolve dist path → spawn build if missing → import
+  and run" boilerplate that mixed source-loaded pi + compiled MCP
+  packages have been copy-pasting. Three downstream consumers
+  (pi-sequential-thinking, pi-exa, pi-code-reasoning) carry hand-rolled
+  versions today and can migrate in one-line replacements. Tested
+  against four canonical scenarios (entry present; entry built on
+  demand; build fails non-zero; build exits 0 with file still missing)
+  plus a negative for entry modules missing the required `runServer`
+  export. Resolves
+  [#6](https://github.com/feniix/bridgekit/issues/6).
+
+### Changed
+
+- `signalFromExtra` (internal helper at `src/adapters/mcp-signal.ts`) removed.
+  The MCP SDK exposes `RequestHandlerExtra<ServerRequest, ServerNotification>`
+  with a guaranteed non-optional `signal: AbortSignal` field; the duck-typing
+  helper existed only because the contract was undocumented. `createMcpServer`'s
+  `tools/call` handler now reads `extra.signal` directly with a typed `extra`
+  parameter. No behavior change; cancellation propagation is unchanged. An
+  adversarial type-level pin in `src/adapters/mcp.typecheck.ts` fails closed
+  if the SDK ever changes `signal`'s type. Resolves
+  [#3](https://github.com/feniix/bridgekit/issues/3).
+
+## [0.10.0] - 2026-05-27
 
 ### Removed (breaking)
 

package/README.md

@@ -66,7 +66,7 @@ This package is ESM-only and supports Node.js 22.19.0 or newer. Published module
 - Define a tool once; ship it to pi and MCP without per-host forks.
 - Host-neutral tool files: no pi or MCP SDK imports in the tool definition itself.
 - TypeBox schemas pass through to MCP `inputSchema` directly — no JSON Schema conversion step.
-- Import-passive, `sideEffects: false`, three-entrypoint split (`.`, `./pi`, `./mcp`) so pi-only consumers do not pull the MCP SDK and vice versa.
+- Import-passive, `sideEffects: false`, four-entrypoint split (`.`, `./pi`, `./mcp`, `./bin-wrapper`) so pi-only consumers do not pull the MCP SDK and vice versa.
 - Conformance-tested public surface: a packed-install smoke test enforces the runtime export set, deep-import rejection, and type-level strictness against the installed declarations.
 
 ## API reference
@@ -85,11 +85,13 @@ import {
 } from "@feniix/bridgekit";
 import { registerPiTools } from "@feniix/bridgekit/pi";
 import { createMcpServer, runMcpStdioServer } from "@feniix/bridgekit/mcp";
+import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
 ```
 
 - Root entrypoint: host-neutral tool definitions, validation, and execution helpers.
 - `/pi`: pi adapter only.
 - `/mcp`: MCP server adapter only.
+- `/bin-wrapper`: optional helper for npm `bin` scripts that need to build a local compiled MCP entry on first invocation.
 
 Do not deep-import from `dist/` or `src/` in consuming packages.
 
@@ -231,6 +233,41 @@ Portable validation failures and portable `isError: true` results return `CallTo
 
 The two adapters now read in parallel: invalid args and portable `isError` results return `{ isError: true }` from both hosts by default, and the same result-guard helpers (`isValidationFailure`, `isDomainFailure`) narrow them on either side.
 
+### bin-wrapper (since 0.11.0)
+
+The `bin-wrapper` subpath ships a helper for npm `bin` scripts that load a compiled MCP entrypoint and build it on first invocation when the compiled output is missing. Replaces the ~25-line "resolve dist path → spawn build if missing → import and run" boilerplate that downstream consumers with mixed source-loaded pi + compiled MCP packages previously hand-rolled.
+
+```js
+#!/usr/bin/env node
+import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
+
+await runBinWrapper({
+  metaUrl: import.meta.url,
+  mcpEntry: "dist/extensions/mcp-server.js",
+  buildScript: "build:mcp",
+});
+```
+
+Options:
+
+- `metaUrl` (required): `import.meta.url` of the bin script. Used to locate the package root (the bin's parent directory).
+- `mcpEntry` (required): path to the compiled MCP entry, relative to the package root (e.g. `"dist/extensions/mcp-server.js"`).
+- `buildScript` (required): npm script to invoke when the entry is missing (e.g. `"build:mcp"`).
+- `buildTimeoutMs` (optional, default `60_000`): timeout for the build subprocess. Distinct "Build timed out…" diagnostic fires when exceeded.
+- `logPrefix` (optional, default `"bridgekit-bin"`): prefix on the "Failed to build…" diagnostic.
+
+The MCP entry module must export `async function runServer(): Promise<void>`. Consumers with a different export name can alias on export.
+
+**Security: `mcpEntry` and `buildScript` must be literal strings in the caller's source.** The helper joins `mcpEntry` onto the resolved package root and dynamically `import()`s it, and it passes `buildScript` to `spawnSync` (with `shell: true` on Windows where `&`, `|`, and `^` are shell metacharacters). Sourcing either from CLI args or environment variables exposes arbitrary-file import and Windows command injection.
+
+Behavior on missing entry:
+
+- Build emits the entry → import and call `runServer()`.
+- Build exits non-zero but the entry exists → recover (import and call `runServer()`).
+- Build exits 0 but the entry is still missing → exit with code 1, generic "Failed to build…" diagnostic.
+- Build exits non-zero with entry missing → exit with the build's status code, generic diagnostic.
+- Build killed by timeout (SIGTERM) → exit 1, distinct timeout diagnostic naming `buildTimeoutMs`.
+
 ## Best practices
 
 Tool definition best practices:
@@ -256,7 +293,7 @@ Package and release checklist:
 - Avoid `workspace:` or `file:` dependency ranges in publishable packages.
 - Avoid dangling `sourceMappingURL` comments: publish maps and useful sources together, or disable source maps for package builds.
 - For MCP stdio bins, ensure the executable entrypoint starts with a Node shebang, has executable mode (`chmod +x` or equivalent), and is included by `npm pack --dry-run --json`.
-- If an npm-launched bin depends on generated output, prefer a checked-in wrapper under `bin/` over pointing `bin` directly at `dist/`; the wrapper should resolve the package-local generated file and may run the package-local build for workspace/local execution.
+- If an npm-launched bin depends on generated output, use `runBinWrapper` from `@feniix/bridgekit/bin-wrapper` (since 0.11.0) — it resolves the package-local generated entry, runs the package-local build when output is missing in workspace/local execution, preserves build failures, and distinguishes timeout from build error in its diagnostic. The bin script becomes a three-line invocation; no hand-rolled wrapper needed.
 - If a package keeps a source-loaded host entrypoint (for example a pi extension source file), use a package-local MCP build behind that wrapper and narrow the build to the MCP entrypoint plus shared host-neutral modules.
 - Declare a compatible Node engine (`>=22.19.0`) in downstream packages that expose BridgeKit-powered MCP bins.
 - Run `npm run check`, `npm run test`, `npm run pack:dry-run`, and `npm run package-smoke` before publishing.
@@ -270,5 +307,5 @@ Read these files in order:
 
 1. `README.md` — public API, contracts, and best practices.
 2. `llms.txt` — compact agent-facing usage rules and anti-patterns.
-3. `examples/README.md` — copyable layouts for shared tools, pi extensions, MCP stdio servers, and per-host metadata via `hostExtras`.
-4. Published declarations such as `dist/src/index.d.ts`, `dist/src/pi.d.ts`, and `dist/src/mcp.d.ts` — canonical installed-package type contracts. In a source checkout, the matching `src/` files contain the same implementation context.
+3. `examples/README.md` — copyable layouts for shared tools, pi extensions, MCP stdio servers, per-host metadata via `hostExtras`, and bin wrappers via `runBinWrapper`.
+4. Published declarations such as `dist/src/index.d.ts`, `dist/src/pi.d.ts`, `dist/src/mcp.d.ts`, and `dist/src/bin-wrapper.d.ts` — canonical installed-package type contracts. In a source checkout, the matching `src/` files contain the same implementation context.

package/dist/src/adapters/mcp.js

@@ -2,7 +2,6 @@ import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { CallToolRequestSchema, ListToolsRequestSchema, } from "@modelcontextprotocol/sdk/types.js";
 import { executePortableTool } from "../core/execute-tool.js";
-import { signalFromExtra } from "./mcp-signal.js";
 function toMcpResult(result) {
     return {
         content: [{ type: "text", text: result.text }],
@@ -197,7 +196,7 @@ export function createMcpServer(options) {
         try {
             const result = await executePortableTool(tool, request.params.arguments ?? {}, {
                 host: "mcp",
-                signal: signalFromExtra(extra),
+                signal: extra.signal,
             });
             return toMcpResult(result);
         }

package/dist/src/bin-wrapper-internal.d.ts

@@ -0,0 +1,39 @@
+import { type SpawnSyncOptions, type SpawnSyncReturns } from "node:child_process";
+export type BinWrapperSpawnSync = (command: string, args: readonly string[], options: SpawnSyncOptions) => SpawnSyncReturns<Buffer>;
+export interface BinWrapperOptions {
+    /**
+     * `import.meta.url` of the bin script. Used to locate the package root
+     * (the bin's parent directory). Passing the helper's own `import.meta.url`
+     * would resolve the wrong package, which is why the caller must supply this.
+     */
+    metaUrl: string;
+    /**
+     * Path to the compiled MCP entry, relative to the package root.
+     *
+     * Must be a literal in the caller's source. The helper does not contain
+     * arbitrary paths — sourcing this from CLI args or env vars exposes the
+     * dynamic `import()` to attacker-controlled file paths.
+     *
+     * @example "dist/extensions/mcp-server.js"
+     */
+    mcpEntry: string;
+    /**
+     * npm script to invoke when the entry is missing.
+     *
+     * Must be a literal in the caller's source. On Windows the helper sets
+     * `shell: true` for `spawnSync`, which makes `&`, `|`, and `^` shell
+     * metacharacters; sourcing this from CLI args or env vars opens a
+     * command-injection vector on Windows.
+     *
+     * @example "build:mcp"
+     */
+    buildScript: string;
+    buildTimeoutMs?: number;
+    logPrefix?: string;
+}
+export interface BinWrapperDeps {
+    spawnSync: BinWrapperSpawnSync;
+    exit: (code: number) => never;
+}
+export declare const defaultBinWrapperDeps: BinWrapperDeps;
+export declare function runBinWrapperWithDeps(options: BinWrapperOptions, deps: BinWrapperDeps): Promise<void>;

package/dist/src/bin-wrapper-internal.js

@@ -0,0 +1,55 @@
+// Internal implementation of bin-wrapper. Ships in the published tarball
+// (the public `bin-wrapper.js` imports from it at runtime) but is not
+// reachable via package.json#exports — deep-importing this module by name
+// fails with ERR_PACKAGE_PATH_NOT_EXPORTED (pinned by scripts/smoke-package.mjs
+// under inv-deep-imports-fail).
+import { spawnSync } from "node:child_process";
+import { existsSync } from "node:fs";
+import { dirname, join, resolve } from "node:path";
+import { fileURLToPath, pathToFileURL } from "node:url";
+const DEFAULT_BUILD_TIMEOUT_MS = 60_000;
+const DEFAULT_LOG_PREFIX = "bridgekit-bin";
+export const defaultBinWrapperDeps = {
+    spawnSync,
+    exit: process.exit,
+};
+export async function runBinWrapperWithDeps(options, deps) {
+    const packageRoot = resolve(dirname(fileURLToPath(options.metaUrl)), "..");
+    const entryPath = join(packageRoot, options.mcpEntry);
+    if (!existsSync(entryPath)) {
+        const timeoutMs = options.buildTimeoutMs ?? DEFAULT_BUILD_TIMEOUT_MS;
+        const build = deps.spawnSync("npm", ["run", options.buildScript, "--silent"], {
+            cwd: packageRoot,
+            stdio: "inherit",
+            shell: process.platform === "win32",
+            timeout: timeoutMs,
+        });
+        // File presence is the load-bearing signal: a build that exits non-zero
+        // *after* emitting the entry (e.g. tsc with a post-emit diagnostic, or a
+        // build pipeline whose final step is non-fatal lint/test) is still
+        // recoverable. Only bail if the artifact we need is actually missing.
+        if (!existsSync(entryPath)) {
+            const prefix = options.logPrefix ?? DEFAULT_LOG_PREFIX;
+            // A child killed by the timeout returns status: null + signal set.
+            // Distinguish that from a build error so the operator sees the actual
+            // cause and knows about buildTimeoutMs.
+            if (build.signal !== null) {
+                console.error(`[${prefix}] Build timed out after ${timeoutMs}ms (signal ${build.signal}). ` +
+                    `Raise buildTimeoutMs or run \`npm run ${options.buildScript}\` manually.`);
+                deps.exit(1);
+            }
+            else {
+                console.error(`[${prefix}] Failed to build the local MCP server. Run \`npm run ${options.buildScript}\` and try again.`);
+                // Propagate the build's non-zero status if present; fall back to 1
+                // when status===0 with missing entry or status===null without signal.
+                deps.exit(build.status !== null && build.status !== 0 ? build.status : 1);
+            }
+        }
+    }
+    const mod = (await import(pathToFileURL(entryPath).href));
+    if (typeof mod.runServer !== "function") {
+        throw new Error(`[bridgekit/bin-wrapper] entry "${options.mcpEntry}" does not export a runServer() function. ` +
+            `Make sure your MCP server module exports \`export async function runServer()\` at the top level.`);
+    }
+    await mod.runServer();
+}

package/dist/src/bin-wrapper.d.ts

@@ -0,0 +1,25 @@
+import { type BinWrapperOptions } from "./bin-wrapper-internal.js";
+export type { BinWrapperOptions } from "./bin-wrapper-internal.js";
+/**
+ * Helper for an npm `bin` script that needs to load a compiled MCP entrypoint
+ * and build it on first invocation (workspace/local execution) when the
+ * compiled output is missing.
+ *
+ * Replaces the ~25-line "resolve dist path -> spawn build if missing ->
+ * import and run" boilerplate shipped in `examples/README.md` since 0.4.x.
+ *
+ * The MCP entry module must export `runServer(): Promise<void>`. Consumers
+ * with a different name can re-export under that alias.
+ *
+ * @example
+ * ```ts
+ * #!/usr/bin/env node
+ * import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
+ * await runBinWrapper({
+ *   metaUrl: import.meta.url,
+ *   mcpEntry: "dist/extensions/mcp-server.js",
+ *   buildScript: "build:mcp",
+ * });
+ * ```
+ */
+export declare function runBinWrapper(options: BinWrapperOptions): Promise<void>;

package/dist/src/bin-wrapper.js

@@ -0,0 +1,26 @@
+import { defaultBinWrapperDeps, runBinWrapperWithDeps } from "./bin-wrapper-internal.js";
+/**
+ * Helper for an npm `bin` script that needs to load a compiled MCP entrypoint
+ * and build it on first invocation (workspace/local execution) when the
+ * compiled output is missing.
+ *
+ * Replaces the ~25-line "resolve dist path -> spawn build if missing ->
+ * import and run" boilerplate shipped in `examples/README.md` since 0.4.x.
+ *
+ * The MCP entry module must export `runServer(): Promise<void>`. Consumers
+ * with a different name can re-export under that alias.
+ *
+ * @example
+ * ```ts
+ * #!/usr/bin/env node
+ * import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
+ * await runBinWrapper({
+ *   metaUrl: import.meta.url,
+ *   mcpEntry: "dist/extensions/mcp-server.js",
+ *   buildScript: "build:mcp",
+ * });
+ * ```
+ */
+export async function runBinWrapper(options) {
+    return runBinWrapperWithDeps(options, defaultBinWrapperDeps);
+}

package/examples/README.md

@@ -241,36 +241,23 @@ For mixed source-loaded pi + compiled MCP packages, keep the pi source entrypoin
 }
 ```
 
-The wrapper should resolve the generated MCP server relative to the installed package, build it when missing in local/workspace execution, and preserve build failures:
+The wrapper should resolve the generated MCP server relative to the installed package, build it when missing in local/workspace execution, and preserve build failures. BridgeKit ships this as a built-in helper under the `/bin-wrapper` subpath:
 
 ```js
 #!/usr/bin/env node
-import { existsSync } from "node:fs";
-import { spawnSync } from "node:child_process";
-import { dirname, join, resolve } from "node:path";
-import { fileURLToPath, pathToFileURL } from "node:url";
-
-const packageRoot = resolve(dirname(fileURLToPath(import.meta.url)), "..");
-const serverPath = join(packageRoot, "dist", "extensions", "mcp-server.js");
-
-if (!existsSync(serverPath)) {
-  const build = spawnSync("npm", ["run", "build:mcp", "--silent"], {
-    cwd: packageRoot,
-    stdio: "inherit",
-    shell: process.platform === "win32",
-    timeout: 60_000,
-  });
-
-  if (build.status !== 0 || !existsSync(serverPath)) {
-    console.error("[my-tools] Failed to build the local MCP server. Run `npm run build:mcp` and try again.");
-    process.exit(build.status && build.status !== 0 ? build.status : 1);
-  }
-}
+import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
 
-const { runServer } = await import(pathToFileURL(serverPath).href);
-await runServer();
+await runBinWrapper({
+  metaUrl: import.meta.url,
+  mcpEntry: "dist/extensions/mcp-server.js",
+  buildScript: "build:mcp",
+});
 ```
 
+`mcpEntry` and `buildScript` are the two options consumers typically vary. The MCP entry module must export `runServer(): Promise<void>` (the convention used throughout these examples). `buildTimeoutMs` (default `60_000`) and `logPrefix` (default `"bridgekit-bin"`) are available for tuning but rarely needed.
+
+Both `mcpEntry` and `buildScript` must be **literal strings** in your bin source. The helper joins `mcpEntry` onto the resolved package root and dynamically `import()`s it, and it passes `buildScript` to `spawnSync` (with `shell: true` on Windows where `&`, `|`, and `^` are shell metacharacters). Sourcing either from CLI args, environment variables, or other runtime input exposes arbitrary-file import and Windows command injection — the trusted-literal expectation is the threat model.
+
 Commit the wrapper with executable mode (`chmod +x bin/my-tools-mcp.js`) and verify `npm pack --dry-run --json` includes it with executable mode.
 
 MCP behavior:

package/llms.txt

@@ -7,7 +7,7 @@ Use this package when you need to define a tool once and expose it through both
 1. `README.md` — public API, contracts, best practices, packaging notes.
 2. `llms.txt` — compact agent-facing usage rules and anti-patterns.
 3. `examples/README.md` — copyable end-to-end layouts for shared tools, pi extension wiring, MCP stdio server wiring, and per-host metadata via `hostExtras`.
-4. Published declarations such as `dist/src/index.d.ts`, `dist/src/pi.d.ts`, and `dist/src/mcp.d.ts` — canonical installed-package type contracts. In a source checkout, the matching `src/` files contain implementation context.
+4. Published declarations such as `dist/src/index.d.ts`, `dist/src/pi.d.ts`, `dist/src/mcp.d.ts`, and `dist/src/bin-wrapper.d.ts` — canonical installed-package type contracts. In a source checkout, the matching `src/` files contain implementation context.
 
 ## Import map
 
@@ -20,11 +20,13 @@ import {
 } from "@feniix/bridgekit";
 import { registerPiTools } from "@feniix/bridgekit/pi";
 import { createMcpServer, runMcpStdioServer } from "@feniix/bridgekit/mcp";
+import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper"; // optional: built-in bin wrapper for mixed source-loaded pi + compiled MCP packages
 ```
 
 - Root entrypoint: host-neutral tool definitions, validation, and execution helpers.
 - `/pi`: pi adapter only.
 - `/mcp`: MCP server adapter only.
+- `/bin-wrapper`: optional helper for npm `bin` scripts that build a local compiled MCP entry on first invocation. `mcpEntry` and `buildScript` must be literal strings in the caller's source (they're the dynamic-import target and the `spawnSync` arg; sourcing them from env or CLI is an arbitrary-file-import and Windows command-injection vector).
 
 Do not deep-import from `dist/` or `src/` in consumer code. Reading published declarations for documentation is fine; imports should use the package entrypoints above.
 
@@ -102,12 +104,24 @@ Some hosts, such as pi in source-extension packages, may intentionally load Type
 
 - Keep the host source entrypoint if that is the package convention, e.g. `pi.extensions: ["./extensions/index.ts"]`.
 - Add a package-local MCP build and point npm `bin` at a checked-in wrapper under `bin/`, not directly at generated `dist/` output.
-- The wrapper should resolve the package-local generated MCP server, run the package-local build when output is missing in workspace/local execution, and preserve non-zero build failures.
+- **Use the built-in `runBinWrapper` helper** (since 0.11.0) instead of a hand-rolled wrapper. It resolves the package-local generated entry, runs the package-local build when output is missing in workspace/local execution, preserves non-zero build failures, recovers when the build emits the entry despite a non-zero exit, and emits a distinct timeout diagnostic when `spawnSync` is killed by `buildTimeoutMs`:
+
+  ```js
+  #!/usr/bin/env node
+  import { runBinWrapper } from "@feniix/bridgekit/bin-wrapper";
+  await runBinWrapper({
+    metaUrl: import.meta.url,
+    mcpEntry: "dist/extensions/mcp-server.js",
+    buildScript: "build:mcp",
+  });
+  ```
+
+  `mcpEntry` and `buildScript` must be literal strings — sourcing them from CLI args or env vars opens arbitrary-file import and Windows command injection. The MCP entry module must export `async function runServer(): Promise<void>`.
 - Narrow the MCP build to the MCP entrypoint and shared host-neutral modules; avoid compiling pi adapter entrypoints into the standalone MCP path.
 - Put runtime imports used by the compiled MCP bin in `dependencies`, not only peers or dev dependencies.
 - Declare BridgeKit's Node engine requirement in the downstream package (`>=22.19.0`).
-- Ensure the checked-in wrapper is executable (`chmod +x` or equivalent) and verify the mode with `npm pack --dry-run --json`.
-- Test wrapper behavior for existing output, missing output, failed builds, and builds that exit successfully without creating the expected file.
+- Ensure the bin script is executable (`chmod +x` or equivalent) and verify the mode with `npm pack --dry-run --json`.
+- If you write your own wrapper instead of using `runBinWrapper`, test the four behavior modes: existing output, missing output that the build creates, failed builds (non-zero exit), and builds that exit successfully without creating the expected file.
 
 ## Anti-patterns
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feniix/bridgekit",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "description": "BridgeKit defines TypeBox-backed tools once and adapts them to pi, MCP, and other hosts.",
   "keywords": [
     "pi",
@@ -37,6 +37,10 @@
       "types": "./dist/src/mcp.d.ts",
       "import": "./dist/src/mcp.js"
     },
+    "./bin-wrapper": {
+      "types": "./dist/src/bin-wrapper.d.ts",
+      "import": "./dist/src/bin-wrapper.js"
+    },
     "./package.json": "./package.json"
   },
   "scripts": {

package/dist/src/adapters/mcp-signal.d.ts

@@ -1,9 +0,0 @@
-/**
- * Defensively pulls an `AbortSignal` out of MCP request `extra`. The MCP SDK
- * does not formally type a `signal` on `extra`, so the shape is sniffed
- * structurally.
- *
- * Validated against `@modelcontextprotocol/sdk` v1.x. Revalidate on any SDK
- * major bump in case the cancellation channel moves or gains a typed surface.
- */
-export declare function signalFromExtra(extra: unknown): AbortSignal | undefined;

package/dist/src/adapters/mcp-signal.js

@@ -1,15 +0,0 @@
-/**
- * Defensively pulls an `AbortSignal` out of MCP request `extra`. The MCP SDK
- * does not formally type a `signal` on `extra`, so the shape is sniffed
- * structurally.
- *
- * Validated against `@modelcontextprotocol/sdk` v1.x. Revalidate on any SDK
- * major bump in case the cancellation channel moves or gains a typed surface.
- */
-export function signalFromExtra(extra) {
-    if (!extra || typeof extra !== "object" || !("signal" in extra)) {
-        return undefined;
-    }
-    const signal = extra.signal;
-    return signal instanceof AbortSignal ? signal : undefined;
-}