agent-relay-orchestrator 0.129.9 → 0.129.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-relay-orchestrator",
-  "version": "0.129.9",
+  "version": "0.129.10",
   "description": "Agent Relay orchestrator — manages agent lifecycle across hosts",
   "type": "module",
   "bin": {
@@ -17,7 +17,7 @@
   },
   "dependencies": {
     "agent-relay-providers": "0.104.5",
-    "agent-relay-sdk": "0.2.127",
+    "agent-relay-sdk": "0.2.128",
     "callmux": "0.24.2"
   },
   "devDependencies": {

package/src/self-upgrade.ts

@@ -3,6 +3,7 @@ import { existsSync, writeFileSync } from "node:fs";
 import { homedir } from "node:os";
 import { getAllManifests } from "agent-relay-providers";
 import { gitCheckoutArtifactPaths, prepareGitCheckoutArtifact, rollbackRuntimeSymlink, swapRuntimeSymlink, type GitCheckoutArtifact } from "agent-relay-sdk/git-checkout-artifact";
+import { assertRegistryOnlyRuntimeManifest } from "agent-relay-sdk/npm-runtime";
 import { runInstallWithRetry } from "agent-relay-sdk";
 import { shellQuote } from "agent-relay-sdk/shell-utils";
 import type { OrchestratorConfig } from "./config";
@@ -207,6 +208,20 @@ export async function handleSelfUpgrade(
     return;
   }
 
+  // Option-4 fail-fast guard (#1435). The npm-reuse RPC install is in-place and additive —
+  // it must not drop the relay server co-installed in the same prefix — so it stays an
+  // `npm install --prefix <runtimePrefix>` rather than a staging+promote (that hardening is
+  // the CLI's job, and the RPC would need the same complete-managed-set + crash-safe swap the
+  // CLI has). Crucially, this prefix is NEVER the symlinked source checkout that triggers
+  // #1435: detectRuntimePrefix() derives it from THIS process's own module path (the segment
+  // before `/node_modules/`), so on a git-checkout host — where the orchestrator runs from
+  // source with no `/node_modules/` ancestor — it is undefined and buildInstallCommand()
+  // delegates to the `agent-relay upgrade` CLI (which installs into a fresh staging prefix).
+  // The prefix is set ONLY on clean-npm hosts, where it is a real dir with a registry-only
+  // manifest. This guard is the SAFE FLOOR: if a symlink-to-source prefix ever did reach here,
+  // refuse it with a clear, actionable error instead of npm's opaque EUNSUPPORTEDPROTOCOL.
+  if (plan.runtimePrefix) assertRegistryOnlyRuntimeManifest(plan.runtimePrefix);
+
   const install = await runInstallWithRetry(plan.installCmd, runner.run.bind(runner), {
     sleep: opts.sleep,
     retries: opts.installRetries,