[BUG]: core migration generator (script/migration.ts) fails on Windows with ENOENT

Description

Running bun script/migration.ts --name <anything> from packages/core on Windows fails after drizzle-kit generates the migration:

[✓] Your SQL migration ➜ E:\Temp\opencode-core-migration-XXXX\incremental\<name>\migration.sql 🚀

ENOENT: no such file or directory, open 'E:\Temp\...\incremental\<name>\migration.sql\migration.sql'

Note the doubled migration.sql\migration.sql — the script's generatedMigrations() helper finds files via new Bun.Glob("*/migration.sql").scan(), which yields backslash-separated paths on Windows. file.split("/")[0] then fails to isolate the directory name, so <dir>\migration.sql is used as the migration name and every subsequent path join is wrong. The same broken split also affects --check, so the schema-consistency gate can't pass on Windows either.

Fix is to split on both separators: file.split(/[\\/]/)[0].

Plugins

None.

OpenCode version

v1.18.18 (dev checkout, packages/core script).

Steps to reproduce

1. On Windows, in a dev checkout of the repo, edit packages/core/src/session/sql.ts (any schema change).
2. cd packages/core && bun script/migration.ts --name test_idx.
3. drizzle-kit succeeds, then the script dies with ENOENT before writing any files.

Screenshot and/or share link

N/A (CLI output above).

Operating System

Windows 11 (Bun 1.3.9). Works fine on Linux/macOS where glob paths use /.

Terminal

Windows Terminal.