test(run-store): assert every lock column rolls back, not just the run status

The lockRunToWorker atomicity test proxied "fully rolled back" through the run
status alone, which would miss a partial rollback that leaves lockedAt/lockedById
and friends populated. Assert those columns are null too.

Author: d-cs

internal-packages/run-store/src/PostgresRunStore.writeAtomicity.test.ts

@@ -701,8 +701,13 @@ describe("createExecutionSnapshot / lockRunToWorker write the snapshot and its l
 
       const snap = await prisma17.taskRunExecutionSnapshot.findUnique({ where: { id: snapshotId } });
       expect(snap).toBeNull();
+      // The whole lock write must roll back, not just the status: no lock columns may leak through.
       const run = await prisma17.taskRun.findUniqueOrThrow({ where: { id: runId } });
       expect(run.status).not.toBe("DEQUEUED");
+      expect(run.lockedAt).toBeNull();
+      expect(run.lockedById).toBeNull();
+      expect(run.lockedToVersionId).toBeNull();
+      expect(run.lockedQueueId).toBeNull();
     }
   );
 });