fix(cli): datatable migrate up/down default to main datatable, not all

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

cli/src/commands/datatable/datatable.ts

@@ -55,29 +55,14 @@ function migrateNew(
   createMigration(opts.datatable ?? DEFAULT_DATATABLE_NAME, name);
 }
 
-// Resolve the datatables to operate on: the one passed via --datatable, or every
-// datatable in the workspace when none is given.
-async function resolveDatatables(
-  workspaceId: string,
-  datatable?: string,
-): Promise<string[]> {
-  if (datatable) return [datatable];
-  const items = await wmill.listDataTables({ workspace: workspaceId });
-  return items.map((x) => x.name);
-}
-
 async function migrateUp(opts: GlobalOptions & { datatable?: string }) {
   const workspace = await resolveWorkspace(opts);
   await requireLogin(opts);
-  const targets = await resolveDatatables(workspace.workspaceId, opts.datatable);
-  if (targets.length === 0) {
-    log.info("No datatables in the workspace");
-    return;
-  }
+  const dt = opts.datatable ?? DEFAULT_DATATABLE_NAME;
   // Reject malformed local migrations (duplicate timestamps, orphan downs) before
   // pushing — the same check `wmill sync push` runs — so a duplicate timestamp
   // can't silently overwrite one migration on upsert.
-  const errors = validateLocalMigrations(new Set(targets));
+  const errors = validateLocalMigrations(new Set([dt]));
   if (errors.length > 0) {
     log.error(
       "Invalid datatable migrations, aborting:\n" +
@@ -85,25 +70,17 @@ async function migrateUp(opts: GlobalOptions & { datatable?: string }) {
     );
     process.exit(1);
   }
-  for (const dt of targets) {
-    // Push any locally-created/edited migration files first (without running
-    // them), so `migrate up` works even before a `wmill sync push`.
-    await pushLocalMigrations(workspace.workspaceId, dt);
-    await runMigrations(workspace.workspaceId, dt);
-  }
+  // Push any locally-created/edited migration files first (without running
+  // them), so `migrate up` works even before a `wmill sync push`.
+  await pushLocalMigrations(workspace.workspaceId, dt);
+  await runMigrations(workspace.workspaceId, dt);
 }
 
 async function migrateDown(opts: GlobalOptions & { datatable?: string }) {
   const workspace = await resolveWorkspace(opts);
   await requireLogin(opts);
-  const targets = await resolveDatatables(workspace.workspaceId, opts.datatable);
-  if (targets.length === 0) {
-    log.info("No datatables in the workspace");
-    return;
-  }
-  for (const dt of targets) {
-    await rollbackMigrations(workspace.workspaceId, dt);
-  }
+  const dt = opts.datatable ?? DEFAULT_DATATABLE_NAME;
+  await rollbackMigrations(workspace.workspaceId, dt);
 }
 
 const migrateCommand = new Command()
@@ -117,20 +94,20 @@ const migrateCommand = new Command()
   .action(migrateNew as any)
   .command(
     "up",
-    "apply all pending migrations to every datatable (or one via --datatable)",
+    "apply all pending migrations to the main datatable (or one via --datatable)",
   )
   .option(
     "-d --datatable <datatable:string>",
-    "Target a specific datatable (default: all datatables in the workspace)",
+    "Target datatable (default: main)",
   )
   .action(migrateUp as any)
   .command(
     "down",
-    "roll back the most recent migration on every datatable (or one via --datatable)",
+    "roll back the most recent migration on the main datatable (or one via --datatable)",
   )
   .option(
     "-d --datatable <datatable:string>",
-    "Target a specific datatable (default: all datatables in the workspace)",
+    "Target datatable (default: main)",
   )
   .action(migrateDown as any);
 

cli/src/guidance/skills.gen.ts

@@ -6594,10 +6594,10 @@ datatable related commands
 - \`datatable migrate\` - manage datatable migrations
   - \`datatable migrate new <name:string>\` - scaffold a new migration (.up.sql / .down.sql files)
     - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
-  - \`datatable migrate up\` - apply all pending migrations to every datatable (or one via --datatable)
-    - \`-d --datatable <datatable:string>\` - Target a specific datatable (default: all datatables in the workspace)
-  - \`datatable migrate down\` - roll back the most recent migration on every datatable (or one via --datatable)
-    - \`-d --datatable <datatable:string>\` - Target a specific datatable (default: all datatables in the workspace)
+  - \`datatable migrate up\` - apply all pending migrations to the main datatable (or one via --datatable)
+    - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
+  - \`datatable migrate down\` - roll back the most recent migration on the main datatable (or one via --datatable)
+    - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
 - \`datatable create [name:string]\` - register a datatable database in the workspace (default: instance-backed 'main') so scripts can use datatable://<name>
   - \`--resource <resource:string>\` - Back the datatable with an existing postgresql resource path instead of the instance database
   - \`--force\` - Allow adding to a workspace that already has datatables (fork metadata on existing ones is not preserved)

system_prompts/auto-generated/cli/cli-commands.md

@@ -80,10 +80,10 @@ datatable related commands
 - `datatable migrate` - manage datatable migrations
   - `datatable migrate new <name:string>` - scaffold a new migration (.up.sql / .down.sql files)
     - `-d --datatable <datatable:string>` - Target datatable (default: main)
-  - `datatable migrate up` - apply all pending migrations to every datatable (or one via --datatable)
-    - `-d --datatable <datatable:string>` - Target a specific datatable (default: all datatables in the workspace)
-  - `datatable migrate down` - roll back the most recent migration on every datatable (or one via --datatable)
-    - `-d --datatable <datatable:string>` - Target a specific datatable (default: all datatables in the workspace)
+  - `datatable migrate up` - apply all pending migrations to the main datatable (or one via --datatable)
+    - `-d --datatable <datatable:string>` - Target datatable (default: main)
+  - `datatable migrate down` - roll back the most recent migration on the main datatable (or one via --datatable)
+    - `-d --datatable <datatable:string>` - Target datatable (default: main)
 - `datatable create [name:string]` - register a datatable database in the workspace (default: instance-backed 'main') so scripts can use datatable://<name>
   - `--resource <resource:string>` - Back the datatable with an existing postgresql resource path instead of the instance database
   - `--force` - Allow adding to a workspace that already has datatables (fork metadata on existing ones is not preserved)

system_prompts/auto-generated/prompts.ts

@@ -2756,10 +2756,10 @@ datatable related commands
 - \`datatable migrate\` - manage datatable migrations
   - \`datatable migrate new <name:string>\` - scaffold a new migration (.up.sql / .down.sql files)
     - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
-  - \`datatable migrate up\` - apply all pending migrations to every datatable (or one via --datatable)
-    - \`-d --datatable <datatable:string>\` - Target a specific datatable (default: all datatables in the workspace)
-  - \`datatable migrate down\` - roll back the most recent migration on every datatable (or one via --datatable)
-    - \`-d --datatable <datatable:string>\` - Target a specific datatable (default: all datatables in the workspace)
+  - \`datatable migrate up\` - apply all pending migrations to the main datatable (or one via --datatable)
+    - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
+  - \`datatable migrate down\` - roll back the most recent migration on the main datatable (or one via --datatable)
+    - \`-d --datatable <datatable:string>\` - Target datatable (default: main)
 - \`datatable create [name:string]\` - register a datatable database in the workspace (default: instance-backed 'main') so scripts can use datatable://<name>
   - \`--resource <resource:string>\` - Back the datatable with an existing postgresql resource path instead of the instance database
   - \`--force\` - Allow adding to a workspace that already has datatables (fork metadata on existing ones is not preserved)

system_prompts/auto-generated/skills/cli-commands/SKILL.md

@@ -85,10 +85,10 @@ datatable related commands
 - `datatable migrate` - manage datatable migrations
   - `datatable migrate new <name:string>` - scaffold a new migration (.up.sql / .down.sql files)
     - `-d --datatable <datatable:string>` - Target datatable (default: main)
-  - `datatable migrate up` - apply all pending migrations to every datatable (or one via --datatable)
-    - `-d --datatable <datatable:string>` - Target a specific datatable (default: all datatables in the workspace)
-  - `datatable migrate down` - roll back the most recent migration on every datatable (or one via --datatable)
-    - `-d --datatable <datatable:string>` - Target a specific datatable (default: all datatables in the workspace)
+  - `datatable migrate up` - apply all pending migrations to the main datatable (or one via --datatable)
+    - `-d --datatable <datatable:string>` - Target datatable (default: main)
+  - `datatable migrate down` - roll back the most recent migration on the main datatable (or one via --datatable)
+    - `-d --datatable <datatable:string>` - Target datatable (default: main)
 - `datatable create [name:string]` - register a datatable database in the workspace (default: instance-backed 'main') so scripts can use datatable://<name>
   - `--resource <resource:string>` - Back the datatable with an existing postgresql resource path instead of the instance database
   - `--force` - Allow adding to a workspace that already has datatables (fork metadata on existing ones is not preserved)