fix(claude-bridge): recover login-shell PATH for bare CLI launches

[artemgetmann]

Review Fast Path

• User path fixed: isolated Telegram/launchd-style runtimes can find and launch bare claude again even when the inherited PATH is only system bins.
• Proof: pnpm exec vitest run src/agents/claude-bridge.test.ts passed; direct stripped-env repro still shows bare claude fails with ENOENT, and the new bridge test proves the spawn env now merges login-shell PATH before launch.
• Shared-state footgun removed: claude-bridge no longer assumes the service/runtime PATH already includes user-installed CLI bins like /Users/user/.local/bin.
• Still hurts: this does not claim live Telegram claude-bridge/sonnet is fixed end-to-end yet; it only fixes the bridge executable lookup boundary.

Why This Matters

• The active blocker is isolated runtime execution context, not Telegram transport and not continuity logic.
• In clean runtime envs, bare claude can disappear even though it works in the operator login shell.
• Recovering login-shell PATH at the bridge spawn point keeps the fix narrow and avoids dragging unrelated runtime/auth changes into this slice.

Scope Boundary

• Changed: src/agents/claude-bridge.ts, src/agents/claude-bridge.test.ts
• Did not change: Telegram transport, continuity/session handling, service env bootstrap, or tester-runtime config scripts.

Verification

• pnpm exec vitest run src/agents/claude-bridge.test.ts
• Direct stripped-env repro before fix shape:
  • env -i HOME="$HOME" USER="$USER" LOGNAME="$LOGNAME" TMPDIR="${TMPDIR:-/tmp}" PATH="/usr/bin:/bin:/usr/sbin:/sbin" /opt/homebrew/bin/node -e 'const { spawnSync } = require("node:child_process"); const before = spawnSync("claude", ["--version"], { encoding: "utf8" }); console.log(JSON.stringify({ beforeError: before.error ? { code: before.error.code, message: before.error.message } : null, beforeStatus: before.status ?? null }));'
  • observed: {"beforeError":{"code":"ENOENT","message":"spawnSync claude ENOENT"},"beforeStatus":null}
• Test proof of the fix:
  • bridge test asserts spawn env PATH becomes /Users/user/.local/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin when login-shell PATH is available and runtime PATH is stripped

AI Assistance

• AI-assisted
• Testing degree: targeted