Rename package names for 1.0

[coderdan]

@cipherstash/prisma-next → @cipherstash/prisma
@cipherstash/stack-drizzle → @cipherstash/drizzle
@cipherstash/stack-supabase → @cipherstash/supabase

The older @cipherstash/supabase and @cipherstash/drizzle packages were based on the legacy protect and V2 stuff.

[coderdan]

Plan revised: adapters keep the stack- prefix

The renames as originally written here turned out not to be viable, and after internal discussion we've settled on the opposite convention — every adapter carries the stack- prefix:

package	outcome
@cipherstash/prisma-next	renamed @cipherstash/stack-prisma (PR #844)
@cipherstash/stack-drizzle	unchanged
@cipherstash/stack-supabase	unchanged

Why not the bare names?

@cipherstash/drizzle is blocked outright. The legacy @cipherstash/protect-based package already occupies that npm name with published versions 0.1.0–3.0.3 (plus 3.0.4-rc.*). npm forbids republishing an existing version, so the renamed package could never ship 1.0.0 under that name. And because all five train packages ride one fixed changeset group pinned to 1.0.0 for GA (#843), the workarounds were all bad: jump the whole train to 4.0.0, or break drizzle out of the fixed group and have it version out of lockstep.

Mixed naming is worse than either pure convention. With drizzle stuck on stack-drizzle, renaming only supabase and prisma would have shipped 1.0 with two bare-named adapters and one prefixed — a permanent inconsistency between name and version story. Uniform stack-* keeps the name↔version relationship consistent across the train, so stack-prisma is the one actual rename.

Scope notes

• prisma-next survives as a term wherever it names the external Prisma Next framework (@prisma-next/*): the stash init --prisma-next flag and provider id, prisma-next.config.ts detection, and the prisma-next CLI. Those are the framework's surface, not ours — only our extension package is renamed.
• The stash-prisma-next skill becomes stash-prisma, matching the stash-drizzle / stash-supabase skill naming.
• @cipherstash/stack-prisma is unclaimed on npm, so it publishes cleanly as 1.0.0 when chore(release): exit changesets pre mode — next release is 1.0.0 #843 exits pre mode (verified with an isolated changeset version run).
• Follow-ups after GA: npm deprecate @cipherstash/prisma-next pointing at the new name, and a README-only @cipherstash/drizzle@3.0.4 republish pointing the legacy package prominently at @cipherstash/stack-drizzle (prepared and ready to publish).

Implementation: PR #844 (merge before #843).