docs(cli): correct stale --prisma copy now that prisma-next v3 has shipped

Dan's review on #691: the `stash eql migration --prisma` copy said the flag
"ships with prisma-next EQL v3 support" / "not available yet" — but that support
has shipped (#655/#683/#685), and Prisma Next installs EQL v3 through its OWN
migration system (`prisma-next migration apply`), not through this command.

Reframed all five spots to current reality (not "coming soon", but "use
prisma-next migration apply"): the user-facing message + its doc comment, the
`eqlMigrationCommand` code comment, the `--prisma` flag help in the registry,
the changeset, and the stash-cli skill (which ships to customers).

No behaviour change — `--prisma` still fails with a pointer. Build + 566 tests green.

Claude-Session: https://claude.ai/code/session_01MxTTPaPP16m6br7Hoab94w

Author: coderdan

.changeset/eql-migration-command.md

@@ -17,5 +17,6 @@ the `cs_migrations` tracking schema, so a single `drizzle-kit migrate` covers
 everything `stash encrypt …` needs. `--supabase` appends the `eql_v3` +
 `eql_v3_internal` role grants for PostgREST/RLS access.
 
-`--prisma` is registered but not available yet — it ships with prisma-next EQL v3
-support and fails with a pointer until then.
+`--prisma` is registered but not supported — Prisma Next installs EQL v3 through
+its own migration system (`prisma-next migration apply`), so the command points
+users there instead of emitting a migration.

packages/cli/src/cli/registry.ts

@@ -394,7 +394,7 @@ export const registry: CommandGroup[] = [
           {
             name: '--prisma',
             description:
-              'Emit a Prisma Next migration (ships with prisma-next EQL v3 support; not available yet).',
+              'Not supported — Prisma Next installs EQL v3 via its own migration system (`prisma-next migration apply`); fails with a pointer.',
           },
           {
             name: '--supabase',

packages/cli/src/commands/eql/migration.ts

@@ -94,9 +94,9 @@ export async function eqlMigrationCommand(
   }
 
   if (options.prisma) {
-    // The prisma-next emitter ships stacked on the prisma-next EQL v3 work
-    // (PR #655); it can't install a v3 schema that doesn't exist on that
-    // surface yet. Fail loudly with a pointer rather than emit a broken file.
+    // Prisma Next installs EQL v3 through its own migration system
+    // (`prisma-next migration apply`, shipped in #655), so this command has
+    // nothing to emit for it. Fail loudly with a pointer rather than a no-op.
     p.log.error(messages.eql.migrationPrismaUnavailable)
     throw new CliExit(1)
   }

packages/cli/src/messages.ts

@@ -73,13 +73,13 @@ export const messages = {
     migrationOneTarget:
       'Pass exactly one target: `--drizzle` or `--prisma`, not both.',
     /**
-     * `--prisma` isn't wired yet — Prisma Next installs EQL v3 through its own
-     * migration system (`prisma-next migration apply`), so the CLI emitter is
-     * not needed there today. Points at the tracking issue so the failure is
-     * actionable.
+     * `--prisma` is registered but has nothing to emit: Prisma Next installs
+     * EQL v3 through its own migration system (`prisma-next migration apply`),
+     * so this command doesn't generate a Prisma migration. The message points
+     * users at the path that does the work.
      */
     migrationPrismaUnavailable:
-      '`stash eql migration --prisma` is not available yet — Prisma Next installs EQL v3 via its own migration system (`prisma-next migration apply`, see cipherstash/stack#690). Use `--drizzle` today.',
+      '`stash eql migration --prisma` is not supported — Prisma Next installs EQL v3 through its own migration system. Run `prisma-next migration apply` instead. Use `--drizzle` for a Drizzle project.',
     /** `--name` carried characters outside `[A-Za-z0-9_-]`. */
     migrationBadName:
       'Migration name must contain only letters, numbers, dashes, and underscores.',

skills/stash-cli/SKILL.md

@@ -380,7 +380,7 @@ stash eql migration --drizzle --supabase   # also grant eql_v3 to anon/authentic
 | Flag | Description |
 |---|---|
 | `--drizzle` | Emit a Drizzle custom migration (via `drizzle-kit generate --custom`, then inject the SQL). Requires `drizzle-kit`. |
-| `--prisma` | Emit a Prisma Next migration. **Not available yet** — ships with prisma-next EQL v3 support; fails with a pointer until then. |
+| `--prisma` | **Not supported.** Prisma Next installs EQL v3 through its own migration system — run `prisma-next migration apply` instead. The flag fails with a pointer. |
 | `--supabase` | Append the Supabase role grants (`eql_v3` + `eql_v3_internal` → `anon`, `authenticated`, `service_role`). Harmless when you connect directly as `postgres`; needed when the same tables are reached via PostgREST/RLS. |
 | `--name <name>` | Migration name (Drizzle). Default `install-eql`. |
 | `--out <path>` | Output directory (Drizzle). Default `drizzle`. |