glasspane-mcp 1.15.0 → 1.16.0

package/README.md

@@ -40,4 +40,15 @@ MCP 客户端配置：
 已捆绑内联，包内不存在指向源码仓库的 `file:` 依赖；`schemas/` 是 kernel schema
 的发布副本，每次 `npm run bundle` 重新同步。
 
+两个入口，各自是什么就按什么用 / two entries, each with one job：
+
+| specifier | file | 行为 / behaviour |
+| --- | --- | --- |
+| `glasspane-mcp`（`exports["."]`） | `dist/index.js` | 就是 `glasspane-mcp` 命令本体：import 它即开始跑 stdio 会话，接管该进程的 stdin/stdout。它是程序，不是库——宿主不要 import 它。 |
+| `glasspane-mcp/stdio-session`（`exports["./stdio-session"]`） | `dist/stdio-session.js` | 同一个会话的库形态（`parseArgs`、`startStdioServer`、`USAGE`、`tooLargeResponse`）：import 时既不读 stdin 也不写 stdout，只有你调用 `startStdioServer()` 才接管。要嵌进自己的进程就用这一条。 |
+
+`exports["."]` 与 `bin["glasspane-mcp"]` 指向同一个文件是刻意的：命令必须无条件运行，
+`argv[1]`/`require.main` 那类"自我判断要不要跑"的守卫曾在 19 个版本里把发布包变成 0
+字节。所以运行与否由你选哪个 specifier 决定，而不是由文件猜。
+
 License: MIT.

package/dist/audit-session.d.ts

@@ -66,6 +66,15 @@ export type TrailProvenance = "in-order" | "late" | "late-inferred";
  * that cannot say (a wiring that has not read the field yet).
  */
 export type LateArrivalAttribution = "echoed-id" | "arrival-order" | "unknown";
+/**
+ * The mechanism an `arrival-order` attribution names, in one sentence with no verdict in
+ * it. Written here because this is the layer that knows it, and put beside every surface
+ * that shows one of those frames: the trail's own
+ * {@link TRAIL_PROVENANCE_NOTES `late-inferred`} note is built from this text, and
+ * `dispatch.ts`'s late-reply log line says the same words for the ids it names, so the
+ * two surfaces cannot one day describe two different mechanisms.
+ */
+export declare const ARRIVAL_ORDER_MECHANISM: string;
 /**
  * The sentence the surface that shows the trail puts beside one id. Written here
  * because this is the layer that knows the mechanism; the tool layer renders it.
@@ -120,8 +129,6 @@ export declare class EvidenceAuditSession {
      * would have to remember to delete. `test/engine-client.test.mjs` pins both.
      */
     provenanceOf(id: string): TrailProvenance | null;
-    /** The ids currently filed as inferred; see {@link TrailProvenance}. */
-    inferredIds(): string[];
     /**
      * The trail's generation number. Every {@link restart} bumps it.
      *

package/dist/dispatch.d.ts

@@ -26,7 +26,7 @@ export declare const MCP_PROTOCOL_VERSION: "2025-06-18";
 export declare const SUPPORTED_PROTOCOL_VERSIONS: readonly string[];
 export declare const SERVER_INFO: {
     readonly name: "glasspane-mcp";
-    readonly version: "1.15.0";
+    readonly version: "1.16.0";
 };
 export declare const PARSE_ERROR = -32700;
 export declare const INVALID_REQUEST = -32600;

package/dist/engine-client.d.ts

@@ -60,8 +60,53 @@ export declare const ENGINE_SOCKET_ENV = "GLASSPANE_ENGINE_SOCK";
  * Single source all the same: the CLI argument parser in index.ts and the
  * reconnecting transport both resolve the path through this function, so an env
  * override cannot be honoured on one side only.
+ *
+ * A **blank** override is not an override. `GLASSPANE_ENGINE_SOCK=""` — which is
+ * what `export FOO=` and a launcher that means "unset" actually put in the
+ * environment — is not nullish, so honouring it literally sends `""` to
+ * `net.connect`. Measured on the delivered artifact: `gp_probe_status` answered
+ * `GP_E_ENGINE_UNREACHABLE` carrying Node's internals ("Port should be >= 0 and <
+ * 65536. Received type string ('')"), and the remedy fell back to the generic
+ * "restart the daemon" wording, i.e. the answer *invented a daemon fault* out of a
+ * variable the shell was never given. Empty-and-whitespace-only reads as "no name
+ * here", which is what the fallback guess is for; the CLI flag spelling of the same
+ * empty value is refused instead, because there an operator is naming a socket in
+ * this command line and dropping it silently would connect them to one they did not
+ * choose (`index.ts`, `http-gateway-cli.ts`).
  */
 export declare function defaultSocketPath(): string;
+/**
+ * The env override that actually names a socket, or `null` when it names nothing.
+ *
+ * `true`-for-blank is written as "returns the value or `null`" rather than as a
+ * `boolean` predicate because the caller has to carry the value onward, and a
+ * `boolean` helper leaves TypeScript unable to see that the surviving case is a
+ * string — the shape of this decision is not something a caller should be cast
+ * around.
+ *
+ * The value is *not* trimmed on the way out: a real path may contain spaces, and
+ * `/tmp/ a.sock` is somebody's socket. This only decides whether the value says
+ * anything at all. It is the single spelling of that rule so the env override and
+ * the CLI flag check (`refuseEmptySocketPath`) cannot drift into disagreeing about
+ * what "no socket named" means.
+ */
+export declare function socketOverride(value: string | undefined): string | null;
+/**
+ * Refuse a `--socket-path` that names nothing, as the usage error it is.
+ *
+ * The opposite of the env rule above, deliberately: a variable somebody exported
+ * can only say "no name here", and the fallback guess is what answers that; a flag
+ * on this command line is an operator *naming a socket*, and dropping the name they
+ * typed would leave this process bridging a daemon they did not choose. And `""` is
+ * not merely a path that does not exist — `net.connect("")` fails its own argument
+ * validation ("Port should be >= 0 and < 65536. Received type string ('')"), which
+ * arrives dressed as `GP_E_ENGINE_UNREACHABLE` with generic restart wording.
+ *
+ * Only the truly empty value is refused. A path of spaces is a path (`/tmp/ .sock`
+ * exists on a POSIX filesystem), and the honest answer for one that does not exist
+ * is the ENOENT this shell already reports, not a usage error invented here.
+ */
+export declare function refuseEmptySocketPath(value: string, flag: string): void;
 /** Fallback deadline for a method missing from the table below. */
 export declare const ENGINE_TIMEOUT_MS = 10000;
 /**