glasspane-mcp 1.1.1 → 1.2.0

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.1.1";
+    readonly version: "1.2.0";
 };
 export declare const PARSE_ERROR = -32700;
 export declare const INVALID_REQUEST = -32600;

package/dist/engine-client.d.ts

@@ -12,10 +12,36 @@ export declare function daemonUnreachableRemedy(): string;
 /** Env override for the daemon socket path (default below). */
 export declare const ENGINE_SOCKET_ENV = "GLASSPANE_ENGINE_SOCK";
 /**
- * The daemon listens here by default (spec §3.1). Single source: 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.
+ * Where this shell connects when nothing was named, in order: `GLASSPANE_ENGINE_SOCK`
+ * (the env var {@link ENGINE_SOCKET_ENV} spells), then the explicit
+ * `--socket-path` this shell's own CLI accepts, then the fallback below.
+ *
+ * The fallback is a **guess made from `$HOME`**, and it is worth being exact
+ * about which guess: `os.homedir()` reads `$HOME`, while the daemon's own
+ * default is `StateRoot.homeDefault()` = `NSHomeDirectory() + "/.glasspane"`,
+ * which on macOS does **not** consult `$HOME` — the same non-inheritance that
+ * has already cost this project real data, and the reason a caller cannot
+ * isolate a run by exporting `HOME`. So in a process whose `$HOME` points into
+ * a sandbox the two sides resolve **different directories**: this shell goes
+ * looking for `$HOME/.glasspane/engine.sock` inside the sandbox while the daemon
+ * is still serving only the socket under the real home. Nor is there a third
+ * case to cover by guessing better — a daemon started with `--state-dir <root>`
+ * listens on `<root>/daemon.sock`, which no value of `$HOME` points at.
+ *
+ * The reliable route is therefore to stop deriving and to say which socket: set
+ * `GLASSPANE_ENGINE_SOCK`, or pass `--socket-path`. The installer's launchd job
+ * hands the daemon an explicit `--socket-path` already, which is what makes an
+ * installed pair agree — so read that value back rather than recomputing it;
+ * this shell's `--help` gives the command.
+ *
+ * Deliberately not "fixed" by asking the daemon: before a connection exists
+ * there is no daemon to ask, and `hello` is itself answered after connecting.
+ * Matching the daemon's home lookup from Node would take an FFI call to
+ * `NSHomeDirectory()`, which this shell does not have.
+ *
+ * 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.
  */
 export declare function defaultSocketPath(): string;
 /** Fallback deadline for a method missing from the table below. */

package/dist/http-gateway-cli.d.ts

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+export {};
+//# sourceMappingURL=http-gateway-cli.d.ts.map