@quolu/lattice 0.54.0 → 0.55.0

package/docs/bridge-setup.md

@@ -33,6 +33,86 @@ fileを除去し、JSON結果の`recovery`へ処置を明示する。その後
 自動化・隔離testではabsoluteな`LATTICE_CONFIG_DIR`で設定rootを変更できる。無効な設定、低いport、
 使用中の明示port、危険なrequest target、到達不能upstreamはsilent fallbackせずtyped errorを返す。
 
+## 常駐が黙って死んでいないか確かめる
+
+`reachable`は「設定したaddressで誰かが応答しているか」しか答えない。常駐設定（macOSのLaunchAgent、
+WindowsのStartup launcher）が消えたbinaryを指していると、supervisorは起動できないprocessを回し続け、
+どこにもエラーが出ないまま公開面から端末だけが消える。`status`はそれを1回で名指しする。
+
+```bash
+lattice bridge status --json
+```
+
+bridgeが無効な間は以下すべてnullで、bridgeを有効にしている時だけ観測する。
+
+**`persistence`** — 常駐設定が実際に起動する対象。
+
+| field | 意味 |
+| --- | --- |
+| `state` | `installed`／`not_installed`／`unreadable` |
+| `loaded` | launchdへ読み込み済みか。Windowsには対応概念が無いのでnull |
+| `node_path`・`node_exists` | 起動するNode実行体と、それが今も存在するか |
+| `bridge_path`・`bridge_exists` | 起動するbridge scriptと、それが今も存在するか |
+| `error` | `unreadable`のときだけtyped code（例`BRIDGE_LAUNCH_AGENT_PLIST_UNSAFE`） |
+
+**`runtime`** — いま応答しているprocess自身の申告。`state`は`running`／`not_running`／`unattested`／
+`descriptor_invalid`で、`running`以外では各値がnullになる。`running`でも、identityを返さない
+0.55.0より前のdaemonが走っている間は`version`以下がnullになる（この場合`runtime_drift`は空になり、
+乖離の有無は判定できていない——「乖離なし」ではない）。
+
+| field | 意味 |
+| --- | --- |
+| `pid` | 応答しているprocessのpid |
+| `version` | そのprocessが読み込んでいるLatticeの版 |
+| `node_path`・`node_version` | そのprocessを実行しているNodeの実体pathと版 |
+| `bridge_path` | そのprocessが実行しているbridge script |
+
+**`runtime_drift`** — 両者の食い違い。空配列は「差が無い」または「`runtime`が名乗っていないので
+判定できない」のどちらかである。
+
+| 値 | 意味 |
+| --- | --- |
+| `bridge_path` | 常駐設定と違うtreeのcodeが走っている（開発treeの残骸など） |
+| `node_path` | 常駐設定が指すnodeと実走nodeが別実体。焼くのは意図的にaliasなので、比較はrealpathで行う |
+| `version` | npm更新後まだ旧moduleを保持している |
+
+**`remedy`** — 自己解消しない状態にだけ、打つべきコマンドが入る。出るのは次の4つ。
+
+- `persistence.node_exists`または`bridge_exists`がfalse（起動対象が消えた）
+- `persistence.state`が`not_installed`（bridgeは有効なのに常駐設定が無い。いま走っているdaemonが
+  最後の1つで、再起動しても戻らない）
+- `persistence.state`が`unreadable`（常駐設定を読めない）
+- `runtime_drift`に`node_path`または`bridge_path`がある
+
+`version`だけの差には`remedy`を出さない。daemonは60秒ごとにon-diskのpackage.jsonと自分の版を
+突き合わせ、差があれば自ら終了してsupervisorに新codeで起動し直させる。放っておいて最大1分ほどで
+解消するので、コマンドを出す状態ではない。自己解消する差にコマンドを出すと、本物の障害が埋もれる。
+
+`remedy`が出たら`reconfigure`で作り直す。plistやlauncherを手で書き換えない。
+
+```bash
+lattice bridge reconfigure --json
+```
+
+### 焼き込むnode pathの選び方（ADR 0163）
+
+常駐設定へ焼くnodeのpathは、版付きの実体（homebrewの`Cellar/node/<version>/bin/node`、nvm-windowsの
+版ディレクトリ）ではなく、**同じbinaryを指すとrealpathで検証できた安定alias**（`/opt/homebrew/bin/node`、
+`C:\Program Files\nodejs\node.exe`）を選ぶ。`brew upgrade node`が旧versionのディレクトリごと消しても
+起動対象が残るようにするためである。
+
+安定aliasを検証できない環境（shim方式のasdf／volta等。shimは自身のlauncherへ解決されるので実体と
+一致しない）では、版付きpathのまま焼く。検証していないpathを推測で焼けば別のnodeでdaemonが起動して
+しまうためで、そこでの防御は起動継続ではなく`node_exists`による消滅の可視化である。
+
+> **0.55.0より前に設定した常駐は自動では移行しない。** 焼き直しは`reconfigure`を実行した時にだけ
+> 起きるので、Latticeを更新しただけの端末は版付きpathを抱えたままになる。更新後に各端末で
+> `lattice bridge reconfigure --json`を1回打つ。現在どちらを焼いているかは`persistence.node_path`で読める。
+
+なお`setup`／`reconfigure`をnode_modules配下でない実体（開発tree）から実行すると、結果の`warnings`へ
+`BRIDGE_PERSISTED_FROM_DEVELOPMENT_TREE`が入る（該当しなければ空配列）。そのtreeを動かすと常駐が
+止まり、`npm`更新も反映されない。開発treeから常駐させること自体は正当な操作なので拒否はしない。
+
 ## listen IPがDHCPで動く場合
 
 設定したlisten IPがホストから消えると、古いsocketは死んだアドレスへ取り残され、LANから到達できなくなる。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quolu/lattice",
-  "version": "0.54.0",
+  "version": "0.55.0",
   "description": "Schedulability compiler for multi-agent development: observe real code boundaries, refactor the conflicting seam, recompile the plan for parallel execution",
   "author": {
     "name": "Quo / クオ at kitepon.dev",

package/src/bridge-cli.mjs

@@ -1,7 +1,9 @@
+import { realpath } from 'node:fs/promises';
 import { createConnection, isIP } from 'node:net';
 import { networkInterfaces } from 'node:os';
 import * as clack from '@clack/prompts';
 
+import packageJson from '../package.json' with { type: 'json' };
 import { resolveBridgeListenAddress } from './bridge-address.mjs';
 import { registerBridgeUpstream } from './bridge-registrar.mjs';
 import {
@@ -10,24 +12,30 @@ import {
 } from './bridge-config.mjs';
 import {
   clearBridgeStopControl, ensureBridgeDaemon, readBridgeDaemonDescriptor,
-  removeBridgeDaemonActiveMarker, removeBridgeDaemonDescriptor, requestBridgeDaemonStop,
-  stopBridgeDaemon,
+  readBridgeRuntimeIdentity, removeBridgeDaemonActiveMarker, removeBridgeDaemonDescriptor,
+  requestBridgeDaemonStop, stopBridgeDaemon,
 } from './bridge-daemon.mjs';
+import { bridgeDevelopmentTreeWarning, DEFAULT_BRIDGE_PATH } from './bridge-executable.mjs';
 import {
-  disableBridgeLaunchAgent, installBridgeLaunchAgent, restoreBridgeLaunchAgent,
-  snapshotBridgeLaunchAgent,
+  describeBridgeLaunchAgent, disableBridgeLaunchAgent, installBridgeLaunchAgent,
+  restoreBridgeLaunchAgent, snapshotBridgeLaunchAgent,
 } from './bridge-launch-agent.mjs';
 import {
-  disableBridgeStartupFolder, installBridgeStartupFolder, restoreBridgeStartupFolder,
-  snapshotBridgeStartupFolder,
+  describeBridgeStartupFolder, disableBridgeStartupFolder, installBridgeStartupFolder,
+  restoreBridgeStartupFolder, snapshotBridgeStartupFolder,
 } from './bridge-startup-folder.mjs';
 
 // v2 adds the liveness fields. `enabled` only says the configuration is on;
 // it never said the bridge could actually be reached, which let a DHCP lease
 // change take the published surface down while status kept reporting health.
 // v3 adds `hub` (bh3): the terminal's registered bridge-hub, if any.
-const RESULT_SCHEMA = 'lattice.bridge_cli_result.v3';
+// v4 adds `persistence`/`runtime`/`runtime_drift`/`remedy`/`warnings`: the
+// configuration being reachable still said nothing about whether the OS
+// persistence entry points at binaries that exist, or whether the process
+// actually serving is the code and node a restart would bring back.
+const RESULT_SCHEMA = 'lattice.bridge_cli_result.v4';
 const REACHABILITY_PROBE_TIMEOUT_MS = 750;
+const RECONFIGURE_COMMAND = 'lattice bridge reconfigure --json';
 
 /** TCP connect probe. Answers "is anything accepting there right now". */
 export function probeBridgeListener({ address, port, timeoutMs = REACHABILITY_PROBE_TIMEOUT_MS }) {
@@ -80,10 +88,86 @@ async function bridgeLiveness(config, { interfaces = networkInterfaces(), probe
 function platformLaunchAgent() {
   if (process.platform === 'win32') {
     return { snapshot: snapshotBridgeStartupFolder, install: installBridgeStartupFolder,
-      disable: disableBridgeStartupFolder, restore: restoreBridgeStartupFolder };
+      disable: disableBridgeStartupFolder, restore: restoreBridgeStartupFolder,
+      describe: describeBridgeStartupFolder };
   }
   return { snapshot: snapshotBridgeLaunchAgent, install: installBridgeLaunchAgent,
-    disable: disableBridgeLaunchAgent, restore: restoreBridgeLaunchAgent };
+    disable: disableBridgeLaunchAgent, restore: restoreBridgeLaunchAgent,
+    describe: describeBridgeLaunchAgent };
+}
+
+const UNREADABLE_PERSISTENCE = Object.freeze({ loaded: null, node_path: null, node_exists: false,
+  bridge_path: null, bridge_exists: false });
+
+/**
+ * What the OS persistence entry (LaunchAgent plist, Windows Startup launcher)
+ * actually points at, and whether those paths still exist. A read failure is
+ * reported as `unreadable` rather than thrown: this is a diagnostic, and it
+ * is worth least on exactly the broken hosts where it would otherwise abort.
+ */
+async function bridgePersistence({ launchAgent, env }) {
+  try {
+    const snapshot = await launchAgent.snapshot({ env });
+    const described = await launchAgent.describe({ snapshot, env });
+    // `loaded` is launchd-specific; the Windows Startup folder has no such
+    // concept and reports null rather than pretending to know.
+    const loaded = typeof snapshot?.loaded === 'boolean' ? snapshot.loaded : null;
+    if (described === null) return { state: 'not_installed', ...UNREADABLE_PERSISTENCE, loaded, error: null };
+    return { state: 'installed', loaded, ...described, error: null };
+  } catch (error) {
+    // Only environment failures degrade into a report: typed BridgeConfigErrors
+    // and raw fs errnos both carry a string `code`. Anything else is a defect in
+    // this codebase (a missing describe implementation, a bad argument) and must
+    // surface as itself rather than be laundered into "unreadable".
+    if (typeof error?.code !== 'string') throw error;
+    return { state: 'unreadable', ...UNREADABLE_PERSISTENCE, error: error.code };
+  }
+}
+
+/**
+ * Where the running process disagrees with what a restart would produce.
+ * `node_path` is compared through realpath because the persisted path is
+ * deliberately a stable alias (see bridge-executable.mjs) — the strings are
+ * expected to differ; the binaries behind them are not.
+ */
+async function bridgeRuntimeDrift(persistence, runtime) {
+  if (persistence?.state !== 'installed' || runtime?.state !== 'running') return [];
+  const drift = [];
+  if (runtime.bridge_path !== null && persistence.bridge_path !== null
+    && runtime.bridge_path !== persistence.bridge_path) drift.push('bridge_path');
+  if (runtime.node_path !== null && persistence.node_path !== null) {
+    const target = await realpath(persistence.node_path).catch(() => null);
+    if (target !== null && target !== runtime.node_path) drift.push('node_path');
+  }
+  if (runtime.version !== null && runtime.version !== packageJson.version) drift.push('version');
+  return drift;
+}
+
+/**
+ * `version` drift alone carries no remedy on purpose: the daemon polls its own
+ * on-disk package version and exits for the supervisor to relaunch on the new
+ * code (see bridgeDaemonVersionDrifted), so it resolves itself within a minute.
+ * Everything else here outlives the current process: a missing binary, a
+ * mismatched path, or an enabled bridge with no persistence entry at all all
+ * survive until someone reinstalls the entry.
+ */
+function bridgeRemedy(persistence, drift) {
+  if (persistence === null) return null;
+  if (persistence.state === 'unreadable') return RECONFIGURE_COMMAND;
+  // Only reached with the bridge enabled, so "nothing is installed" means the
+  // currently-serving daemon is the last one: nothing brings it back at reboot.
+  if (persistence.state === 'not_installed') return RECONFIGURE_COMMAND;
+  if (persistence.state === 'installed'
+    && (!persistence.node_exists || !persistence.bridge_exists)) return RECONFIGURE_COMMAND;
+  return drift.includes('node_path') || drift.includes('bridge_path') ? RECONFIGURE_COMMAND : null;
+}
+
+async function bridgeDiagnostics({ config, launchAgent, env, runtimeIdentity }) {
+  if (config?.enabled !== true) return null;
+  const persistence = await bridgePersistence({ launchAgent, env });
+  const runtime = await runtimeIdentity({ env });
+  const drift = await bridgeRuntimeDrift(persistence, runtime);
+  return { persistence, runtime, drift, remedy: bridgeRemedy(persistence, drift) };
 }
 
 function fail(stderr, code, message) {
@@ -121,7 +205,7 @@ function parseOptions(words) {
   return options;
 }
 
-function result(action, config, recovery = null, liveness = null) {
+function result(action, config, recovery = null, liveness = null, diagnostics = null, warnings = null) {
   return { schema: RESULT_SCHEMA, action, configured: config !== null, enabled: config?.enabled ?? false,
     listen: config?.listen ?? null, allowed_hosts: config?.allowed_hosts ?? null,
     upstream: config?.upstream ?? null, hub: config?.hub ?? null, updated_at: config?.updated_at ?? null, recovery,
@@ -129,7 +213,12 @@ function result(action, config, recovery = null, liveness = null) {
     effective_listen: liveness?.effective_listen ?? null,
     listen_candidates: liveness?.listen_candidates ?? null,
     reachable: liveness?.reachable ?? null,
-    liveness_reason: liveness?.liveness_reason ?? null };
+    liveness_reason: liveness?.liveness_reason ?? null,
+    persistence: diagnostics?.persistence ?? null,
+    runtime: diagnostics?.runtime ?? null,
+    runtime_drift: diagnostics?.drift ?? null,
+    remedy: diagnostics?.remedy ?? null,
+    warnings };
 }
 
 export async function collectBridgeSetupWizard({ input, output, prompts = clack } = {}) {
@@ -180,7 +269,8 @@ export async function collectBridgeSetupWizard({ input, output, prompts = clack
 export async function runBridgeCli({ argv, stdout, stderr, env = process.env,
   stdin = process.stdin, daemon = { ensure: ensureBridgeDaemon, requestStop: requestBridgeDaemonStop,
     stop: stopBridgeDaemon, clearStop: clearBridgeStopControl },
-  launchAgent = platformLaunchAgent(),
+  launchAgent = platformLaunchAgent(), runtimeIdentity = readBridgeRuntimeIdentity,
+  bridgePath = DEFAULT_BRIDGE_PATH,
   prompts = clack, probe = probeBridgeListener, interfaces = networkInterfaces() } = {}) {
   if (!Array.isArray(argv)) {
     return fail(stderr, 'USAGE', 'usage: lattice bridge <setup|reconfigure|status|disable|register> [options] --json');
@@ -308,11 +398,21 @@ export async function runBridgeCli({ argv, stdout, stderr, env = process.env,
         return configured;
       });
     } else return fail(stderr, 'USAGE', 'unknown bridge command or options');
-    // Liveness is only meaningful for a read: the mutating commands have just
-    // reconfigured the daemon and the socket may not have settled yet.
+    // Liveness and the persistence/runtime diagnostics are only meaningful for
+    // a read: the mutating commands have just reconfigured the daemon and the
+    // socket may not have settled yet.
     const liveness = command === 'status' ? await bridgeLiveness(config, { probe, interfaces }) : null;
-    if (wizard) stdout.write(`Lattice bridgeを${config.listen.address}:${config.listen.port}で有効にしました。\n`);
-    else stdout.write(`${JSON.stringify(result(command, config, recovery, liveness))}\n`);
+    const diagnostics = command === 'status'
+      ? await bridgeDiagnostics({ config, launchAgent, env, runtimeIdentity }) : null;
+    // An install persisted straight out of a checkout is legitimate but must
+    // never be silent — it is half of what made the 2026-08-10 outage take
+    // manual launchctl archaeology to explain.
+    const warnings = command === 'setup' || command === 'reconfigure'
+      ? [bridgeDevelopmentTreeWarning(bridgePath)].filter((warning) => warning !== null) : null;
+    if (wizard) {
+      stdout.write(`Lattice bridgeを${config.listen.address}:${config.listen.port}で有効にしました。\n`);
+      for (const warning of warnings ?? []) stdout.write(`警告: ${warning.message}\n`);
+    } else stdout.write(`${JSON.stringify(result(command, config, recovery, liveness, diagnostics, warnings))}\n`);
     return 0;
   } catch (error) {
     stderr.write(`${JSON.stringify({ schema: 'lattice.cli_error.v2',

package/src/bridge-daemon.mjs

@@ -306,6 +306,33 @@ async function attest(descriptor) {
   } catch { return null; }
 }
 
+const UNIDENTIFIED_RUNTIME = Object.freeze({ pid: null, version: null, node_path: null,
+  node_version: null, bridge_path: null });
+
+/**
+ * Who is actually serving right now — pid, product version, node binary — as
+ * reported by the running process itself over its attested health endpoint,
+ * not as recorded by any file. This is the only way to see that a daemon is
+ * executing code or a node binary that no longer matches what a restart would
+ * pick up. A malformed descriptor is reported as its own state rather than
+ * thrown: this feeds `lattice bridge status`, the command an operator reaches
+ * for precisely when something is already broken.
+ */
+export async function readBridgeRuntimeIdentity({ env = process.env } = {}) {
+  let descriptor;
+  try { descriptor = await readBridgeDaemonDescriptor({ env }); } catch (error) {
+    if (error?.code !== 'BRIDGE_DAEMON_DESCRIPTOR_INVALID') throw error;
+    return { ...UNIDENTIFIED_RUNTIME, state: 'descriptor_invalid' };
+  }
+  if (descriptor === null) return { ...UNIDENTIFIED_RUNTIME, state: 'not_running' };
+  const body = await attest(descriptor);
+  if (body === null) return { ...UNIDENTIFIED_RUNTIME, state: 'unattested', pid: descriptor.pid };
+  const text = (value) => (typeof value === 'string' ? value : null);
+  return { state: 'running', pid: descriptor.pid, version: text(body.version),
+    node_path: text(body.node_path), node_version: text(body.node_version),
+    bridge_path: text(body.bridge_path) };
+}
+
 async function healthy(descriptor, config) {
   if (descriptor === null || descriptor.address !== config.listen.address
     || descriptor.port !== config.listen.port) return false;

package/src/bridge-executable.mjs

@@ -0,0 +1,100 @@
+/**
+ * What gets baked into the OS persistence surfaces (the macOS LaunchAgent
+ * plist, the Windows Startup launcher) as the Node executable — and how a
+ * bridge installed out of a development tree is called out at setup time.
+ *
+ * `process.execPath` is already realpath-resolved by libuv, so under Homebrew
+ * it reads `/opt/homebrew/Cellar/node/<version>/bin/node` even when node was
+ * invoked through `/opt/homebrew/bin/node`. Baking that version-pinned path
+ * into a LaunchAgent makes `brew upgrade node` delete the very binary launchd
+ * is told to exec: KeepAlive then respins a process that can never start, and
+ * nothing anywhere reports it — the terminal just disappears from the
+ * published view (hit on this Mac 2026-08-08 and again 2026-08-10).
+ *
+ * So we bake a stable alias whenever one demonstrably resolves to the same
+ * binary. The test is deliberately narrow — `realpath(candidate)` equals the
+ * already-validated `resolved` path, and nothing else. In particular we do
+ * NOT additionally require the candidate's parent directories to be free of
+ * group write: the standard Homebrew prefix (`/opt/homebrew/bin`, drwxrwxr-x)
+ * fails that check, so the rule would refuse to fire in exactly the
+ * environment it exists for. Nor would it buy anything — the Cellar path we
+ * bake today sits under an equally group-writable `/opt/homebrew/Cellar`, so
+ * the set of principals who can swap the binary is identical either way. The
+ * binary itself is still checked (owner, mode, exec bit) by the caller before
+ * any of this runs.
+ *
+ * Shim-based version managers (asdf, volta) resolve to their own launcher
+ * rather than to the node binary, so they never match and we keep the
+ * resolved path. That is the honest outcome: we never bake a path we could
+ * not verify, and `lattice bridge status` reports what the persistence
+ * surface actually points at, so a version-pinned path is visible before it
+ * dies rather than silent after.
+ */
+
+import { realpath } from 'node:fs/promises';
+import path from 'node:path';
+
+export const DEFAULT_BRIDGE_PATH = path.resolve(import.meta.dirname, '../bin/lattice-bridge.mjs');
+export const DEFAULT_SUPERVISOR_PATH =
+  path.resolve(import.meta.dirname, '../bin/lattice-bridge-supervisor.mjs');
+
+// Directories that hold a stable `node` on a default install of the platform's
+// usual package manager. They are appended to (not substituted for) whatever
+// PATH the installing shell had, because launchd and the Windows Startup
+// folder inherit no PATH at all — the candidate has to come from here.
+const WELL_KNOWN_DIRECTORIES = {
+  darwin: ['/opt/homebrew/bin', '/usr/local/bin', '/usr/bin'],
+  win32: ['C:\\Program Files\\nodejs'],
+  other: ['/usr/local/bin', '/usr/bin'],
+};
+
+function candidateDirectories(env, platform) {
+  const raw = typeof env.PATH === 'string' ? env.PATH
+    : typeof env.Path === 'string' ? env.Path : '';
+  const fromPath = raw.split(platform === 'win32' ? ';' : ':')
+    .filter((entry) => entry !== '' && path.isAbsolute(entry));
+  const wellKnown = WELL_KNOWN_DIRECTORIES[platform] ?? WELL_KNOWN_DIRECTORIES.other;
+  return [...new Set([...fromPath, ...wellKnown])];
+}
+
+function samePath(left, right, platform) {
+  return platform === 'win32' ? left.toLowerCase() === right.toLowerCase() : left === right;
+}
+
+/**
+ * The path to bake for a node executable whose real location is `resolved`:
+ * the first candidate alias that resolves to exactly that binary, or
+ * `resolved` itself when no alias can be verified.
+ */
+export async function stableNodePath({ resolved, env = process.env,
+  platform = process.platform } = {}) {
+  if (typeof resolved !== 'string' || !path.isAbsolute(resolved)) {
+    throw new TypeError('resolved node executable path required');
+  }
+  const name = platform === 'win32' ? 'node.exe' : 'node';
+  for (const directory of candidateDirectories(env, platform)) {
+    const candidate = path.join(directory, name);
+    if (samePath(candidate, resolved, platform)) continue;
+    let target;
+    try { target = await realpath(candidate); } catch { continue; }
+    if (samePath(target, resolved, platform)) return candidate;
+  }
+  return resolved;
+}
+
+/**
+ * A bridge script outside any `node_modules` is being persisted straight out
+ * of a checkout: the daemon then survives every `npm update` unchanged, and
+ * dies for good if the tree is moved or deleted. Not an error — installing
+ * from a development tree is a legitimate thing to do deliberately — but it
+ * must not happen without the operator being told.
+ */
+export function bridgeDevelopmentTreeWarning(bridgePath) {
+  if (typeof bridgePath !== 'string') return null;
+  if (bridgePath.split(/[\\/]/u).includes('node_modules')) return null;
+  return {
+    code: 'BRIDGE_PERSISTED_FROM_DEVELOPMENT_TREE',
+    message: `the bridge is persisted from a development tree (${bridgePath}); `
+      + 'it will not follow npm updates and stops for good if that tree moves',
+  };
+}

package/src/bridge-launch-agent.mjs

@@ -2,13 +2,14 @@ import { execFile } from 'node:child_process';
 import { randomBytes } from 'node:crypto';
 import { constants as fsConstants } from 'node:fs';
 import {
-  chmod, lstat, mkdir, open, readFile, realpath, rename, rm, writeFile,
+  chmod, lstat, mkdir, open, realpath, rename, rm, stat, writeFile,
 } from 'node:fs/promises';
 import path from 'node:path';
 import { promisify } from 'node:util';
 
 import { BridgeConfigError, readBridgeConfig } from './bridge-config.mjs';
 import { readBridgeDaemonDescriptor } from './bridge-daemon.mjs';
+import { DEFAULT_BRIDGE_PATH, stableNodePath } from './bridge-executable.mjs';
 import { bridgeRegistrarSettings } from './bridge-registrar.mjs';
 
 export const BRIDGE_LAUNCH_AGENT_LABEL = 'dev.kitepon.lattice.bridge';
@@ -252,6 +253,40 @@ export async function snapshotBridgeLaunchAgent({ env = process.env,
   return Object.freeze({ installed: content !== null, loaded, content });
 }
 
+const PROGRAM_ARGUMENTS_PATTERN =
+  /<key>ProgramArguments<\/key>\s*<array>\s*<string>([^<]*)<\/string>\s*<string>([^<]*)<\/string>\s*<\/array>/u;
+
+/** Inverse of `xml`, innermost-last so an escaped `&amp;lt;` survives intact. */
+function unxml(value) {
+  return value.replaceAll('&apos;', "'").replaceAll('&quot;', '"')
+    .replaceAll('&gt;', '>').replaceAll('&lt;', '<').replaceAll('&amp;', '&');
+}
+
+async function pathPresent(ref) {
+  if (typeof ref !== 'string') return false;
+  try { await stat(ref); return true; } catch { return false; }
+}
+
+/**
+ * What the installed plist actually tells launchd to run, and whether those
+ * paths still exist. A LaunchAgent whose ProgramArguments point at a deleted
+ * binary is the product's worst failure mode: KeepAlive keeps respinning it,
+ * nothing logs, and the only visible symptom is a terminal missing from the
+ * published view. Reporting it here is what turns that into an answer
+ * `lattice bridge status` can give in one call.
+ */
+export async function describeBridgeLaunchAgent({ snapshot } = {}) {
+  if (snapshot?.installed !== true) return null;
+  const match = typeof snapshot.content === 'string'
+    ? snapshot.content.match(PROGRAM_ARGUMENTS_PATTERN) : null;
+  const nodePath = match === null ? null : unxml(match[1]);
+  const bridgePath = match === null ? null : unxml(match[2]);
+  return {
+    node_path: nodePath, node_exists: await pathPresent(nodePath),
+    bridge_path: bridgePath, bridge_exists: await pathPresent(bridgePath),
+  };
+}
+
 async function bootoutIfLoaded({ runner, uid }) {
   if (!await loadedState(runner, uid)) return false;
   await launchctl(runner, ['bootout', service(uid)], 'BRIDGE_LAUNCHCTL_BOOTOUT_FAILED',
@@ -261,17 +296,22 @@ async function bootoutIfLoaded({ runner, uid }) {
 
 export async function installBridgeLaunchAgent({ config, env = process.env,
   runner = defaultLaunchctlRunner, uid = userId(), nodePath = process.execPath,
-  bridgePath = path.resolve(import.meta.dirname, '../bin/lattice-bridge.mjs'),
+  bridgePath = DEFAULT_BRIDGE_PATH,
   waitReady = defaultWaitReady, waitStopped = defaultWaitStopped,
-  previousListen = null } = {}) {
+  stableNode = stableNodePath, previousListen = null } = {}) {
   if (config?.enabled !== true) throw fail('BRIDGE_DISABLED', 'bridge is disabled');
   const refs = bridgeLaunchAgentPaths(env);
   await prepareDirectory(refs.directory, uid);
   await strictPlist(refs.plist, uid);
+  // The safety checks run against the real binary; what goes into the plist is
+  // a stable alias for it when one can be verified, so a version-manager
+  // upgrade cannot delete the path launchd was told to exec. See
+  // bridge-executable.mjs for why the alias is not additionally permission-checked.
   const resolvedNode = await executablePath(nodePath, 'node executable', { uid });
+  const bakedNode = await stableNode({ resolved: resolvedNode, env });
   const resolvedBridge = await executablePath(bridgePath, 'bridge executable', { executable: false, uid });
   const instanceToken = randomBytes(32).toString('hex');
-  const content = plistDocument({ nodePath: resolvedNode, bridgePath: resolvedBridge, instanceToken, env });
+  const content = plistDocument({ nodePath: bakedNode, bridgePath: resolvedBridge, instanceToken, env });
   const stopped = await bootoutIfLoaded({ runner, uid });
   if (stopped) await waitStopped({ listen: previousListen, env });
   await atomicPlist(refs.plist, content);

package/src/bridge-server.mjs

@@ -7,6 +7,7 @@ import { parseTree } from 'jsonc-parser';
 
 import { networkInterfaces } from 'node:os';
 
+import packageJson from '../package.json' with { type: 'json' };
 import { resolveBridgeListenAddress } from './bridge-address.mjs';
 import { registerBridgeUpstream } from './bridge-registrar.mjs';
 import {
@@ -228,10 +229,18 @@ export async function startBridgeServer({
       response.writeHead(200, { 'content-type': 'application/json; charset=utf-8', 'cache-control': 'no-store' });
       const attested = typeof instanceToken === 'string'
         && incoming.headers['x-lattice-bridge-instance-token'] === instanceToken;
+      // The identity fields answer "what is actually running right now", which
+      // no descriptor can: the descriptor records what was configured, while a
+      // daemon can outlive an npm update or keep executing a node binary its
+      // own persistence entry no longer points at. Attested callers only —
+      // these are local filesystem paths and must not leak to the public
+      // availability probe.
       response.end(`${JSON.stringify(attested
         ? { schema: 'lattice.bridge_health.v1', pid: process.pid,
           address: currentConfig.listen.address, port: currentConfig.listen.port,
-          updated_at: currentConfig.updated_at ?? null }
+          updated_at: currentConfig.updated_at ?? null,
+          version: packageJson.version, node_path: process.execPath,
+          node_version: process.version, bridge_path: process.argv[1] ?? null }
         : { schema: 'lattice.bridge_health.v1', status: 'available' })}\n`);
       return;
     }

package/src/bridge-startup-folder.mjs

@@ -32,13 +32,16 @@ import { execFile } from 'node:child_process';
 import { randomBytes } from 'node:crypto';
 import { constants as fsConstants } from 'node:fs';
 import {
-  lstat, mkdir, open, readFile, realpath, rename, rm, writeFile,
+  lstat, mkdir, open, readFile, realpath, rename, rm, stat, writeFile,
 } from 'node:fs/promises';
 import path from 'node:path';
 import { promisify } from 'node:util';
 
 import { BridgeConfigError, readBridgeConfig } from './bridge-config.mjs';
 import { readBridgeDaemonDescriptor } from './bridge-daemon.mjs';
+import {
+  DEFAULT_BRIDGE_PATH, DEFAULT_SUPERVISOR_PATH, stableNodePath,
+} from './bridge-executable.mjs';
 import { bridgeRegistrarSettings } from './bridge-registrar.mjs';
 
 export const BRIDGE_STARTUP_LABEL = 'LatticeBridge';
@@ -242,6 +245,33 @@ export async function snapshotBridgeStartupFolder({ env = process.env } = {}) {
   return Object.freeze({ installed: launcherContent !== null, launcherContent, descriptorContent });
 }
 
+async function pathPresent(ref) {
+  if (typeof ref !== 'string') return false;
+  try { await stat(ref); return true; } catch { return false; }
+}
+
+/**
+ * The Windows counterpart of `describeBridgeLaunchAgent`, reporting the same
+ * shape: what the persisted launcher runs and whether it is still there. The
+ * node path comes from the `.vbs` (first triple-quoted argument), the bridge
+ * script from the supervisor descriptor that owns it.
+ */
+export async function describeBridgeStartupFolder({ snapshot } = {}) {
+  if (snapshot?.installed !== true) return null;
+  const quoted = typeof snapshot.launcherContent === 'string'
+    ? [...snapshot.launcherContent.matchAll(/"""([^"]*)"""/gu)].map((match) => match[1]) : [];
+  const nodePath = quoted.length > 0 ? quoted[0] : null;
+  let bridgePath = null;
+  try {
+    const parsed = JSON.parse(snapshot.descriptorContent);
+    if (typeof parsed?.bridgePath === 'string') bridgePath = parsed.bridgePath;
+  } catch {}
+  return {
+    node_path: nodePath, node_exists: await pathPresent(nodePath),
+    bridge_path: bridgePath, bridge_exists: await pathPresent(bridgePath),
+  };
+}
+
 /** Read the supervisor's own recorded pid and kill its whole process tree
   * (`taskkill /T /F`) — a forcibly-terminated supervisor cannot clean up its
   * child itself, so the tree kill is what actually stops the bridge, not the
@@ -266,17 +296,21 @@ async function stopRunning({ env, listen, runner, waitStopped }) {
 
 export async function installBridgeStartupFolder({ config, env = process.env,
   runner = defaultStartupRunner, nodePath = process.execPath,
-  bridgePath = path.resolve(import.meta.dirname, '../bin/lattice-bridge.mjs'),
-  supervisorPath = path.resolve(import.meta.dirname, '../bin/lattice-bridge-supervisor.mjs'),
+  bridgePath = DEFAULT_BRIDGE_PATH, supervisorPath = DEFAULT_SUPERVISOR_PATH,
   waitReady = defaultWaitReady, waitStopped = defaultWaitStopped,
-  previousListen = null } = {}) {
+  stableNode = stableNodePath, previousListen = null } = {}) {
   if (config?.enabled !== true) throw fail('BRIDGE_DISABLED', 'bridge is disabled');
   const refs = bridgeStartupFolderPaths(env);
   await prepareDirectory(refs.startupDirectory);
   await prepareDirectory(refs.runtimeDirectory);
   await strictFile(refs.launcher);
   await strictFile(refs.descriptor);
+  // Same reasoning as the LaunchAgent: validate the real binary, bake a
+  // verified stable alias for it. nvm-windows swaps the version behind the
+  // `C:\Program Files\nodejs` junction exactly the way Homebrew swaps the
+  // Cellar directory behind `/opt/homebrew/bin/node`.
   const resolvedNode = await executablePath(nodePath, 'node executable');
+  const bakedNode = await stableNode({ resolved: resolvedNode, env });
   const resolvedBridge = await executablePath(bridgePath, 'bridge executable');
   const resolvedSupervisor = await executablePath(supervisorPath, 'supervisor executable');
   const instanceToken = randomBytes(32).toString('hex');
@@ -286,7 +320,7 @@ export async function installBridgeStartupFolder({ config, env = process.env,
   await stopRunning({ env, listen: previousListen, runner, waitStopped });
   await atomicFile(refs.descriptor, descriptorContent);
   await atomicFile(refs.launcher,
-    launcherScript({ nodePath: resolvedNode, supervisorPath: resolvedSupervisor, descriptorPath: refs.descriptor }));
+    launcherScript({ nodePath: bakedNode, supervisorPath: resolvedSupervisor, descriptorPath: refs.descriptor }));
   await launch(runner, ['wscript.exe', refs.launcher], 'BRIDGE_STARTUP_LAUNCHER_FAILED',
     'could not start the bridge startup process');
   return waitReady({ config, instanceToken, env });

package/src/runtime-work-order-controller.mjs

@@ -348,8 +348,15 @@ async function observeWorkerProcessTree(pid, { requireDescendantsInRootGroup = t
       rawState: match[4],
       startedIdentity: match[5].trim(),
     };
-    if (![record.pid, record.processGroupId].every((value) => Number.isSafeInteger(value)
-      && value > 0) || !Number.isSafeInteger(record.parentPid) || record.parentPid < 0
+    // processGroupIdは0を許す: Linuxのkernel thread（pid 2 kthreaddとその子）は
+    // 実在するがユーザー空間のprocess groupに属さないためpgid=0を持つ——実機の`ps -axo`は
+    // これを常に含むので、pid>0の一律要求ではこの関数が動くたびに毎回fail closedしていた
+    // （2026-08-10、CIのubuntu-latestで再現・確認）。0は安全側にも効く: 実workerのroot
+    // process groupは常にpid>0のleaderが持つ実PIDなので、pgid=0のrecordは下の
+    // 「同じprocess groupを共有する無関係processが無いか」の照合に決して誤って一致しない。
+    if (!Number.isSafeInteger(record.pid) || record.pid <= 0
+      || !Number.isSafeInteger(record.processGroupId) || record.processGroupId < 0
+      || !Number.isSafeInteger(record.parentPid) || record.parentPid < 0
       || record.startedIdentity.length === 0 || records.has(record.pid)) {
       fail('WORK_ORDER_REPORT_INVALID', 'ps process recordが不正');
     }

package/src/todo-cli.mjs

@@ -183,6 +183,29 @@ function typedFailure(stderr, error) {
   return 1;
 }
 
+/**
+ * An error that reached here is, by definition, one none of the typed
+ * TodoStoreError/TypeError branches recognized — the one case where the
+ * caller most needs to know *what actually happened*. Collapsing it to just
+ * the constructor name (`{code:'INTERNAL_FAILURE',message:'Error'}`) was
+ * itself a diagnosability defect: a crashed `todo start` produced exactly
+ * that content-free payload, and the only way to find the real cause
+ * (`manifest_journal_head_mismatch`) was importing todo-store.mjs directly
+ * and calling readTodoStore() by hand (2026-08-10 P0). The actual message
+ * and a short stack excerpt cost nothing to include — this is a local CLI's
+ * own stderr, not a response surface with an untrusted audience.
+ */
+function internalFailure(stderr, error) {
+  const constructorName = error?.constructor?.name ?? 'Error';
+  const message = typeof error?.message === 'string' && error.message.length > 0
+    ? error.message : constructorName;
+  const detail = { error_name: constructorName };
+  if (typeof error?.stack === 'string' && error.stack.length > 0) {
+    detail.stack_excerpt = error.stack.split('\n').slice(0, 6).join('\n');
+  }
+  return typedFailure(stderr, { code: 'INTERNAL_FAILURE', message, detail });
+}
+
 const TODO_COMMAND_NAMES = Object.freeze([
   'status', 'show', 'note', 'bindings', 'independence', 'seam-profile', 'seam-proposal',
   'verify', 'snapshot', 'gantt', 'dashboard', 'phase', 'migrate', 'start', 'block',
@@ -2811,9 +2834,7 @@ export async function runTodoCli({ argv, cwd, stdout, stderr, env = process.env
       await runTodoSchemaCommand(argv[0], stdout);
       return 0;
     } catch (error) {
-      return typedFailure(stderr, {
-        code: 'INTERNAL_FAILURE', message: error?.constructor?.name ?? 'Error',
-      });
+      return internalFailure(stderr, error);
     }
   }
 
@@ -2835,9 +2856,7 @@ export async function runTodoCli({ argv, cwd, stdout, stderr, env = process.env
     } catch (error) {
       if (typeof error?.code === 'string' && error.detail !== null
         && typeof error.detail === 'object') return typedFailure(stderr, error);
-      return typedFailure(stderr, {
-        code: 'INTERNAL_FAILURE', message: error?.constructor?.name ?? 'Error',
-      });
+      return internalFailure(stderr, error);
     }
   }
 
@@ -3118,7 +3137,18 @@ export async function runTodoCli({ argv, cwd, stdout, stderr, env = process.env
     const ganttCommand = argv[0] === 'gantt';
     const dashboardAdopt = argv[0] === 'dashboard' && argv[1] === 'adopt';
     const migrationDryRun = argv[0] === 'migrate' && argv.includes('--dry-run');
-    if (!ganttCommand && !dashboardAdopt && !migrationDryRun) {
+    // `verify` is the store's own read-only recovery diagnostic — the command
+    // an operator reaches for precisely when the store might be inconsistent.
+    // ensureActiveProjectDashboard calls readTodoStoreStable for an unrelated
+    // side effect (registering this session as an active dashboard project),
+    // and readTodoStoreStable retries a persistent STORE_INCONSISTENT as if it
+    // were a transient in-flight write before giving up and reporting a
+    // content-free STORE_BUSY. Running that pre-hook ahead of `verify` meant
+    // the one command meant to surface the real inconsistency never got to —
+    // it died in the same generic way every other command did (2026-08-10 P0:
+    // `todo verify` was unreachable for the exact case it exists to diagnose).
+    const verifyCommand = argv[0] === 'verify';
+    if (!ganttCommand && !dashboardAdopt && !migrationDryRun && !verifyCommand) {
       await ensureActiveProjectDashboard({ repoRoot, env });
     }
     const result = atomicCommit
@@ -3135,9 +3165,6 @@ export async function runTodoCli({ argv, cwd, stdout, stderr, env = process.env
         message: error.message,
       });
     }
-    return typedFailure(stderr, {
-      code: 'INTERNAL_FAILURE',
-      message: error?.constructor?.name ?? 'Error',
-    });
+    return internalFailure(stderr, error);
   }
 }