gm-skill 2.0.1847 → 2.0.1848

package/gm-plugkit/cli.js

@@ -151,20 +151,6 @@ function statusServing(st, freshMs) {
   return Number.isFinite(st.ts) && (now - st.ts) < freshMs;
 }
 
-function sleepSync(ms) {
-  Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, ms);
-}
-
-function waitForWatcherHeartbeat(dir, deadlineMs, freshMs) {
-  const t0 = Date.now();
-  while (Date.now() - t0 < deadlineMs) {
-    const st = readStatus(dir);
-    if (statusServing(st, freshMs)) return st;
-    sleepSync(300);
-  }
-  return null;
-}
-
 function ensureSpoolDir() {
   try { fs.mkdirSync(spoolDir(), { recursive: true }); } catch (_) {}
 }
@@ -285,22 +271,21 @@ function writeCliError(phase, err) {
     process.exit(1);
   }
 
-  const serving = waitForWatcherHeartbeat(spoolDir(), 30000, 12000);
-  if (!serving) {
-    const errMsg = `watcher spawned (pid=${daemon.pid}) but .status.json heartbeat not fresh within 30s`;
-    writeCliError('watcher-heartbeat-timeout', new Error(errMsg));
-    console.error('Daemon start failed:', errMsg);
-    process.exit(1);
-  }
-
-  writeCliStatus({ phase: 'ready', version: bootstrapResult.version, daemon_pid: daemon.pid, watcher_pid: serving.pid, log: daemon.logPath });
+  // Fire-and-forget: the daemon child is already detached+unref'd by
+  // startSpoolDaemon(), so the CLI process itself has nothing left to do.
+  // Waiting here for a heartbeat confirmation (removed) used to block the
+  // calling shell for the full bootstrap+first-heartbeat duration -- up to
+  // 30s on a healthy boot, worse on a slow/degraded one -- holding up every
+  // caller even though the daemon spawn itself is near-instant. A caller
+  // that needs serving-confirmation reads .gm/exec-spool/.status.json
+  // directly (ts freshness) rather than blocking this call on it.
+  writeCliStatus({ phase: 'daemon-spawned', version: bootstrapResult.version, daemon_pid: daemon.pid, log: daemon.logPath });
 
   console.log(JSON.stringify({
     ok: true,
     binary: bootstrapResult.binaryPath,
     daemon,
-    watcher_pid: serving.pid,
-    message: 'plugkit ready, spool watcher serving'
+    message: 'plugkit daemon spawned, not yet confirmed serving -- check .gm/exec-spool/.status.json for heartbeat freshness'
   }));
   process.exit(0);
 })().catch((err) => {

package/gm-plugkit/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-plugkit",
-  "version": "2.0.1847",
+  "version": "2.0.1848",
   "description": "Bootstrap and daemon-spawn tool for gm plugkit binary. Downloads the correct platform binary, verifies SHA256, and starts the spool watcher daemon. Includes plugkit-wasm-wrapper for WASM-based spool watching.",
   "main": "index.js",
   "bin": {

package/gm.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.1847",
+  "version": "2.0.1848",
   "description": "Spool-dispatch orchestration engine with unified state machine, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-skill",
-  "version": "2.0.1847",
+  "version": "2.0.1848",
   "description": "Canonical universal harness — AI-native software engineering via skill-driven orchestration; bootstraps plugkit for task execution and session isolation. Install in any AI coding agent host.",
   "author": "AnEntrypoint",
   "license": "MIT",

package/skills/gm/SKILL.md

@@ -52,7 +52,7 @@ cat .gm/exec-spool/.status.json 2>/dev/null; echo ---; cat .gm/exec-spool/.turn-
 bun x gm-plugkit@latest spool
 ```
 
-(`npx -y gm-plugkit@latest spool` if no `bun`.) Atomic: daemonizes watcher, blocks until `.status.json` heartbeats fresh, returns only on serving (exit 0) or loud timeout. No `&`, no `sleep`, no re-`cat` -- returns, you write to `instruction/` directly. (Already-alive watcher returns at once.)
+(`npx -y gm-plugkit@latest spool` if no `bun`.) Fire-and-forget: spawns the detached daemon and returns immediately (already-alive watcher also returns at once, unchanged) -- it does NOT wait for the watcher to confirm serving. No `&`, no `sleep`, no re-`cat`; write your first verb to `in/` right after it returns. A first-read "file does not exist" on that verb is normal (the just-spawned watcher hasn't noticed the file yet) -- re-Read next message, same as any dead-watcher-adjacent recheck. If you need to actively confirm serving before dispatching (rare), read `.gm/exec-spool/.status.json` yourself and check `ts` freshness.
 
 **Dispatch shape: Write request + Read response, SAME tool-call block.** Never proceed/narrate/begin work before reading the response and following its `instruction` field. First-read "file does not exist" mid-verb = normal, re-Read next message. Never poll with `sleep && ls` -- plugkit is synchronous; missing response = dead watcher (recheck `ts`) or slow verb, never "still processing."