Summary
SKILL_MAP is typed Record<Integration, …> but omits the 'prisma-next' key. installSkills and the AGENTS.md builder do SKILL_MAP[integration] → undefined → not iterable for any repo the CLI detects as Prisma Next (auto-detected via detectPrismaNext).
tsc catches the missing key, but the build (tsup) transpiles without type-checking, so it shipped in rc.2 — reachable by any Prisma user running stash init, stash plan, or stash impl.
Companion to #655, which releases the @cipherstash/prisma-next EQL v3 package but touches no CLI code, so the CLI-side Prisma Next experience was still broken.
Expected
stash init/plan/impl should not crash in Prisma Next projects.- An unmapped
Integration should degrade to the base skill set rather than throw.
- A
stash-prisma-next skill should document the EQL v3 surface (domain-named column types, cipherstashFromStackV3 wiring, eql* query operators, and EQL install via prisma-next migration apply, not stash eql install).
Root cause note
The underlying gap is that the CLI package has no tsc --noEmit gate in CI, so a type error the compiler catches still ships through tsup.
Resolution
Fixed in #683 — added the prisma-next SKILL_MAP entry, routed both consumers through a skillsFor() helper that falls back for unmapped integrations, and added the new stash-prisma-next skill. Closes the rc.2 M1 finding.
Summary
SKILL_MAPis typedRecord<Integration, …>but omits the'prisma-next'key.installSkillsand the AGENTS.md builder doSKILL_MAP[integration]→undefined→not iterablefor any repo the CLI detects as Prisma Next (auto-detected viadetectPrismaNext).tsccatches the missing key, but the build (tsup) transpiles without type-checking, so it shipped in rc.2 — reachable by any Prisma user runningstash init,stash plan, orstash impl.Companion to #655, which releases the
@cipherstash/prisma-nextEQL v3 package but touches no CLI code, so the CLI-side Prisma Next experience was still broken.Expected
stash init/plan/implshould not crash in Prisma Next projects.Integrationshould degrade to the base skill set rather than throw.stash-prisma-nextskill should document the EQL v3 surface (domain-named column types,cipherstashFromStackV3wiring,eql*query operators, and EQL install viaprisma-next migration apply, notstash eql install).Root cause note
The underlying gap is that the CLI package has no
tsc --noEmitgate in CI, so a type error the compiler catches still ships throughtsup.Resolution
Fixed in #683 — added the
prisma-nextSKILL_MAPentry, routed both consumers through askillsFor()helper that falls back for unmapped integrations, and added the newstash-prisma-nextskill. Closes the rc.2 M1 finding.