remotelink 0.4.6 → 0.4.7

package/README.md

@@ -53,7 +53,7 @@ npx remotelink --help          Show help
 
 The package also exposes the aliases `remote-link` and `remote-arc`.
 
-In 0.4.6, background recovery and Relay reconnect are separate. A normal npx remotelink@latest launch can safely hand off a known older background Agent to the current release without creating two executors.
+In 0.4.7, background recovery and Relay reconnect are separate. A normal npx remotelink@latest launch can safely hand off a known older background Agent to the current release without creating two executors.
 Recovery installs a user service (macOS/Linux) or a hidden login supervisor
 (Windows), which takes over when the executing Agent ends. Only one updated
 Agent owns execution; additional terminals follow its operation log and offer
@@ -62,7 +62,7 @@ execution lease. Turning recovery off preserves current execution. Explicit
 Stop background Agent also ends that Agent's work. Windows recovery needs the
 supervisor to remain running; killing it requires a local relaunch or login.
 Sleep/power loss still makes the device unavailable. All concurrent instances
-must be updated; pre-0.4.4 Agents do not participate in the execution lease. When the installed version is identified as an older release, 0.4.6 performs a controlled handoff even when that older Agent still owns the execution lease: it stops the known Remote Arc worker and supervisor, waits for the lease to release, preserves pairing and policy, installs the replacement bundle, and verifies that the replacement worker owns execution. Unknown processes still fail closed instead of being killed automatically. Unknown legacy processes still fail closed instead of being killed automatically.
+must be updated; pre-0.4.4 Agents do not participate in the execution lease. When the installed version is identified as an older release, 0.4.7 performs a controlled handoff even when that older Agent still owns the execution lease: it stops the known Remote Arc worker and supervisor, waits for the lease to release, preserves pairing and policy, installs the replacement bundle, and verifies that the replacement worker owns execution. If a saved device pairing has been revoked from Dashboard, interactive startup now validates it before viewer/background attach, stops the known local background owner, clears the revoked credential and begins fresh pairing. Unknown processes still fail closed instead of being killed automatically.
 
 ## Native execution core
 

package/dist/index.js

@@ -7433,7 +7433,7 @@ var {
 } = createBackgroundController();
 
 // src/index.ts
-var VERSION = "0.4.6";
+var VERSION = "0.4.7";
 var DEFAULT_ORIGIN = "https://mcp.remotearc.app";
 var CONFIG_DIR = path7.join(os4.homedir(), ".remotearc");
 var CONFIG_PATH = path7.join(CONFIG_DIR, "config.json");
@@ -8060,6 +8060,19 @@ async function main() {
       if (agentMode || supervisorMode) return;
       config = await pair(origin, selectedMode());
     }
+    if (!agentMode && !supervisorMode) {
+      try {
+        await validateSavedPairing(config);
+      } catch (error) {
+        if (!(error instanceof RevokedDeviceCredentialError)) throw error;
+        logLine("warn", error.message);
+        await disableBackgroundAgent({ stopCurrent: true }).catch(() => void 0);
+        await resetConfig();
+        logLine("event", "Starting a fresh device pairing\u2026");
+        config = null;
+        continue;
+      }
+    }
     if (disableBackground) {
       config.backgroundEnabled = false;
       await writeConfig(config);