fix(runtime): guard path-candidate activation on the remote runtime proxy

MobileSocketWiring.onReady called this.runtime.activateRecentPtyPathCandidateTracking() unconditionally, throwing on the E2EE/remote proxy (which lacks the method) and breaking the remote runtime connection (CI verify failure). Guarded with optional chaining (runtime-rpc.ts:900) — activation is a local-host concern. Mutation-verified E2EE-proxy regression test. Integration test + 3 typechecks green.

Co-authored-by: Orca <help@stably.ai>

src/main/runtime/runtime-rpc.test.ts

@@ -3253,6 +3253,58 @@ describe('OrcaRuntimeRpcServer', () => {
     }
   })
 
+  it('completes remote E2EE authentication against a runtime proxy without activateRecentPtyPathCandidateTracking', async () => {
+    const userDataPath = mkdtempSync(join(tmpdir(), 'orca-runtime-rpc-'))
+    // Why: a remote-host runtime proxy only implements RPC-forwarded methods;
+    // activation is a local-host concern, so the proxy legitimately lacks
+    // activateRecentPtyPathCandidateTracking and onReady must not throw.
+    const runtimeProxy = {
+      getRuntimeId: () => 'proxy-runtime-test',
+      getStartedAt: () => 1,
+      getStatus: () => ({ graphStatus: 'unavailable' }),
+      cleanupSubscriptionsForConnection: () => {},
+      cancelMobileDictationForConnection: () => {},
+      onClientDisconnected: () => {}
+    } as unknown as OrcaRuntimeService
+    expect(
+      (runtimeProxy as { activateRecentPtyPathCandidateTracking?: unknown })
+        .activateRecentPtyPathCandidateTracking
+    ).toBeUndefined()
+    const server = new OrcaRuntimeRpcServer({
+      runtime: runtimeProxy,
+      userDataPath,
+      enableWebSocket: true,
+      wsPort: 0
+    })
+
+    await server.start()
+    const offer = server.createPairingOffer({
+      address: '127.0.0.1',
+      name: 'remote',
+      scope: 'runtime'
+    })
+    expect(offer.available).toBe(true)
+    if (!offer.available) {
+      throw new Error('WebSocket pairing unavailable')
+    }
+    // Real E2EE pairing + authentication drives MobileSocketWiring.onReady
+    // before e2ee_authenticated is sent; a throwing onReady never authenticates.
+    const session = await authenticateMobileWsSession(offer.pairingUrl)
+    const responses = createEncryptedWsResponseReader(session)
+    try {
+      sendEncryptedWsRequest(session, { id: 'proxy_status', method: 'status.get' })
+      await expect(responses.next('proxy_status')).resolves.toMatchObject({
+        id: 'proxy_status',
+        ok: true,
+        result: { graphStatus: 'unavailable' }
+      })
+    } finally {
+      responses.dispose()
+      session.ws.close()
+      await server.stop()
+    }
+  })
+
   it('keeps active runtime multiplex streams responsive while a background stream is ACK-limited over WebSocket', async () => {
     const userDataPath = mkdtempSync(join(tmpdir(), 'orca-runtime-rpc-'))
     const writes: { terminal: string; text: string }[] = []

src/main/runtime/runtime-rpc.ts

@@ -894,7 +894,10 @@ export class OrcaRuntimeRpcServer {
           onReady: () => {
             // Why: first authenticated mobile/remote client (direct WS and
             // cloud relay both attach here) starts path-candidate tracking.
-            this.runtime.activateRecentPtyPathCandidateTracking()
+            // Activation is a local-host concern: candidate buffers live on the
+            // buffer-owning host's runtime, so a remote runtime proxy may
+            // legitimately lack this method (its own server activates it).
+            this.runtime.activateRecentPtyPathCandidateTracking?.()
             this.mobileRelayPairingProvider?.onDemandStateChanged?.()
           },
           onClose: (socket, hasOtherConnections) => {