@gjsify/devtools-mcp 0.36.0 → 0.38.0

package/lib/types/dbus-client.d.ts

@@ -33,10 +33,9 @@ export interface ConnectContext {
     sessionBusAvailable: boolean;
 }
 /**
- * The two I/O steps of the resolution, overridable ONLY so the specs can drive
- * every row of the precedence — including "stale file falls back to the session
- * bus" — on a host with no bus daemon, which is what CI and macOS are. The
- * defaults are the real GDBus calls.
+ * The resolution's two I/O steps, overridable ONLY so the specs can drive every row of
+ * the precedence — "stale file falls back to the session bus" included — on a host with
+ * no bus daemon, which is what CI and macOS are.
  */
 export interface ConnectDeps {
     dial?: (address: string) => Gio.DBusConnection;
@@ -46,21 +45,18 @@ export interface ConnectDeps {
  * Resolve the precedence into a LIVE connection — dial-then-fallback, not
  * dial-and-hope.
  *
- * The published address file outranks the session bus because it is meant to be
- * positive evidence that an app of exactly this id is listening NOW. Nothing made
- * that true: it is removed on `unexport`/`GApplication::shutdown`, and GApplication
- * installs a handler for SIGTERM only, so Ctrl-C, SIGKILL and a crash all leave it
- * behind — and `Gio.DBusConnection.new_for_address_sync` on a socket that is gone
- * throws `G_IO_ERROR_NOT_FOUND` (measured, gjs 1.88.1) out of the bridge's FIRST
- * statement. Ranking a claim above the bus is only honest if the claim is CHECKED:
- * dial it, and on failure delete the file and continue down the precedence. A stale
- * file then degrades to "the session bus, as on any Linux desktop" or to the
- * three-ways-in diagnostic, never to a raw localised GIO error.
+ * The published address file outranks the session bus as positive evidence that an app of
+ * exactly this id is listening NOW — but only if the claim is CHECKED, because nothing
+ * makes it true: GApplication handles SIGTERM only, so Ctrl-C, SIGKILL and a crash all
+ * leave the file behind, and `Gio.DBusConnection.new_for_address_sync` on a vanished
+ * socket throws `G_IO_ERROR_NOT_FOUND` (measured, gjs 1.88.1) out of the bridge's FIRST
+ * statement. So: dial it, and on failure delete it and continue down the precedence, which
+ * degrades to the session bus or to the three-ways-in diagnostic rather than to a raw
+ * localised GIO error.
  *
- * An EXPLICIT address (`--address`, `GJSIFY_DEVTOOLS_ADDRESS`) deliberately does
- * NOT fall back: the operator named it on both sides, so quietly talking to
- * something else would hide the typo instead of reporting it. It fails with a
- * message naming that address and what to do — not with GIO's.
+ * An EXPLICIT address (`--address`, `GJSIFY_DEVTOOLS_ADDRESS`) deliberately does NOT fall
+ * back: the operator named it on both sides, so talking to something else would hide the
+ * typo instead of reporting it.
  */
 export declare function connectToDevtools(ctx: ConnectContext, deps?: ConnectDeps): {
     bus: Gio.DBusConnection;
@@ -81,9 +77,8 @@ export declare class DbusDevtoolsClient {
     describeTarget(label?: string): string;
     resolve(label?: string): BusAddress;
     /**
-     * The destination for a call. A peer connection has no bus daemon and no
-     * name registry, so the message must carry NO destination — sending the
-     * well-known name there gets `ServiceUnknown` from a peer that has never
+     * A peer connection has no bus daemon and no name registry, so the message must carry
+     * NO destination: the well-known name gets `ServiceUnknown` from a peer that has never
      * heard of names.
      */
     private _destination;
@@ -92,15 +87,15 @@ export declare class DbusDevtoolsClient {
     /** Call a `() -> (s)` method and return its JSON string (pretty-printed). */
     jsonCall(label: string | undefined, method: string, params?: GLib.Variant | null): Promise<string>;
     /**
-     * Whether `busName` currently has an owner (the app is running). In peer
-     * mode there is no name registry: being connected IS the answer, because the
-     * socket belongs to exactly one app process.
+     * Whether `busName` currently has an owner, i.e. the app is running. In peer mode
+     * there is no name registry and being connected IS the answer, because the socket
+     * belongs to exactly one app process.
      */
     nameHasOwner(busName: string): Promise<boolean>;
     /**
-     * Enumerate devtools-enabled instances (base + labelled). Enumeration is a
-     * BUS feature; a peer address reaches exactly one app, so peer mode reports
-     * that one rather than pretending to have searched.
+     * Enumerate devtools-enabled instances. Enumeration is a BUS feature: a peer address
+     * reaches exactly one app, so peer mode reports that one rather than pretending to
+     * have searched.
      */
     listInstances(): Promise<DevtoolsInstanceRef[]>;
 }

package/lib/types/transport-choice.d.ts

@@ -25,16 +25,13 @@ export type ClientTransportChoice =
  * | unset | unset | absent  | yes | `session-bus` — **Linux is byte-unchanged** |
  * | unset | unset | absent  | no  | `unavailable` |
  *
- * The published address FILE deliberately outranks the session bus. It is
- * POSITIVE evidence — it exists only while an app of exactly this id runs on the
- * peer transport, and the app deletes it on shutdown — whereas "a session bus
- * exists" says nothing about the app. With the file ranked below the bus, an app
- * launched with an explicit `GJSIFY_DEVTOOLS_ADDRESS` on a Linux desktop would
- * have been reported as "no devtools-enabled app on the session bus", which is a
- * misleading answer to a question the file already answers correctly.
- *
- * Linux stays unchanged in the default case regardless: with nothing in peer
- * mode no address file is ever written, so that row is a stat() that misses.
+ * The published address FILE deliberately outranks the session bus, because it is
+ * POSITIVE evidence: it exists only while an app of exactly this id runs on the peer
+ * transport, and the app deletes it on shutdown, whereas "a session bus exists" says
+ * nothing about the app. Ranked the other way, an app launched with an explicit
+ * `GJSIFY_DEVTOOLS_ADDRESS` on a Linux desktop was reported as "no devtools-enabled app
+ * on the session bus". In the default case that row is a stat() that misses, since
+ * nothing in bus mode writes an address file.
  */
 export declare function chooseClientTransport(input: {
     optionAddress?: string | null;

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/devtools-mcp",
-    "version": "0.36.0",
+    "version": "0.38.0",
     "description": "MCP↔devtools bridge for GJS apps — exposes a running app's org.gjsify.Devtools control plane (DBus) to an AI agent as MCP tools",
     "type": "module",
     "module": "lib/esm/index.js",
@@ -39,12 +39,12 @@
         "@girs/gjs": "^4.1.0",
         "@girs/glib-2.0": "^4.1.0",
         "@girs/soup-3.0": "^4.1.0",
-        "@gjsify/devtools-protocol": "^0.36.0",
+        "@gjsify/devtools-protocol": "^0.38.0",
         "@modelcontextprotocol/sdk": "^1.29.0",
         "zod": "^4.4.3"
     },
     "peerDependencies": {
-        "@gjsify/devtools-cdp": "^0.36.0"
+        "@gjsify/devtools-cdp": "^0.38.0"
     },
     "peerDependenciesMeta": {
         "@gjsify/devtools-cdp": {
@@ -52,9 +52,9 @@
         }
     },
     "devDependencies": {
-        "@gjsify/cli": "^0.36.0",
-        "@gjsify/devtools-cdp": "^0.36.0",
-        "@gjsify/unit": "^0.36.0",
+        "@gjsify/cli": "^0.38.0",
+        "@gjsify/devtools-cdp": "^0.38.0",
+        "@gjsify/unit": "^0.38.0",
         "@types/node": "^25.9.2",
         "typescript": "^6.0.3"
     },