botmux 3.10.0 → 3.23.1

package/scripts/postinstall-bin.mjs

@@ -0,0 +1,388 @@
+#!/usr/bin/env node
+/**
+ * postinstall: point the single global `botmux` launcher at the platform binary.
+ *
+ * WHY THIS EXISTS
+ * The old model was `bin: {botmux: dist/cli.js}` with a `#!/usr/bin/env node`
+ * shebang, so the CLI ran on whatever Node resolved first. With two Node versions
+ * installed, each carries its OWN global botmux and users could not tell which one
+ * `botmux` meant or which one an update touched. The fix: ship the self-contained
+ * Bun single-file executable (its own runtime embedded, no Node needed) via npm
+ * optional platform subpackages, and have exactly ONE launcher point at it.
+ *
+ * npm installs only the subpackage whose `os`/`cpu` match (that is what optional
+ * platform deps do), so we look up whichever one actually landed and write a
+ * launcher that `exec`s its binary.
+ *
+ * ── THE GUARD (do not loosen this) ──────────────────────────────────────────────
+ * We only write the launcher for a REAL global install. Empirically measured what
+ * each package manager exposes to postinstall (not assumed — probed every case):
+ *
+ *   `npm i -g botmux`                    → npm_config_global === "true"
+ *   installed as someone's local dep     → npm_config_global ABSENT
+ *   `pnpm install` INSIDE the botmux repo → npm_config_global ABSENT
+ *   `bun add -g botmux`                  → npm_config_global ABSENT (see below)
+ *
+ * The third case is the dangerous one: a repo-local `pnpm install` DOES run the
+ * root package's postinstall. So a `!== "false"` style check would fire during
+ * ordinary development and rewrite ~/.botmux/bin/botmux — hijacking the global
+ * launcher of whatever fleet shares that HOME (on the dev box that is ~50 live
+ * daemons). Hence the env check stays a STRICT `=== "true"`, and there is a second,
+ * independent bail-out when we can see we are inside the source checkout.
+ *
+ * ⚠️ THE FOURTH CASE IS WHY THE ENV CHECK ALONE IS NOT ENOUGH. Bun does pass a few
+ * npm_* vars to lifecycle scripts — MEASURED with a probe package whose postinstall
+ * dumped its own env, the complete set is:
+ *
+ *   BUN_INSTALL, BUN_WHICH_IGNORE_CWD, npm_config_user_agent, npm_execpath,
+ *   npm_node_execpath
+ *
+ * — but `npm_config_global` is NOT among them, and that is the one this guard read.
+ * So for a perfectly real `bun add -g botmux` the check failed and this script
+ * exited 0 without writing anything. MEASURED end to end: `.bun/bin/` empty, no
+ * launcher, the platform binary sitting in the download cache, i.e. the user had NO
+ * `botmux` command at all. Worse, the obvious workaround did NOT help: `bun pm -g
+ * trust botmux` made bun report `1 script ran` while this script still wrote
+ * nothing, because the env check had already failed.
+ *
+ * ⚠️ TWO SEPARATE LAYERS — do not conflate them. (a) bun BLOCKS the script by
+ * default (`Blocked N postinstalls`); `bun pm trust` lifts that. (b) even once it
+ * runs, this guard killed it. Fixing (b) is what makes `bun pm trust` an actually
+ * working workaround. pnpm 10/11 is a different layer again: `onlyBuiltDependencies`
+ * means the script does not run at all, so this fix alone does not rescue pnpm —
+ * that needs approve-builds/onlyBuiltDependencies or a different mechanism.
+ *
+ * So the global check is: the env says global (npm/yarn), OR THE INSTALL LOCATION
+ * ITSELF says global. The layout list is INLINED in `locationSaysGlobal` below —
+ * see the ⚠️ notes there for why importing the repo's classifier from `dist/` was
+ * dead code in the published package, and why the inlined version is deliberately
+ * stricter on Windows. A source checkout matches no global layout (verified), so
+ * this cannot reopen the repo-local hijack that guard 2 also covers.
+ *
+ * ── FAIL HARD WHEN THERE IS NO BINARY ──────────────────────────────────────────
+ * This used to warn and exit 0, because `bin: {botmux: "dist/cli.js"}` gave every
+ * failure a Node fallback to land on. That fallback is gone (it forced the main
+ * package to depend on node-pty, which has no linux prebuild and so pulled a whole
+ * node-gyp toolchain into every `npm i -g` — an install-time requirement that
+ * simply is not met on many machines). With no fallback, exiting 0 without a
+ * launcher would leave the user with a `botmux` command that does not exist, and
+ * they would find out later with a confusing error. So: no binary → fail the
+ * install, loudly, with the reason.
+ *
+ * The GUARD cases below still exit 0 silently — those are not failures, they are
+ * "this is not a global install, there is nothing to do".
+ */
+
+import { existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync, chmodSync, renameSync, unlinkSync, realpathSync, statSync } from 'node:fs';
+import { dirname, join, basename } from 'node:path';
+import { homedir } from 'node:os';
+import { createRequire } from 'node:module';
+import { spawnSync } from 'node:child_process';
+import { fileURLToPath } from 'node:url';
+
+/** Abort the install with a reason. There is no Node fallback any more (see header). */
+function fail(reason, hint) {
+  console.error(`[botmux] ${reason}`);
+  if (hint) console.error(`[botmux] ${hint}`);
+  process.exit(1);
+}
+
+/**
+ * Are we on a musl libc distro (Alpine and most slim Docker images)?
+ *
+ * WHY THIS CHECK EXISTS: npm selects platform subpackages by `os`/`cpu`, and both
+ * are identical for glibc and musl (`linux`/`x64`), so on Alpine npm happily
+ * installs `botmux-linux-x64` — a glibc-linked binary that dies at exec time with a
+ * loader error naming no cause. Without this check we would write a launcher
+ * pointing at a binary that cannot run: the worst outcome, because the install
+ * "succeeds" and the failure surfaces much later.
+ *
+ * (npm does support a `libc` field — undocumented in `npm help package-json` but
+ * live in the wild, e.g. `@napi-rs/canvas-linux-x64-musl` publishes `libc: musl`.
+ * Once botmux ships musl subpackages declaring it, npm will pick the right one on
+ * its own and this guard becomes a diagnostic for "the musl package failed to
+ * install" rather than "musl is unsupported".)
+ *
+ * Detection order is authoritative-first, and deliberately conservative: only claim
+ * musl when positively observed, so a glibc box is never blocked by a false
+ * positive.
+ *
+ * MEASURED on node:22-alpine: `process.report.getReport().header` has 23 keys and
+ * carries NEITHER `glibcVersionRuntime` NOR any musl key. So the report is only
+ * useful as a NEGATIVE signal ("glibcVersionRuntime present ⇒ definitely glibc,
+ * stop"); on musl it tells us nothing and the loader probe below is what actually
+ * decides. Do not add a `header.musl` branch back — Node does not publish one.
+ */
+function isMuslLinux() {
+  if (process.platform !== 'linux') return false;
+  // Negative signal only (see above): a reported glibc runtime settles it.
+  try {
+    if (process.report?.getReport?.()?.header?.glibcVersionRuntime) return false;
+  } catch { /* report unavailable; fall through to filesystem probes */ }
+  // The ld-musl loader is the direct positive evidence.
+  for (const dir of ['/lib', '/usr/lib']) {
+    try {
+      if (readdirSync(dir).some(f => f.startsWith('ld-musl-'))) return true;
+    } catch { /* unreadable; try the next probe */ }
+  }
+  // Alpine's marker file, for images that moved the loader.
+  try {
+    if (existsSync('/etc/alpine-release')) return true;
+  } catch { /* ignore */ }
+  return false;
+}
+
+// ── Guard 1: only a real global install ─────────────────────────────────────────
+// Two independent positive signals (see header). The env check is unchanged and
+// still strict; the location check is what makes `bun add -g` / `pnpm add -g` work,
+// since those provide no npm_config_* at all.
+const here = dirname(fileURLToPath(import.meta.url));
+const pkgRoot = dirname(here); // scripts/ -> package root
+
+/**
+ * Does the install LOCATION say this is a package-manager-owned global tree?
+ *
+ * ⚠️ WHY THIS IS INLINED INSTEAD OF IMPORTING THE REPO'S CLASSIFIER. The first
+ * version did `await import('./dist/utils/global-install.js')` to reuse
+ * `detectGlobalInstallManager`. That was DEAD CODE in the published package: #1115
+ * removed `dist/` from `package.json` `files`, so the import always ENOENTs, the
+ * catch returned false, and the guard silently fell back to env-only — leaving
+ * `bun add -g botmux` exactly as broken as before. MEASURED, not reasoned:
+ *
+ *   git archive origin/master | tar x && npm pack
+ *   tar tzf botmux-*.tgz | grep -c '^package/dist/'    → 0
+ *
+ * and end to end, a real `bun add -g <that tarball>` then running this script the
+ * way bun does: exit 0, no launcher. This file is a standalone script with no build
+ * step, and neither `dist/` nor `src/` is published, so being SELF-CONTAINED is its
+ * natural form — inlining is not a compromise here.
+ *
+ * ⚠️ AND IT IS DELIBERATELY STRICTER THAN `detectGlobalInstallManager`. That
+ * function ends with `platform === 'win32' ? 'npm' : 'unknown'`, so on Windows it
+ * cannot tell a global install from a LOCAL dependency — MEASURED:
+ *
+ *   detectGlobalInstallManager('C:/projects/myapp/node_modules/botmux', 'win32') → 'npm'
+ *
+ * Harmless where it is used today (a wrong `npm i -g` merely reinstalls), but in
+ * THIS file it would mean a Windows local dependency repoints the shared
+ * `~/.botmux/bin/botmux` — the exact hijack guard 1 exists to prevent. So the list
+ * below recognises only KNOWN GLOBAL layouts and has no platform fallback. Windows
+ * npm globals are unaffected: they arrive with `npm_config_global=true` and never
+ * reach this check.
+ *
+ * The layout patterns mirror `detectGlobalInstallManager`'s; a source guard in
+ * test/npm-binary-distribution.test.ts pins the two in agreement over a matrix of
+ * real global paths, so the duplication cannot drift unnoticed.
+ */
+function locationSaysGlobal(root) {
+  const r = root.replace(/\\/g, '/').replace(/\/+$/, '').toLowerCase();
+  // Every global layout below ends at the main package; anything else is not ours.
+  if (!r.endsWith('/node_modules/botmux')) return false;
+  return r.endsWith('/lib/node_modules/botmux')                    // npm, POSIX
+    || r.includes('/.bun/install/global/node_modules/botmux')      // bun
+    || r.includes('/bun/install/global/node_modules/botmux')       // bun, custom BUN_INSTALL
+    || r.includes('/.pnpm/')                                       // pnpm virtual store
+    || /\/pnpm\/global\/[^/]+\/node_modules\/botmux$/.test(r)      // pnpm 9 global
+    || /\/pnpm\/global\/v\d+\/[^/]+\/node_modules\/botmux$/.test(r) // pnpm 11 global
+    || /\/pnpm\/store\/v\d+\/links\/@\/botmux\//.test(r);          // pnpm 11 store links
+}
+
+if (process.env.npm_config_global !== 'true' && !locationSaysGlobal(pkgRoot)) {
+  // Silent: this is the overwhelmingly common case (dev installs, transitive
+  // installs). Noise here would appear on every `bun install` in the repo.
+  process.exit(0);
+}
+
+// ── Guard 2: never act from inside the source checkout ──────────────────────────
+// Defence in depth for guard 1. If the package directory we are running from is a
+// git checkout of botmux (has .git and src/), this is a developer environment, not
+// an installed package — the launcher must not be repointed.
+if (existsSync(join(pkgRoot, '.git')) && existsSync(join(pkgRoot, 'src'))) {
+  process.exit(0);
+}
+
+// ── musl (Alpine): select the -musl subpackage ──────────────────────────────────
+// This used to be a hard FAIL ("botmux's prebuilt binaries are glibc-linked and
+// cannot run on musl"), which was true while only glibc binaries shipped. musl
+// binaries now exist, so that message became a lie and the guard would have blocked
+// the very platform we just added support for. The #1047 comment predicted this:
+// "Once botmux ships musl subpackages declaring it, npm will pick the right one on
+// its own and this guard becomes a diagnostic".
+//
+// npm does the actual selection via each subpackage's `libc` field, so on Alpine it
+// installs `botmux-linux-<arch>-musl`. We only have to look for the same name — the
+// detection below is what makes the lookup agree with what npm installed.
+const MUSL = isMuslLinux();
+const SUBPACKAGE = `botmux-${process.platform}-${process.arch}${MUSL ? '-musl' : ''}`;
+
+// ── Locate the platform binary ─────────────────────────────────────────────────
+// Resolve through Node's own resolver rather than guessing at node_modules layout:
+// npm, pnpm, and yarn lay out global installs differently (nested, hoisted,
+// symlinked store), and hand-built paths break on at least one of them. We resolve
+// the subpackage's package.json (an explicit export path that always exists) and
+// take its directory.
+let binary;
+try {
+  const require = createRequire(join(pkgRoot, 'package.json'));
+  const manifest = require.resolve(`${SUBPACKAGE}/package.json`);
+  binary = join(dirname(manifest), 'botmux');
+} catch {
+  fail(
+    `no prebuilt binary package for ${process.platform}-${process.arch} (${SUBPACKAGE}).`,
+    // Do NOT say "it still works via Node" — that fallback is gone (see header).
+    // On Windows the daemon cannot run natively at all (PTY/tmux/Unix signals), so
+    // WSL is the real answer there, not a Node install.
+    'Supported: linux-x64, linux-arm64, darwin-x64, darwin-arm64. '
+      + 'On Windows, run botmux inside WSL2 (it reports as linux and is fully supported).',
+  );
+}
+
+if (!existsSync(binary)) {
+  fail(
+    `${SUBPACKAGE} is installed but its binary is missing (${binary}).`,
+    'Try reinstalling: npm i -g botmux --force',
+  );
+}
+
+// The binary must be executable or the launcher's `exec` fails at RUN time — long
+// after install, with a confusing error. npm preserves the exec bit from the
+// tarball, but a repacked/mirrored registry may not, so repair it here rather than
+// trusting it.
+try {
+  const mode = statSync(binary).mode;
+  if ((mode & 0o111) === 0) chmodSync(binary, 0o755);
+} catch { /* best effort; the exec below will surface a real problem */ }
+
+// Do not activate a platform package merely because npm selected the right
+// os/cpu/libc tuple. That metadata cannot express a glibc symbol-version floor:
+// a binary built on Ubuntu 24.04 is still "linux-x64 + glibc", yet its embedded
+// node-pty native may require GLIBC_2.34 and die on Debian 10 (glibc 2.28).
+//
+// Probe the exact candidate before touching the shared launcher. `--version`
+// loads the complete compiled module graph (including node-pty), but starts no
+// daemon and writes no bot data. A failed global npm update can then roll back
+// while every already-running daemon and every shell keeps using the old launcher.
+const probe = spawnSync(binary, ['--version'], {
+  encoding: 'utf-8',
+  timeout: 30_000,
+  env: { ...process.env, BOTMUX_INSTALL_PROBE: '1' },
+});
+if (probe.error || probe.status !== 0) {
+  const raw = probe.error?.message || probe.stderr || probe.stdout || `exit ${probe.status ?? probe.signal ?? 'unknown'}`;
+  const detail = String(raw).trim().split('\n').slice(0, 8).join(' | ');
+  fail(
+    `${SUBPACKAGE} cannot run on this host; the existing botmux launcher was not changed.`,
+    `${detail || 'candidate probe failed'}. Install a compatible release or upgrade the host OS; `
+      + 'do not replace glibc in-place on a live machine.',
+  );
+}
+
+// ── Write the single launcher ──────────────────────────────────────────────────
+// Same path + same atomic-write discipline as the daemon and `bun run use:here` use
+// (src/daemon.ts, scripts/claim-botmux-bin.mjs), because concurrent CLI sessions
+// `exec` this file constantly and a half-written script breaks every `botmux send`
+// in flight. Three parts, none optional: realpath first (else we rename over a
+// symlink's own inode), a unique temp name, and an explicit chmod (creation mode is
+// masked by umask — under umask 077, 0o755 lands as 0o700).
+const binDir = join(homedir(), '.botmux', 'bin');
+const launcher = join(binDir, 'botmux');
+// `exec` replaces the shell process, so signals/exit codes pass straight through
+// to the binary. No `node` anywhere in this launcher — that is the entire point.
+const content = `#!/bin/sh\nexec "${binary}" "$@"\n`;
+
+function atomicWrite(file, data, mode) {
+  let target = file;
+  try { target = realpathSync(file); }
+  catch {
+    try { target = join(realpathSync(dirname(file)), basename(file)); }
+    catch { /* parent missing too; keep as-is */ }
+  }
+  const tmp = `${target}.${process.pid}.${Math.random().toString(16).slice(2, 10)}.tmp`;
+  try {
+    writeFileSync(tmp, data, { mode });
+    chmodSync(tmp, mode);
+    renameSync(tmp, target);
+  } catch (err) {
+    try { unlinkSync(tmp); } catch { /* may not exist */ }
+    throw err;
+  }
+}
+
+try {
+  mkdirSync(binDir, { recursive: true });
+  let existing = '';
+  try { existing = readFileSync(launcher, 'utf-8'); } catch { /* first install */ }
+  if (existing !== content) {
+    atomicWrite(launcher, content, 0o755);
+  }
+  console.log(`[botmux] launcher → ${binary}`);
+} catch (err) {
+  fail(
+    `could not write the launcher at ${launcher}: ${err && err.message ? err.message : String(err)}`,
+    // NOT "npm's own shim still works" — `bin` was removed with the Node fallback,
+    // so there is no other `botmux` on PATH. Give the user something they can act on.
+    `Fix the permissions on ${binDir} and retry, or set BOTMUX_INSTALL_DIR and use the `
+      + 'standalone installer: curl -fsSL https://raw.githubusercontent.com/deepcoldy/botmux/master/install.sh | sh',
+  );
+}
+
+// ── PATH: write it, don't just suggest it ─────────────────────────────────────
+// This used to only PRINT `echo 'export PATH=…' >> ~/.profile`. Two problems:
+// the user had to act on it, and for zsh users the suggested file is WRONG —
+// zsh never reads ~/.profile (measured), so following the hint verbatim left
+// `botmux` still not found. There is no `bin` field any more, so PATH is the
+// only way this launcher becomes a command; we now write the right startup file
+// for the user's actual shell (bash/zsh/fish/other) and tell them what we did.
+//
+// ⚠️ DO NOT GATE THIS ON `process.env.PATH`. It used to be wrapped in
+// `if (!process.env.PATH.split(':').includes(binDir))`, which asks "is binDir on
+// the PATH of the process running the install?" — the wrong question. What decides
+// whether `botmux` works is whether the user's FUTURE shells get it, i.e. whether a
+// startup file says so. The two come apart whenever the installing shell has binDir
+// on PATH transiently, and botmux itself creates that situation: the daemon
+// prepends `~/.botmux/bin` to every CLI session's PATH (five `prependBotmuxBin`
+// call sites in worker.ts / worker-pool.ts). So `npm i -g botmux` run from inside a
+// botmux session — or any shell that merely exported the dir — wrote NO startup
+// file, printed NO hint, and exited 0; the next terminal then had no `botmux` at
+// all, because there is no `bin` field to fall back on. MEASURED with the real
+// script against an isolated HOME, changing only PATH:
+//   PATH without binDir → writes ~/.zshenv + "open a new terminal" hint
+//   PATH with    binDir → zero files, zero output, exit 0   ← the reported bug
+// `ensurePathEntry` already asks the right question per file (`fileAlreadyHasEntry`,
+// which also recognises a line the user wrote by hand) and reports those as
+// `skipped`, so this outer check was redundant as well as wrong.
+//
+// ⚠️ FAIL-SOFT, and never `fail()`: the launcher is already installed and working
+// at this point, so a PATH edit that cannot happen must degrade to the printed
+// hint — not abort a successful install. That includes the sibling module simply
+// not being there: it ships via package.json `files`, and if a future edit drops
+// it (or a mirror repacks the tarball without it) the import throws. Guarding it
+// keeps `npm i -g botmux` succeeding either way.
+{
+  let ensurePathEntry = null;
+  try {
+    ({ ensurePathEntry } = await import('./install-path-entry.mjs'));
+  } catch (err) {
+    console.error(`[botmux] PATH helper unavailable (${err && err.message ? err.message : String(err)})`);
+  }
+  let written = [], skipped = [];
+  if (ensurePathEntry) {
+    try {
+      const r = ensurePathEntry({ installDir: binDir });
+      ({ written, skipped } = r);
+      for (const f of written) console.log(`[botmux] added ${binDir} to PATH in ${f} (${r.shell})`);
+      for (const f of skipped) console.log(`[botmux] ${f} already puts ${binDir} on PATH`);
+      for (const { file, error } of r.failed) console.error(`[botmux] could not update ${file}: ${error}`);
+    } catch (err) {
+      console.error(`[botmux] could not update your shell startup file: ${err && err.message ? err.message : String(err)}`);
+    }
+  }
+  if (written.length > 0) {
+    console.log('[botmux] open a new terminal (or re-source that file) and `botmux` will be on PATH');
+  } else if (skipped.length === 0) {
+    // Nothing written and nothing already present — fall back to telling them.
+    // Deliberately not naming a specific file here: the correct one depends on
+    // the shell, and naming the wrong one is what caused the original bug.
+    console.log(`[botmux] add ${binDir} to your PATH so this launcher is the \`botmux\` your shell finds`);
+  }
+}

package/dist/.runtime-build-id

@@ -1 +0,0 @@
-bc24a7e04925bf39c43c6baba34729686bfd5f776882ccda5ff26e978e706f89

package/dist/adapters/adopt-route.d.ts

@@ -1,63 +0,0 @@
-/**
- * adopt-route.ts
- *
- * 为没有 BOTMUX_* 环境变量的"孤立" Claude 进程（即通过 /adopt 接管的外部 CLI）
- * 提供 askUserQuestion hook 的路由解析逻辑。
- *
- * 通过以下步骤确定目标 Lark 会话：
- *   1. 收集 hook 进程的祖先 PID 链
- *   2. 遍历在线 daemon，查询每个 daemon 是否有以某祖先 PID 启动的 adopt 会话
- *   3. 首个命中即返回路由信息
- */
-/** 从 daemon 取回的 adopt 会话路由信息 */
-export interface AdoptRoute {
-    sessionId: string;
-    chatId: string;
-    larkAppId: string;
-    rootMessageId: string;
-}
-/**
- * 沿进程祖先链向上收集 PID（不含 startPid 自己）。
- *
- * @param startPid    起始进程 PID（自身不包含在结果中）
- * @param readParent  注入式父 PID 读取函数（默认使用 /proc 或 ps）
- * @param maxDepth    最大深度，防止意外无限循环（默认 40）
- * @returns           祖先 PID 数组，从最近父进程到最远祖先
- */
-export declare function getAncestorPids(startPid: number, readParent?: (pid: number) => number | null, maxDepth?: number): number[];
-/**
- * 查询某个 daemon 是否有以指定 PID 启动的活跃 adopt 会话。
- *
- * GET http://127.0.0.1:<ipcPort>/api/adopt-session/<pid>
- *   200 → 解析 AdoptRoute；其它状态码或异常 → null（不抛）。
- * 超时：2 秒（AbortController）。
- */
-export declare function queryAdoptSession(ipcPort: number, pid: number): Promise<AdoptRoute | null>;
-/**
- * 通过祖先 PID 匹配在线 adopt 会话。
- *
- * **并发 + 全局 budget 封顶**：候选 = daemon 列表序 × 祖先链序（由近及远）逐个编号；
- * 全部并发查询（每请求各自带 2s 超时），整体不超过 `budgetMs`。命中按候选 index 取
- * 最小，保持确定性。
- *
- * 为何要全局 budget：runHook 在缺 BOTMUX_* 时同步 await 本函数，而全局 hook 会覆盖
- * 非 botmux 的 Claude 会话；若某 daemon still-online 但 IPC 不响应，顺序 await 会
- * `祖先数 × 2s × daemon 数` 线性叠加（可达几十秒），把真·非 botmux 的 ask 卡死。
- * 并发让总耗时收敛到单请求量级，budget 再封顶，保证快速 passthrough。
- *
- * @param deps.startPid      hook 进程自身的 PID
- * @param deps.listDaemons   列出在线 daemon（ipcPort）
- * @param deps.queryDaemon   查询某 daemon 是否有该 pid 的活跃 adopt 会话
- * @param deps.getAncestors  取祖先 PID（默认使用 getAncestorPids）
- * @param deps.budgetMs      整体耗时上限（默认 1500ms；可注入便于测试）
- */
-export declare function resolveAdoptRoute(deps: {
-    startPid: number;
-    listDaemons: () => Array<{
-        ipcPort: number;
-    }>;
-    queryDaemon: (ipcPort: number, pid: number) => Promise<AdoptRoute | null>;
-    getAncestors?: (startPid: number) => number[];
-    budgetMs?: number;
-}): Promise<AdoptRoute | null>;
-//# sourceMappingURL=adopt-route.d.ts.map

package/dist/adapters/adopt-route.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"adopt-route.d.ts","sourceRoot":"","sources":["../../src/adapters/adopt-route.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAQH,gCAAgC;AAChC,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAC;IAClB,MAAM,EAAE,MAAM,CAAC;IACf,SAAS,EAAE,MAAM,CAAC;IAClB,aAAa,EAAE,MAAM,CAAC;CACvB;AA8CD;;;;;;;GAOG;AACH,wBAAgB,eAAe,CAC7B,QAAQ,EAAE,MAAM,EAChB,UAAU,CAAC,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,MAAM,GAAG,IAAI,EAC3C,QAAQ,CAAC,EAAE,MAAM,GAChB,MAAM,EAAE,CAiBV;AAID;;;;;;GAMG;AACH,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,MAAM,EACf,GAAG,EAAE,MAAM,GACV,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CAiC5B;AAID;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAsB,iBAAiB,CAAC,IAAI,EAAE;IAC5C,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC9C,WAAW,EAAE,CAAC,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CAAC;IAC1E,YAAY,CAAC,EAAE,CAAC,QAAQ,EAAE,MAAM,KAAK,MAAM,EAAE,CAAC;IAC9C,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB,GAAG,OAAO,CAAC,UAAU,GAAG,IAAI,CAAC,CA+C7B"}

package/dist/adapters/adopt-route.js

@@ -1,196 +0,0 @@
-/**
- * adopt-route.ts
- *
- * 为没有 BOTMUX_* 环境变量的"孤立" Claude 进程（即通过 /adopt 接管的外部 CLI）
- * 提供 askUserQuestion hook 的路由解析逻辑。
- *
- * 通过以下步骤确定目标 Lark 会话：
- *   1. 收集 hook 进程的祖先 PID 链
- *   2. 遍历在线 daemon，查询每个 daemon 是否有以某祖先 PID 启动的 adopt 会话
- *   3. 首个命中即返回路由信息
- */
-import { execFileSync } from 'node:child_process';
-import { readFileSync } from 'node:fs';
-import { fetchDaemonIpc } from '../core/daemon-ipc-auth.js';
-// ── 祖先 PID 收集 ──────────────────────────────────────────────────────────────
-/**
- * 读取某进程的父 PID。
- *
- * 默认实现：
- *   1. 优先从 /proc/<pid>/stat 读取（Linux），第 4 字段（0-based）是 ppid。
- *      注意 stat 第 2 字段 comm 可以含括号和空格，所以从最后一个 `)` 之后的子串解析。
- *   2. 失败时回退到 `ps -o ppid= -p <pid>`（macOS/Linux 通用）。
- *
- * 失败/进程不存在 → 返回 null。
- */
-function defaultReadParent(pid) {
-    // 先尝试 /proc（Linux 最快）
-    try {
-        const stat = readFileSync(`/proc/${pid}/stat`, 'utf-8');
-        // stat 格式: "<pid> (<comm>) <state> <ppid> ..."
-        // comm 字段可能含空格和括号，取最后一个 ')' 之后的部分
-        const lastParen = stat.lastIndexOf(')');
-        if (lastParen === -1)
-            throw new Error('unexpected /proc stat format');
-        const tail = stat.slice(lastParen + 1).trim();
-        // tail: "<state> <ppid> ..."
-        const parts = tail.split(' ');
-        // parts[0] = state, parts[1] = ppid
-        const ppid = parseInt(parts[1], 10);
-        if (Number.isInteger(ppid) && ppid > 0)
-            return ppid;
-    }
-    catch {
-        // /proc 不可用或解析失败，回退到 ps
-    }
-    // 回退到 ps（macOS / 无 /proc 的 Linux）
-    try {
-        const out = execFileSync('ps', ['-o', 'ppid=', '-p', String(pid)], {
-            encoding: 'utf-8',
-        });
-        const ppid = parseInt(out.trim(), 10);
-        if (Number.isInteger(ppid) && ppid > 0)
-            return ppid;
-    }
-    catch {
-        // 进程不存在或 ps 调用失败
-    }
-    return null;
-}
-/**
- * 沿进程祖先链向上收集 PID（不含 startPid 自己）。
- *
- * @param startPid    起始进程 PID（自身不包含在结果中）
- * @param readParent  注入式父 PID 读取函数（默认使用 /proc 或 ps）
- * @param maxDepth    最大深度，防止意外无限循环（默认 40）
- * @returns           祖先 PID 数组，从最近父进程到最远祖先
- */
-export function getAncestorPids(startPid, readParent, maxDepth) {
-    const reader = readParent ?? defaultReadParent;
-    const depth = maxDepth ?? 40;
-    const ancestors = [];
-    const visited = new Set([startPid]);
-    let current = startPid;
-    for (let i = 0; i < depth; i++) {
-        const parent = reader(current);
-        if (parent === null || parent <= 1)
-            break; // 到 init 或读不到，停止
-        if (visited.has(parent))
-            break; // 防环
-        visited.add(parent);
-        ancestors.push(parent);
-        current = parent;
-    }
-    return ancestors;
-}
-// ── Daemon 查询辅助 ─────────────────────────────────────────────────────────────
-/**
- * 查询某个 daemon 是否有以指定 PID 启动的活跃 adopt 会话。
- *
- * GET http://127.0.0.1:<ipcPort>/api/adopt-session/<pid>
- *   200 → 解析 AdoptRoute；其它状态码或异常 → null（不抛）。
- * 超时：2 秒（AbortController）。
- */
-export async function queryAdoptSession(ipcPort, pid) {
-    const controller = new AbortController();
-    const timer = setTimeout(() => controller.abort(), 2000);
-    try {
-        const res = await fetchDaemonIpc(ipcPort, `/api/adopt-session/${pid}`, { signal: controller.signal });
-        if (!res.ok)
-            return null;
-        const body = (await res.json());
-        if (!body || typeof body !== 'object')
-            return null;
-        const b = body;
-        if (typeof b.sessionId !== 'string' ||
-            typeof b.chatId !== 'string' ||
-            typeof b.larkAppId !== 'string' ||
-            typeof b.rootMessageId !== 'string') {
-            return null;
-        }
-        return {
-            sessionId: b.sessionId,
-            chatId: b.chatId,
-            larkAppId: b.larkAppId,
-            rootMessageId: b.rootMessageId,
-        };
-    }
-    catch {
-        // 超时、网络错误、JSON 解析失败等 → null
-        return null;
-    }
-    finally {
-        clearTimeout(timer);
-    }
-}
-// ── 主逻辑 ─────────────────────────────────────────────────────────────────────
-/**
- * 通过祖先 PID 匹配在线 adopt 会话。
- *
- * **并发 + 全局 budget 封顶**：候选 = daemon 列表序 × 祖先链序（由近及远）逐个编号；
- * 全部并发查询（每请求各自带 2s 超时），整体不超过 `budgetMs`。命中按候选 index 取
- * 最小，保持确定性。
- *
- * 为何要全局 budget：runHook 在缺 BOTMUX_* 时同步 await 本函数，而全局 hook 会覆盖
- * 非 botmux 的 Claude 会话；若某 daemon still-online 但 IPC 不响应，顺序 await 会
- * `祖先数 × 2s × daemon 数` 线性叠加（可达几十秒），把真·非 botmux 的 ask 卡死。
- * 并发让总耗时收敛到单请求量级，budget 再封顶，保证快速 passthrough。
- *
- * @param deps.startPid      hook 进程自身的 PID
- * @param deps.listDaemons   列出在线 daemon（ipcPort）
- * @param deps.queryDaemon   查询某 daemon 是否有该 pid 的活跃 adopt 会话
- * @param deps.getAncestors  取祖先 PID（默认使用 getAncestorPids）
- * @param deps.budgetMs      整体耗时上限（默认 1500ms；可注入便于测试）
- */
-export async function resolveAdoptRoute(deps) {
-    const { startPid, listDaemons, queryDaemon } = deps;
-    const getAncestors = deps.getAncestors ?? ((pid) => getAncestorPids(pid));
-    const budgetMs = deps.budgetMs ?? 1500;
-    const ancestors = getAncestors(startPid);
-    if (ancestors.length === 0)
-        return null;
-    const daemons = listDaemons();
-    if (daemons.length === 0)
-        return null;
-    // 候选编号：daemon 列表序 × 祖先链序（由近及远），index 决定确定性优先级。
-    const candidates = [];
-    let idx = 0;
-    for (const daemon of daemons) {
-        for (const pid of ancestors) {
-            candidates.push({ index: idx++, ipcPort: daemon.ipcPort, pid });
-        }
-    }
-    // 并发发起全部查询，命中按 index 记入 hits；整体被 budget 封顶。
-    const hits = new Map();
-    const queries = candidates.map(async (c) => {
-        const route = await queryDaemon(c.ipcPort, c.pid);
-        if (route)
-            hits.set(c.index, route);
-    });
-    let timer;
-    const budget = new Promise((resolve) => {
-        timer = setTimeout(resolve, budgetMs);
-        timer.unref?.();
-    });
-    try {
-        await Promise.race([Promise.allSettled(queries), budget]);
-    }
-    finally {
-        if (timer)
-            clearTimeout(timer);
-    }
-    // 在「budget 内已 settle 的命中」里按候选 index 升序取最早的一个（确定性）。
-    let best = null;
-    let bestIdx = Infinity;
-    for (const [i, route] of hits) {
-        if (i < bestIdx) {
-            bestIdx = i;
-            best = route;
-        }
-    }
-    if (best && process.env.BOTMUX_HOOK_DEBUG === '1') {
-        process.stderr.write(`[adopt-route] matched candidate#${bestIdx} session=${best.sessionId}\n`);
-    }
-    return best;
-}
-//# sourceMappingURL=adopt-route.js.map

package/dist/adapters/adopt-route.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"adopt-route.js","sourceRoot":"","sources":["../../src/adapters/adopt-route.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAClD,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAY5D,8EAA8E;AAE9E;;;;;;;;;GASG;AACH,SAAS,iBAAiB,CAAC,GAAW;IACpC,sBAAsB;IACtB,IAAI,CAAC;QACH,MAAM,IAAI,GAAG,YAAY,CAAC,SAAS,GAAG,OAAO,EAAE,OAAO,CAAC,CAAC;QACxD,+CAA+C;QAC/C,kCAAkC;QAClC,MAAM,SAAS,GAAG,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QACxC,IAAI,SAAS,KAAK,CAAC,CAAC;YAAE,MAAM,IAAI,KAAK,CAAC,8BAA8B,CAAC,CAAC;QACtE,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,SAAS,GAAG,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QAC9C,6BAA6B;QAC7B,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;QAC9B,oCAAoC;QACpC,MAAM,IAAI,GAAG,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;QACpC,IAAI,MAAM,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC;YAAE,OAAO,IAAI,CAAC;IACtD,CAAC;IAAC,MAAM,CAAC;QACP,wBAAwB;IAC1B,CAAC;IAED,kCAAkC;IAClC,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,YAAY,CAAC,IAAI,EAAE,CAAC,IAAI,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,CAAC,GAAG,CAAC,CAAC,EAAE;YACjE,QAAQ,EAAE,OAAO;SAClB,CAAC,CAAC;QACH,MAAM,IAAI,GAAG,QAAQ,CAAC,GAAG,CAAC,IAAI,EAAE,EAAE,EAAE,CAAC,CAAC;QACtC,IAAI,MAAM,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,IAAI,GAAG,CAAC;YAAE,OAAO,IAAI,CAAC;IACtD,CAAC;IAAC,MAAM,CAAC;QACP,iBAAiB;IACnB,CAAC;IAED,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,eAAe,CAC7B,QAAgB,EAChB,UAA2C,EAC3C,QAAiB;IAEjB,MAAM,MAAM,GAAG,UAAU,IAAI,iBAAiB,CAAC;IAC/C,MAAM,KAAK,GAAG,QAAQ,IAAI,EAAE,CAAC;IAC7B,MAAM,SAAS,GAAa,EAAE,CAAC;IAC/B,MAAM,OAAO,GAAG,IAAI,GAAG,CAAS,CAAC,QAAQ,CAAC,CAAC,CAAC;IAE5C,IAAI,OAAO,GAAG,QAAQ,CAAC;IACvB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC;QAC/B,MAAM,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,CAAC;QAC/B,IAAI,MAAM,KAAK,IAAI,IAAI,MAAM,IAAI,CAAC;YAAE,MAAM,CAAE,iBAAiB;QAC7D,IAAI,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC;YAAE,MAAM,CAAa,KAAK;QACjD,OAAO,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;QACpB,SAAS,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QACvB,OAAO,GAAG,MAAM,CAAC;IACnB,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC;AAED,+EAA+E;AAE/E;;;;;;GAMG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CACrC,OAAe,EACf,GAAW;IAEX,MAAM,UAAU,GAAG,IAAI,eAAe,EAAE,CAAC;IACzC,MAAM,KAAK,GAAG,UAAU,CAAC,GAAG,EAAE,CAAC,UAAU,CAAC,KAAK,EAAE,EAAE,IAAI,CAAC,CAAC;IACzD,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,MAAM,cAAc,CAC9B,OAAO,EACP,sBAAsB,GAAG,EAAE,EAC3B,EAAE,MAAM,EAAE,UAAU,CAAC,MAAM,EAAE,CAC9B,CAAC;QACF,IAAI,CAAC,GAAG,CAAC,EAAE;YAAE,OAAO,IAAI,CAAC;QACzB,MAAM,IAAI,GAAG,CAAC,MAAM,GAAG,CAAC,IAAI,EAAE,CAAY,CAAC;QAC3C,IAAI,CAAC,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ;YAAE,OAAO,IAAI,CAAC;QACnD,MAAM,CAAC,GAAG,IAA+B,CAAC;QAC1C,IACE,OAAO,CAAC,CAAC,SAAS,KAAK,QAAQ;YAC/B,OAAO,CAAC,CAAC,MAAM,KAAK,QAAQ;YAC5B,OAAO,CAAC,CAAC,SAAS,KAAK,QAAQ;YAC/B,OAAO,CAAC,CAAC,aAAa,KAAK,QAAQ,EACnC,CAAC;YACD,OAAO,IAAI,CAAC;QACd,CAAC;QACD,OAAO;YACL,SAAS,EAAE,CAAC,CAAC,SAAS;YACtB,MAAM,EAAE,CAAC,CAAC,MAAM;YAChB,SAAS,EAAE,CAAC,CAAC,SAAS;YACtB,aAAa,EAAE,CAAC,CAAC,aAAa;SAC/B,CAAC;IACJ,CAAC;IAAC,MAAM,CAAC;QACP,4BAA4B;QAC5B,OAAO,IAAI,CAAC;IACd,CAAC;YAAS,CAAC;QACT,YAAY,CAAC,KAAK,CAAC,CAAC;IACtB,CAAC;AACH,CAAC;AAED,+EAA+E;AAE/E;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,IAMvC;IACC,MAAM,EAAE,QAAQ,EAAE,WAAW,EAAE,WAAW,EAAE,GAAG,IAAI,CAAC;IACpD,MAAM,YAAY,GAAG,IAAI,CAAC,YAAY,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,eAAe,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1E,MAAM,QAAQ,GAAG,IAAI,CAAC,QAAQ,IAAI,IAAI,CAAC;IACvC,MAAM,SAAS,GAAG,YAAY,CAAC,QAAQ,CAAC,CAAC;IACzC,IAAI,SAAS,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IAExC,MAAM,OAAO,GAAG,WAAW,EAAE,CAAC;IAC9B,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,IAAI,CAAC;IAEtC,+CAA+C;IAC/C,MAAM,UAAU,GAA2D,EAAE,CAAC;IAC9E,IAAI,GAAG,GAAG,CAAC,CAAC;IACZ,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;QAC7B,KAAK,MAAM,GAAG,IAAI,SAAS,EAAE,CAAC;YAC5B,UAAU,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,GAAG,EAAE,EAAE,OAAO,EAAE,MAAM,CAAC,OAAO,EAAE,GAAG,EAAE,CAAC,CAAC;QAClE,CAAC;IACH,CAAC;IAED,4CAA4C;IAC5C,MAAM,IAAI,GAAG,IAAI,GAAG,EAAsB,CAAC;IAC3C,MAAM,OAAO,GAAG,UAAU,CAAC,GAAG,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE;QACzC,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC;QAClD,IAAI,KAAK;YAAE,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,KAAK,EAAE,KAAK,CAAC,CAAC;IACtC,CAAC,CAAC,CAAC;IAEH,IAAI,KAAgD,CAAC;IACrD,MAAM,MAAM,GAAG,IAAI,OAAO,CAAO,CAAC,OAAO,EAAE,EAAE;QAC3C,KAAK,GAAG,UAAU,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QACtC,KAAK,CAAC,KAAK,EAAE,EAAE,CAAC;IAClB,CAAC,CAAC,CAAC;IACH,IAAI,CAAC;QACH,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC,CAAC,CAAC;IAC5D,CAAC;YAAS,CAAC;QACT,IAAI,KAAK;YAAE,YAAY,CAAC,KAAK,CAAC,CAAC;IACjC,CAAC;IAED,mDAAmD;IACnD,IAAI,IAAI,GAAsB,IAAI,CAAC;IACnC,IAAI,OAAO,GAAG,QAAQ,CAAC;IACvB,KAAK,MAAM,CAAC,CAAC,EAAE,KAAK,CAAC,IAAI,IAAI,EAAE,CAAC;QAC9B,IAAI,CAAC,GAAG,OAAO,EAAE,CAAC;YAAC,OAAO,GAAG,CAAC,CAAC;YAAC,IAAI,GAAG,KAAK,CAAC;QAAC,CAAC;IACjD,CAAC;IACD,IAAI,IAAI,IAAI,OAAO,CAAC,GAAG,CAAC,iBAAiB,KAAK,GAAG,EAAE,CAAC;QAClD,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,mCAAmC,OAAO,YAAY,IAAI,CAAC,SAAS,IAAI,CAAC,CAAC;IACjG,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC"}