turbollm 1.12.7 → 1.13.0

package/bin/turbollm.mjs

@@ -1,29 +1,29 @@
 #!/usr/bin/env node
-// Hand-written launcher shim — NOT bundled by tsup. It runs before the bundled
-// daemon (dist/cli.js) loads, so it can do two things that must happen before
-// node:sqlite is imported (the bundle hoists that import, emitting an experimental
-// warning that PowerShell renders as a scary red error block on every run):
-//   1. Guard the Node version with a friendly message (node:sqlite needs Node 22.13+ —
-//      that's when node:sqlite became available WITHOUT the --experimental-sqlite flag;
-//      on 22.5.0-22.12.x it's registered only behind that flag, so importing it bare
-//      throws ERR_UNKNOWN_BUILTIN_MODULE: "No such built-in module: node:sqlite"
-//      (GitHub #40) even though `node -v` reports 22.x).
-//   2. Register a 'warning' filter that swallows the node:sqlite experimental notice
-//      while still printing every other warning.
-// Then it hands off to the real CLI via dynamic import (same process; argv intact).
-const [major, minor] = process.versions.node.split('.').map(Number)
-if (major < 22 || (major === 22 && minor < 13)) {
-  process.stderr.write(
-    `TurboLLM requires Node.js 22.13.0 or newer (needs node:sqlite unflagged).\n` +
-      `You are running Node.js ${process.versions.node}.\n` +
-      `Please upgrade: https://nodejs.org\n`,
-  )
-  process.exit(1)
-}
-
-process.on('warning', (w) => {
-  if (w.name === 'ExperimentalWarning' && /SQLite/i.test(w.message)) return
-  process.stderr.write(`${w.stack ?? `${w.name}: ${w.message}`}\n`)
-})
-
-await import('../dist/cli.js')
+// Hand-written launcher shim — NOT bundled by tsup. It runs before the bundled
+// daemon (dist/cli.js) loads, so it can do two things that must happen before
+// node:sqlite is imported (the bundle hoists that import, emitting an experimental
+// warning that PowerShell renders as a scary red error block on every run):
+//   1. Guard the Node version with a friendly message (node:sqlite needs Node 22.13+ —
+//      that's when node:sqlite became available WITHOUT the --experimental-sqlite flag;
+//      on 22.5.0-22.12.x it's registered only behind that flag, so importing it bare
+//      throws ERR_UNKNOWN_BUILTIN_MODULE: "No such built-in module: node:sqlite"
+//      (GitHub #40) even though `node -v` reports 22.x).
+//   2. Register a 'warning' filter that swallows the node:sqlite experimental notice
+//      while still printing every other warning.
+// Then it hands off to the real CLI via dynamic import (same process; argv intact).
+const [major, minor] = process.versions.node.split('.').map(Number)
+if (major < 22 || (major === 22 && minor < 13)) {
+  process.stderr.write(
+    `TurboLLM requires Node.js 22.13.0 or newer (needs node:sqlite unflagged).\n` +
+      `You are running Node.js ${process.versions.node}.\n` +
+      `Please upgrade: https://nodejs.org\n`,
+  )
+  process.exit(1)
+}
+
+process.on('warning', (w) => {
+  if (w.name === 'ExperimentalWarning' && /SQLite/i.test(w.message)) return
+  process.stderr.write(`${w.stack ?? `${w.name}: ${w.message}`}\n`)
+})
+
+await import('../dist/cli.js')

package/dist/{chunk-UXU6FBYT.js → chunk-TIH3B2GZ.js}

@@ -3579,6 +3579,17 @@ var CodeRunManager = class {
     const s = this.sessions.get(sessionId);
     return !!s && (s.active !== null || s.queue.length > 0);
   }
+  /** Is ANY session mid-turn? The session-agnostic form of {@link isActive}, for callers that
+   *  must not disturb the daemon while a Code run is in flight — today the app self-update
+   *  pre-check (spec 29 B.1), which restarts the process and would take a running agent with
+   *  it. Deliberately not derived by iterating session ids at the call site: that would let a
+   *  caller miss a session it didn't know to ask about. */
+  anyActive() {
+    for (const s of this.sessions.values()) {
+      if (s.active !== null || s.queue.length > 0) return true;
+    }
+    return false;
+  }
   /** The turns currently WAITING behind the active turn (not the running one) — the server-side
    *  message queue, surfaced to the UI so its "Queued" chips survive a disconnect. `userMsgId`
    *  (not just index) identifies each entry so a per-chip action (sendNow) can target one