Fix force-stop daemon to handle lock contention gracefully

When cleanupWorkspaceDaemonFiles fails to acquire the daemon registry
lock, forceStopDaemon now catches the error and falls back to directly
removing the socket file. This preserves the force-stop contract that
cleanup must succeed even under contention, which is critical since
force-stop is the fallback path when graceful shutdown fails.

Author: cursoragent

src/cli/daemon-control.ts

@@ -51,11 +51,20 @@ export async function forceStopDaemon(socketPath: string): Promise<void> {
     await new Promise((resolve) => setTimeout(resolve, 500));
   }
   if (entry) {
-    cleanupWorkspaceDaemonFiles(entry.workspaceKey, {
-      pid: entry.pid,
-      socketPath,
-      allowLiveOwner: true,
-    });
+    try {
+      cleanupWorkspaceDaemonFiles(entry.workspaceKey, {
+        pid: entry.pid,
+        socketPath,
+        allowLiveOwner: true,
+      });
+    } catch {
+      // Lock contention: fall back to direct socket removal.
+      try {
+        unlinkSync(socketPath);
+      } catch {
+        // Socket may already be gone.
+      }
+    }
   } else {
     // Registry entry missing; cannot derive workspace key from socket path alone.
     // Clean up the socket file directly.