test(platform): read Sandbox drain audit events in request order

The drain audit test took the last row of an unordered operator_events read. Each audit row is inserted and then updated with its outcome, so on a reused PostgreSQL table its physical position can differ from request order. Read the rows by creation time instead.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: Brooooooklyn

platform/packages/api/test/integration/operator-operations.test.ts

@@ -1,5 +1,5 @@
 import { PLATFORM_APPLICATION_KEY } from '@void/platform';
-import { eq, sql } from 'drizzle-orm';
+import { asc, eq, sql } from 'drizzle-orm';
 import {
   afterAll,
   afterEach,
@@ -978,7 +978,12 @@ describe('operator installation-aware system and worker operations', () => {
     expect(JSON.parse((await env.ROUTING.get(SANDBOX_DRAIN_STATE_KEY))!)).toMatchObject({
       state: 'complete',
     });
-    const events = await env.db.select().from(operatorEvents);
+    // Each audit row is inserted, then updated with its outcome, so its physical
+    // position does not follow request order.
+    const events = await env.db
+      .select()
+      .from(operatorEvents)
+      .orderBy(asc(operatorEvents.created_at), asc(operatorEvents.id));
     expect(events).toHaveLength(1 + resumedPages.length);
     expect(events.at(-1)).toEqual(
       expect.objectContaining({