test(run-store): assert the legacy store is untouched when completing a NEW batch item

Broadens the batch-item misroute regression guard: completing a NEW-resident item must update #new and leave #legacy with zero matching rows.

Author: d-cs

internal-packages/run-store/src/runOpsStore.batchItemMisroute.test.ts

@@ -88,6 +88,8 @@ describe("run-ops split — completing a batch item routes by the batch id, not
       expect(result.count).toBe(1);
       const onNew = await prisma17.batchTaskRunItem.findUnique({ where: { id: item.id } });
       expect(onNew?.status).toBe("COMPLETED");
+      // Legacy was never touched: no phantom/double-routed item update on #legacy.
+      expect(await prisma14.batchTaskRunItem.count({ where: { batchTaskRunId: batchId } })).toBe(0);
     }
   );
 });