test(cli): the platform-global drop-gate pin reads the refusal's new detail

The integration pin still matched the withdrawn os migrate
organization-ownership --apply in the --json detail; it now asserts the
ceremony is named and no step of the command 18.0 refuses is.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SYEJqDL3NXxrJRBVqaMu9T

Author: claude

packages/cli/src/utils/organization-ownership-platform-global-column-drop.integration.test.ts

@@ -436,7 +436,9 @@ describe('os migrate apply --allow-destructive: the organization_id drop on a ho
       created: [],
       marker: null,
     });
-    expect(payload.detail).toMatch(/os migrate organization-ownership --apply/);
+    expect(payload.detail).toMatch(/organization-ownership ceremony/);
+    // 18.0 refuses `os migrate organization-ownership` on every database: the refusal names no step of it.
+    expect(payload.detail).not.toMatch(/os migrate organization-ownership|--plan-file|organization-ownership --out/);
     // The drops the refusal held back are the ones the drift offered.
     expect(organizationDropsIn(payload.skipped)).toEqual([...DECLARED].sort());
     for (const table of HOST_OBJECTS) expect(hasOrganizationColumn(dbFile, table), table).toBe(true);