Use the server suite timeout for Cursor sandbox qualification

The loaded CI shard exceeded this test's shorter 10-second override. Inherit the existing 15-second server test limit, matching the adjacent sandbox case, while retaining all command and environment assertions. Record the original CI interruption and timeout separately from live qualification.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/plans/2026-10-03-cursor-production-readiness.md

@@ -83,6 +83,14 @@ artifacts. Final PR checks validate the combined source separately. Release the
 qualified package/image pair above; any later package or image needs release
 verification against its own identity.
 
+The first CI run of the merged source lost five workers to simultaneous runner
+shutdowns. A single infrastructure repeat recovered four jobs; the remaining
+server shard hit a 10-second override in the legacy Cursor sandbox command test.
+That unchanged file passed all five cases in a focused local run. The test now
+inherits the server suite's existing 15-second limit, as its adjacent explicit
+command case already does. Assertions and production code are unchanged. The
+shutdowns and timeout remain recorded; they are separate from the live campaign.
+
 ### Final live acceptance matrix
 
 All 18 required cells passed, including cleanup: nine local and nine Daytona.

server/src/__tests__/cursor-local-execute.test.ts

@@ -388,7 +388,7 @@ describe("cursor execute", () => {
       else process.env.HOME = previousHome;
       await fs.rm(root, { recursive: true, force: true });
     }
-  }, 10_000);
+  });
 
   it("keeps explicit command overrides for remote sandbox execution", async () => {
     const root = await fs.mkdtemp(path.join(os.tmpdir(), "paperclip-cursor-sandbox-explicit-"));