Docs/CLI: `prisma-next migration apply` does not exist — use top-level `prisma-next migrate`

[coderdan]

Problem

The Prisma Next guidance prescribes prisma-next migration apply, which does not exist. Prisma Next's apply verb is the top-level prisma-next migrate; migration only groups plan/new/show/status/log/list/graph/check. Running the prescribed command errors:

$ prisma-next migration apply
Unknown command: apply
Use `prisma-next migrate --to <contract>` instead.

Surfaced by the rc.4 skilltester run — found independently by the Codex run at Prisma Next 0.14.0, confirmed against 0.16.0.

Where it appeared

• skills/stash-prisma-next/SKILL.md — quickstart command + two prose references + the description frontmatter
• skills/stash-cli/SKILL.md — two prose references
• packages/prisma-next/README.md — quickstart command
• CLI (user-visible), packages/cli:
  • stash init --prisma-next printed next-steps (init/providers/prisma-next.ts)
  • stash init flag help (cli/registry.ts)
  • stash eql install Prisma-Next refusal message (commands/db/install.ts)
  • install-eql skip message + comments (commands/init/steps/install-eql.ts, init/index.ts)

Fix

Replace with the top-level prisma-next migrate (--yes to skip the confirm prompt in CI) everywhere it's live guidance, and update the CLI unit + e2e assertions that pinned the old string. Historical CHANGELOG entries left as-is (append-only).

Status

Fixed in PR #763 (commit e02c2b93), with a stash + @cipherstash/prisma-next patch changeset. This issue tracks that item on its own; the fix is part of PR #763.