@axiomatic-labs/claudeflow 2.26.24 → 2.26.26

package/lib/install.js

@@ -257,11 +257,11 @@ async function run() {
     fs.rmSync(tmpExtract, { recursive: true, force: true });
   }
 
-  // Kill any running observer daemon so the next request spawns a fresh one
-  // with the updated runtime code. Pre-fix: a running daemon held the old
-  // version in memory until manually killed, causing the bridge to talk to
-  // stale logic (see v2.13.71→v2.13.72 dual-daemon incident).
-  killStaleObserverDaemon(cwd);
+  // install does NOT touch running processes — it only writes template files.
+  // The observer daemon / dev servers are never killed here; a fresh daemon
+  // with the updated runtime code is picked up on the next session, or via the
+  // /claudeflow-observer-reset skill. Killing the daemon on update used to cascade
+  // into tearing down the user's dev servers, so update stays purely a file copy.
 
   // Install analysis tools (ast-grep + Serena MCP)
   installAnalysisTools();
@@ -347,74 +347,6 @@ async function run() {
   showGettingStarted(cwd, cliStatus);
 }
 
-function killStaleObserverDaemon(cwd) {
-  const pidPath = path.join(cwd, '.claudeflow', 'tmp', 'error-observer.pid');
-  if (!fs.existsSync(pidPath)) return;
-  let pid;
-  try {
-    pid = Number(fs.readFileSync(pidPath, 'utf8').trim());
-  } catch {
-    return;
-  }
-  if (!Number.isFinite(pid) || pid <= 1) return;
-  try {
-    // signal 0 = "is this PID alive and ours to signal?"
-    process.kill(pid, 0);
-  } catch {
-    // Not running or not ours. Clean up the stale pidfile and move on.
-    try { fs.unlinkSync(pidPath); } catch {}
-    return;
-  }
-  try {
-    process.kill(pid, 'SIGTERM');
-    ui.success(`Stopped running observer daemon (pid ${pid}) so the update takes effect`);
-  } catch {
-    // Swallow — non-fatal. The user can restart manually if needed.
-  }
-  try { fs.unlinkSync(pidPath); } catch {}
-
-  killStaleBrowserBridge(cwd);
-}
-
-// Clean stale Chrome launch lockfiles after an update. The bridge process
-// itself is ephemeral (inject-and-exit), but `.browser-cdp-<port>.pid` is a
-// "have we already launched Chrome this session" lock used by
-// UserPromptSubmit. If Chrome died but the lockfile survived (crash, kill,
-// stale session), the next UserPromptSubmit sees the lock, decides Chrome
-// is already running, skips the launch — and the bridge never runs again,
-// so injected scripts in any surviving tabs keep posting to the old daemon
-// (which we just killed) until manual recovery.
-function killStaleBrowserBridge(cwd) {
-  const tmpDir = path.join(cwd, '.claudeflow', 'tmp');
-  let entries;
-  try {
-    entries = fs.readdirSync(tmpDir);
-  } catch {
-    return;
-  }
-  const cleaned = [];
-  for (const name of entries) {
-    if (!/^\.browser-cdp-\d+\.pid$/.test(name)) continue;
-    const full = path.join(tmpDir, name);
-    let pid;
-    try {
-      pid = Number(fs.readFileSync(full, 'utf8').trim());
-    } catch {
-      continue;
-    }
-    let alive = false;
-    if (Number.isFinite(pid) && pid > 1) {
-      try { process.kill(pid, 0); alive = true; } catch {}
-    }
-    if (!alive) {
-      try { fs.unlinkSync(full); cleaned.push(name); } catch {}
-    }
-  }
-  if (cleaned.length > 0) {
-    ui.success(`Removed ${cleaned.length} stale Chrome lockfile(s) — next prompt will relaunch the bridge cleanly`);
-  }
-}
-
 function ensureGlobalCli(version) {
   // Returns { available: boolean, autoInstalled: boolean, upgraded: boolean, fromVersion?: string, error?: string }
   // `commandExists('claudeflow')` yields a false positive when install.js runs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiomatic-labs/claudeflow",
-  "version": "2.26.24",
+  "version": "2.26.26",
   "description": "Claudeflow — AI-powered development toolkit for Claude Code. Skills, agents, hooks, and quality gates that ship production apps.",
   "bin": {
     "claudeflow": "./bin/cli.js"