@aburi/effects-prisma 0.3.0 → 0.4.0

package/README.md

@@ -23,6 +23,46 @@ lands there) is a prerequisite, and the target must have at least three
 call in an unrelated file will not false-classify. Bare `$transaction()`
 without a client segment is also skipped.
 
+### Receiver identification
+
+The import gate answers "does this file use Prisma", which a file is free to
+answer yes to while most of its calls belong to something else. `delete`,
+`create` and `update` are shared vocabulary across `Map`, `Set`, the DOM and
+every HTTP router, and `this.<x>.<y>.delete(...)` is everyday TypeScript — so
+the shape plus the gate is not evidence that the receiver is a database client.
+
+Three further checks decide what is recorded:
+
+- **Literal first argument.** A Prisma method takes an options object, an array
+  or a callback — never a bare literal. `this.cache.items.delete("session")` is
+  a `Map`, and is not classified at all.
+- **Receiver name.** The segment before the model — `prisma` in
+  `this.prisma.user.create`, `db` in `db.user.create` — is matched word-wise
+  against the client vocabulary (`prisma` / `db` / `database` / `orm` / `tx` /
+  `trx`), so `prismaClient`, `readReplicaDb` and `_prisma` all count and
+  `cache`, `router`, `store` and `apiClient` do not. `client` is deliberately
+  absent: a resource SDK's `<client>.<resource>.<verb>` is a delegate call's
+  shape exactly, so the entry would hand `apiClient.users.update(payload)` the
+  top tier.
+- **Argument count.** A delegate takes at most one argument, `$transaction`
+  two. More than that is evidence against — but only evidence: `argumentCount`
+  is a syntactic count, and a drop would erase a real write without logging
+  anything, so an overflow costs the tier instead.
+
+A match on all three gives `confidence: "high"`; anything short of that still
+records the effect, at `confidence: "medium"`.
+
+The `medium` tier is deliberate. Without the AST — which effect plugins never
+see — a client bound under a house naming convention and an unrelated object of
+the same shape are indistinguishable from the callee string, so the uncertainty
+is stated rather than resolved by guessing. A receiver the language plugin
+flagged as dynamic (`getPrisma().user.create()`) is capped at `medium` for the
+same reason: the name in the target is a collapsed expression, not a binding.
+
+Naming your client something this vocabulary does not know is not an error — it
+costs the effect its `high` tier, and the table in `src/receivers.ts` is one
+literal list if a house convention deserves to be in it.
+
 ## Install
 
 ```bash

package/dist/index.d.mts

@@ -1,4 +1,4 @@
-import { CallCandidate, ClassifyContext, EffectClassification, EffectPlugin, ImportEdge, PluginContext } from "@aburi/types";
+import { CallCandidate, ClassifyContext, Confidence, EffectClassification, EffectPlugin, ImportEdge, PluginContext } from "@aburi/types";
 
 //#region src/classify.d.ts
 /**
@@ -14,10 +14,27 @@ import { CallCandidate, ClassifyContext, EffectClassification, EffectPlugin, Imp
  *          from false-classifying.
  *        - `<...>.$transaction` (2+ segments) — the top-level transaction API on the
  *          client itself.
- *   3. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the
+ *   3. A literal first argument rules the call out — no Prisma method takes one — and the
+ *      receiver and the argument count decide the tier (`classificationConfidence`).
+ *   3a. A model segment that names nothing — `prisma[model].create(…)`, which arrives as
+ *      `prisma.<computed>.create` — supplies the third segment without supplying a model, so
+ *      the receiver has to carry the claim on its own: it must name a client binding, or the
+ *      call is not classified at all.
+ *   4. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the
  *      language plugin's contract is a normalized non-empty callee, so a violation
  *      here is an upstream bug we surface loudly instead of silently miscategorizing.
  *
+ * **The import gate is not a receiver check.** It answers "does this file use Prisma",
+ * which a file is free to answer yes to while most of its calls belong to something else:
+ * `this.cache.items.delete(key)` is a `Map`, `session.user.update(fields)` is an object,
+ * and both have three segments and a delegate verb. Step 3 is what keeps those from being
+ * recorded as `db.write` at the tier a hand-annotated effect gets — a claim that
+ * would then propagate through the call graph and into the diff. Where the receiver names
+ * the client, the classification still lands at `high`; where it does not, the effect is
+ * still emitted but at `medium`, because a syntactic classifier cannot tell a client under
+ * a house naming convention apart from an unrelated object of the same shape, and silently
+ * dropping the first is as wrong as confidently claiming the second.
+ *
  * The function is a pure lookup — no I/O, no state, no async — matching the per-call
  * timeout budget the core enforces (effect-plugin.md §5.1.1).
  */
@@ -149,5 +166,89 @@ declare class PrismaEffectsPlugin implements EffectPlugin {
  */
 declare const prismaEffectsPlugin: PrismaEffectsPlugin;
 //#endregion
-export { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME, PRISMA_READ_METHODS, PRISMA_TRANSACTION_METHOD, PRISMA_WRITE_METHODS, PrismaEffectsPlugin, type PrismaReadMethod, type PrismaTransactionMethod, type PrismaWriteMethod, classifyPrismaCall, effectsPrismaManifest, hasPrismaImport, isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod, prismaEffectsPlugin };
-//# sourceMappingURL=index.d.mts.map
+//#region src/receivers.d.ts
+/**
+ * The words a Prisma Client binding is spelled with.
+ *
+ * A classifier only ever sees the callee string, so "which local binding holds the client"
+ * is not a question it can answer outright — the assignment that created the binding
+ * (`const prisma = new PrismaClient()`, `constructor(private prisma: PrismaClient)`) is in
+ * the AST, which effect plugins deliberately never see (effect-plugin.md §11.1). What the
+ * callee does carry is the name the author gave that binding, and Prisma's own docs, the
+ * generated client, and every published starter spell it from this handful of words.
+ *
+ * Matching is per word (`identifierWords`), so `prismaClient`, `readReplicaDb`, `_prisma`,
+ * `dbClient` and `prismaRo` all count, while `cache`, `router`, `items` and `store` do not.
+ * That is the whole point: `delete`, `create` and `update` are shared vocabulary across
+ * `Map`, `Set`, the DOM and every HTTP router, and `this.<x>.<y>.delete(...)` is everyday
+ * TypeScript, so the method name plus a file-level import gate is not evidence that the
+ * receiver is a database client.
+ *
+ * `tx` / `trx` are here because the interactive-transaction callback rebinds the client
+ * under its own parameter name — `prisma.$transaction(async (tx) => tx.user.create(...))` —
+ * and that call is as much a write as the one outside it.
+ *
+ * **What is deliberately not here.** A word only earns a place if it separates a database
+ * client from everything else that shares Prisma's verbs:
+ *
+ * - `client` matches `apiClient`, `httpClient`, `redisClient`, `sdkClient`. A resource
+ *   SDK's `<client>.<resource>.<verb>` is spelled exactly like a Prisma delegate, so
+ *   `apiClient.users.update(payload)` would land at the tier a hand-annotated effect gets
+ *   — the bug class this module exists to close. `prismaClient`, `dbClient` and `_prisma`
+ *   match on `prisma` or `db` regardless; a bare `client.user.create()` is all the entry
+ *   would have bought.
+ * - `transaction` matches the domain nouns `paymentTransaction` / `transactionLog` more
+ *   often than it names a client, and `tx` / `trx` already cover the callback parameter.
+ * - `datasource` was unreachable as anyone spells it: `identifierWords("dataSource")` is
+ *   `["data", "source"]`, so only the all-lowercase form ever matched.
+ *
+ * A literal source of truth, like every other vocabulary in this package: extending it for
+ * a house naming convention is a table edit in exactly one place.
+ */
+declare const PRISMA_CLIENT_WORDS_LIST: readonly ["prisma", "db", "database", "orm", "tx", "trx"];
+type PrismaClientWord = (typeof PRISMA_CLIENT_WORDS_LIST)[number];
+declare const PRISMA_CLIENT_WORDS: ReadonlySet<PrismaClientWord>;
+/** True when `segment` spells a word this package recognizes as a Prisma client binding. */
+declare function namesPrismaClient(segment: string): boolean;
+/**
+ * The most arguments a Prisma call takes before it stops looking like Prisma's own API.
+ *
+ * A model delegate method takes a single options object (`{ where }`, `{ data }`) or
+ * nothing at all. `$transaction` takes two: the callback form carries an options object
+ * (`$transaction(fn, { timeout })`), while the array form takes one.
+ */
+declare const PRISMA_DELEGATE_MAX_ARGUMENTS = 1;
+declare const PRISMA_TRANSACTION_MAX_ARGUMENTS = 2;
+/**
+ * How much the call backs the classification its method name suggests.
+ *
+ * `high` needs every signal to agree: the receiver segment names a client binding, the
+ * receiver is a binding at all rather than a collapsed expression, and the call takes no
+ * more arguments than the API allows. Anything else is `medium` — the effect is still
+ * recorded, with the uncertainty stated:
+ *
+ * - **An unrecognized receiver** is either a binding this plugin cannot place by name (a
+ *   house convention, a client reached through a wrapper) or an unrelated object that
+ *   happens to share the verb. A syntactic classifier cannot separate those two without
+ *   the binding table it has no access to, so it says so in `confidence` rather than
+ *   picking one and being confidently wrong half the time. `medium` is the same tier
+ *   `@aburi/framework-express` uses for a route that matches the shape without an import
+ *   anchor.
+ * - **A dynamic receiver** (`getClient().user.create()`, `clients[0].user.create()`) is
+ *   capped at `medium` whatever it is spelled: normalization collapsed an expression down
+ *   to a name, so the name in `target` is not a binding and reading it as one would
+ *   manufacture evidence out of a call the language plugin already flagged as unresolvable
+ *   (`CallCandidate.dynamicReceiver`).
+ * - **An argument list longer than the API takes** is evidence against, not proof:
+ *   `argumentCount` comes from a syntactic walk, and this classifier is the first thing to
+ *   read it as a signature. Treating an overflow as "not a Prisma call" would let one
+ *   miscount erase a real write and log nothing — the failure mode with no trace. So it
+ *   costs the tier instead, which is this module's own rule applied to its own inputs.
+ *
+ * A literal first argument is the one shape that is *not* a tier question, and it is not
+ * decided here: `prisma.user.delete("u1")` is a type error rather than a Prisma call, so
+ * `classifyPrismaCall` rejects it outright.
+ */
+declare function classificationConfidence(clientSegment: string | undefined, call: CallCandidate, maxArguments: number): Confidence;
+//#endregion
+export { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME, PRISMA_CLIENT_WORDS, PRISMA_DELEGATE_MAX_ARGUMENTS, PRISMA_READ_METHODS, PRISMA_TRANSACTION_MAX_ARGUMENTS, PRISMA_TRANSACTION_METHOD, PRISMA_WRITE_METHODS, type PrismaClientWord, PrismaEffectsPlugin, type PrismaReadMethod, type PrismaTransactionMethod, type PrismaWriteMethod, classificationConfidence, classifyPrismaCall, effectsPrismaManifest, hasPrismaImport, isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod, namesPrismaClient, prismaEffectsPlugin };

package/dist/index.mjs

@@ -1,215 +1 @@
-import { assertNonEmptySegments, hasMatchingImport } from "@aburi/plugin-registry/plugin-input";
-
-//#region src/constants.ts
-/**
-* Package-relative plugin name. Doubles as the prefix of every thrown message, so a caught
-* exception names the plugin that rejected the input. `manifest.ts` declares the same
-* string as `name`.
-*/
-const EFFECTS_PRISMA_PLUGIN_NAME = "effects-prisma";
-/**
-* Shared derivedBy namespace. `manifest.ts` imports this same const for its
-* `derivedByPrefixes` entry, so the classifier's tag builder and the registry
-* declaration cannot drift.
-*/
-const EFFECTS_PRISMA_DERIVED_BY_PREFIX = "effects-plugin:prisma";
-
-//#endregion
-//#region src/imports.ts
-/**
-* npm module specifiers that expose a `PrismaClient`. Any file that pulls in one of
-* these is treated as a Prisma consumer; files that reference the identifier without
-* importing Prisma are ignored so an unrelated `db.user.findMany()` from another ORM
-* does not get miscategorized.
-*
-* - `@prisma/client` — the default Prisma Client entry since v4.
-* - `@prisma/client/edge` — the Edge runtime entry used by Vercel Edge, Cloudflare
-*   Workers, and Prisma Accelerate. Different bundle, same delegate surface.
-*
-* The set is a literal source of truth. Extending the plugin for community builds or a
-* future Prisma bundle is a table edit here.
-*/
-const PRISMA_CLIENT_MODULES_LIST = ["@prisma/client", "@prisma/client/edge"];
-const PRISMA_CLIENT_MODULES = new Set(PRISMA_CLIENT_MODULES_LIST);
-/** Membership test against the closed set of Prisma Client entry points. */
-function isPrismaClientModule(source) {
-	return PRISMA_CLIENT_MODULES.has(source);
-}
-/**
-* True when the file's import list contains any recognized Prisma Client module. An
-* empty source string on an ImportEdge is rejected by the shared guard: the language
-* plugin's contract is to emit normalized non-empty specifiers, and treating `""` as
-* unmatched would silently hide upstream bugs.
-*
-* `filePath` is required and threaded into any thrown error message so a caught
-* exception in production tooling (CI logs, error reporters) points directly at the
-* offending source file rather than a bare "empty source" string.
-*/
-function hasPrismaImport(imports, filePath) {
-	return hasMatchingImport(imports, {
-		plugin: EFFECTS_PRISMA_PLUGIN_NAME,
-		filePath
-	}, isPrismaClientModule);
-}
-
-//#endregion
-//#region src/methods.ts
-/**
-* Prisma model delegate method vocabulary.
-*
-* Each `_LIST` is the single source of truth — the union type and the runtime `Set` are
-* both derived from it, so extending the vocabulary is a table edit in exactly one
-* place. Extending as Prisma ships new delegate methods keeps the classifier honest
-* without a code rewrite.
-*
-* Only methods that map cleanly onto core `db.read` / `db.write` vocabulary are listed.
-* Delegate helpers whose semantics do not match (metadata accessors, raw SQL escapes,
-* connection lifecycle) stay out — the plugin returns `null` for them so downstream
-* effect plugins get a chance.
-*/
-const PRISMA_READ_METHODS_LIST = [
-	"findUnique",
-	"findUniqueOrThrow",
-	"findFirst",
-	"findFirstOrThrow",
-	"findMany",
-	"count",
-	"aggregate",
-	"groupBy"
-];
-const PRISMA_WRITE_METHODS_LIST = [
-	"create",
-	"createMany",
-	"createManyAndReturn",
-	"update",
-	"updateMany",
-	"updateManyAndReturn",
-	"upsert",
-	"delete",
-	"deleteMany"
-];
-const PRISMA_READ_METHODS = new Set(PRISMA_READ_METHODS_LIST);
-const PRISMA_WRITE_METHODS = new Set(PRISMA_WRITE_METHODS_LIST);
-const PRISMA_TRANSACTION_METHOD = "$transaction";
-function isPrismaReadMethod(name) {
-	return PRISMA_READ_METHODS.has(name);
-}
-function isPrismaWriteMethod(name) {
-	return PRISMA_WRITE_METHODS.has(name);
-}
-function isPrismaTransactionMethod(name) {
-	return name === PRISMA_TRANSACTION_METHOD;
-}
-
-//#endregion
-//#region src/classify.ts
-/**
-* Classify a CallCandidate against Prisma Client conventions.
-*
-* Recognition strategy:
-*   1. The owning file must import a Prisma Client module (see `hasPrismaImport`). No
-*      import → `null`, so callers can chain other effect plugins after this one.
-*   2. The target is split on `.`; the plugin looks at the trailing segments to match
-*      Prisma's fixed client surface. Two shapes are accepted:
-*        - `<...>.<model>.<verb>` (3+ segments) — a model delegate call. The client
-*          segment stops two-segment method collisions (Express `router.create(...)`)
-*          from false-classifying.
-*        - `<...>.$transaction` (2+ segments) — the top-level transaction API on the
-*          client itself.
-*   3. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the
-*      language plugin's contract is a normalized non-empty callee, so a violation
-*      here is an upstream bug we surface loudly instead of silently miscategorizing.
-*
-* The function is a pure lookup — no I/O, no state, no async — matching the per-call
-* timeout budget the core enforces (effect-plugin.md §5.1.1).
-*/
-function classifyPrismaCall(call, ctx) {
-	const origin = {
-		plugin: EFFECTS_PRISMA_PLUGIN_NAME,
-		filePath: ctx.file.path
-	};
-	const { segments: parts, last: method } = assertNonEmptySegments(call.target, origin);
-	if (!hasPrismaImport(ctx.file.imports, ctx.file.path)) return null;
-	if (isPrismaTransactionMethod(method)) {
-		if (parts.length < 2) return null;
-		return {
-			effectId: "db.transaction",
-			confidence: "high",
-			derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:tx`
-		};
-	}
-	if (parts.length < 3) return null;
-	if (isPrismaReadMethod(method)) return {
-		effectId: "db.read",
-		confidence: "high",
-		derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:read`
-	};
-	if (isPrismaWriteMethod(method)) return {
-		effectId: "db.write",
-		confidence: "high",
-		derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:write`
-	};
-	return null;
-}
-
-//#endregion
-//#region src/manifest.ts
-/**
-* Manifest for `@aburi/effects-prisma`. `as const satisfies EffectsManifest` keeps
-* every literal narrow so downstream registry checks see the exact shape.
-*
-* The plugin returns core-owned effect ids (`db.read` / `db.write` / `db.transaction`)
-* from `classify()`; per extension-vocab.md §5.1 core vocab lives in the reserved
-* namespace and MUST NOT appear in a plugin's `provides.effects`. The plugin's own
-* `x-prisma:*` namespace currently has no bindings — model-specific effects would sit there
-* once introduced. `derivedByPrefixes` shares its literal with the classifier's tag
-* builder so both stay in lockstep across edits.
-*/
-const effectsPrismaManifest = {
-	$schema: "https://aburi.kage1020.com/schema/aburi.plugin.v1.json",
-	name: EFFECTS_PRISMA_PLUGIN_NAME,
-	version: "0.0.0",
-	type: "effects",
-	engines: { aburi: "*" },
-	provides: {
-		effects: [],
-		effectPrefixes: [],
-		extKinds: [],
-		extKindPrefixes: [],
-		derivedByPrefixes: [EFFECTS_PRISMA_DERIVED_BY_PREFIX],
-		frameworks: []
-	}
-};
-
-//#endregion
-//#region src/plugin.ts
-/**
-* Prisma effect plugin. Sits behind the language plugin's `walkBody` output, mapping
-* `prisma.<model>.<verb>` and `prisma.$transaction` call expressions into the core
-* `db.read` / `db.write` / `db.transaction` effect vocabulary.
-*
-* `init` and `classify` are both pure with respect to plugin state — no lazy resources,
-* no per-run caches — so repeated invocations against the same CallCandidate produce
-* identical results. This matches the per-call timeout contract in
-* effect-plugin.md §5.1.1 and the "pure classifier" recommendation in §11.1.
-*/
-var PrismaEffectsPlugin = class {
-	manifest = effectsPrismaManifest;
-	async init(_ctx) {}
-	classify(call, ctx) {
-		return classifyPrismaCall(call, ctx);
-	}
-};
-/**
-* Ready-to-register instance. Callers pass this to `@aburi/plugin-registry` or a scan
-* pipeline. The type annotation is omitted deliberately: `class implements EffectPlugin`
-* already enforces the structural contract, and inferring the narrow class type keeps
-* the manifest literals (`readonly ["effects-plugin:prisma"]`, `"effects-prisma"`)
-* visible to consumers that want to compare against them without a separate manifest
-* import.
-*/
-const prismaEffectsPlugin = new PrismaEffectsPlugin();
-
-//#endregion
-export { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME, PRISMA_READ_METHODS, PRISMA_TRANSACTION_METHOD, PRISMA_WRITE_METHODS, PrismaEffectsPlugin, classifyPrismaCall, effectsPrismaManifest, hasPrismaImport, isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod, prismaEffectsPlugin };
-//# sourceMappingURL=index.mjs.map
+import{assertNonEmptySegments as e,hasLiteralFirstArgument as t,hasMatchingImport as n,identifierMentions as r}from"@aburi/plugin-registry/plugin-input";import{COMPUTED_TARGET_SEGMENT as i}from"@aburi/types";const a=`effects-prisma`,o=`effects-plugin:prisma`,s=new Set([`@prisma/client`,`@prisma/client/edge`]);function c(e){return s.has(e)}function l(e,t){return n(e,{plugin:a,filePath:t},c)}const u=[`findUnique`,`findUniqueOrThrow`,`findFirst`,`findFirstOrThrow`,`findMany`,`count`,`aggregate`,`groupBy`],d=[`create`,`createMany`,`createManyAndReturn`,`update`,`updateMany`,`updateManyAndReturn`,`upsert`,`delete`,`deleteMany`],f=new Set(u),p=new Set(d),m=`$transaction`;function h(e){return f.has(e)}function g(e){return p.has(e)}function _(e){return e===m}const v=new Set([`prisma`,`db`,`database`,`orm`,`tx`,`trx`]);function y(e){return r(e,v)}const b=1,x=2;function S(e,t,n){return t.dynamicReceiver===!0||t.argumentCount>n?`medium`:e!==void 0&&y(e)?`high`:`medium`}function C(n,r){let s={plugin:a,filePath:r.file.path},{segments:c,last:u}=e(n.target,s);if(!l(r.file.imports,r.file.path))return null;if(_(u))return c.length<2||t(n)?null:{effectId:`db.transaction`,confidence:S(c.at(-2),n,2),derivedBy:`${o}:tx`};if(c.length<3||t(n))return null;let d=c.at(-3);if(d!==void 0&&c.at(-2)===i&&!y(d))return null;let f=S(d,n,1);return h(u)?{effectId:`db.read`,confidence:f,derivedBy:`${o}:read`}:g(u)?{effectId:`db.write`,confidence:f,derivedBy:`${o}:write`}:null}const w={$schema:`https://aburi.kage1020.com/schema/aburi.plugin.v1.json`,name:a,version:`0.0.0`,type:`effects`,engines:{aburi:`*`},provides:{effects:[],effectPrefixes:[],extKinds:[],extKindPrefixes:[],derivedByPrefixes:[o],frameworks:[]}};var T=class{manifest=w;async init(e){}classify(e,t){return C(e,t)}};const E=new T;export{o as EFFECTS_PRISMA_DERIVED_BY_PREFIX,a as EFFECTS_PRISMA_PLUGIN_NAME,v as PRISMA_CLIENT_WORDS,b as PRISMA_DELEGATE_MAX_ARGUMENTS,f as PRISMA_READ_METHODS,x as PRISMA_TRANSACTION_MAX_ARGUMENTS,m as PRISMA_TRANSACTION_METHOD,p as PRISMA_WRITE_METHODS,T as PrismaEffectsPlugin,S as classificationConfidence,C as classifyPrismaCall,w as effectsPrismaManifest,l as hasPrismaImport,h as isPrismaReadMethod,_ as isPrismaTransactionMethod,g as isPrismaWriteMethod,y as namesPrismaClient,E as prismaEffectsPlugin};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aburi/effects-prisma",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Aburi Prisma effects plugin: classifies prisma.<model>.<verb> and prisma.$transaction call expressions into core db.read / db.write / db.transaction effects",
   "license": "Apache-2.0",
   "author": "kage1020",
@@ -25,7 +25,6 @@
   },
   "files": [
     "dist",
-    "src",
     "README.md"
   ],
   "sideEffects": false,
@@ -33,15 +32,15 @@
     "access": "public"
   },
   "dependencies": {
-    "@aburi/plugin-registry": "0.3.0",
-    "@aburi/types": "0.3.0"
+    "@aburi/plugin-registry": "0.4.0",
+    "@aburi/types": "0.4.0"
   },
   "devDependencies": {
     "@types/node": "^26.0.1",
     "tsdown": "^0.22.3",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.9",
-    "@aburi/lang-typescript": "0.3.0"
+    "vitest": "^4.1.11",
+    "@aburi/lang-typescript": "0.4.0"
   },
   "scripts": {
     "build": "tsdown",

package/dist/index.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.mts","names":[],"sources":["../src/classify.ts","../src/constants.ts","../src/imports.ts","../src/manifest.ts","../src/methods.ts","../src/plugin.ts"],"mappings":";;;;;AA0BA;;;;;;;;;;;;;;AAGuB;;;;iBAHP,kBAAA,CACd,IAAA,EAAM,aAAA,EACN,GAAA,EAAK,eAAA,GACJ,oBAAA;;;;;;AAHH;;cCjBa,0BAAA;;;;;;cAOA,gCAAA;;;ADaU;;;;ACpBvB;;;;AAAmE;AAOnE;ADauB,iBEWP,eAAA,CAAgB,OAAA,WAAkB,UAAU,IAAI,QAAA;;;;;;AFdhE;;;;;;;;cGZa,qBAAA;EAAA;;;;;;;;;;;;;;;;;;;;;AHYb;;;;;;;;;;cIbM,wBAAA;AAAA,cAWA,yBAAA;AAAA,KAYM,gBAAA,WAA2B,wBAAwB;AAAA,KACnD,iBAAA,WAA4B,yBAAyB;AJR1C;AAAA,KIWX,uBAAA;AAAA,cAEC,mBAAA,EAAqB,WAAW,CAAC,gBAAA;AAAA,cACjC,oBAAA,EAAsB,WAAW,CAAC,iBAAA;AAAA,cAGlC,yBAAA,EAA2B,uBAAwC;AAAA,iBAEhE,kBAAA,CAAmB,IAAA,WAAe,IAAA,IAAQ,gBAAgB;AAAA,iBAI1D,mBAAA,CAAoB,IAAA,WAAe,IAAA,IAAQ,iBAAiB;AAAA,iBAI5D,yBAAA,CAA0B,IAAA,WAAe,IAAA,IAAQ,uBAAuB;;;;;AJ9BxF;;;;;;;;cKNM,mBAAA,YAA+B,YAAA;EAAA,SAC1B,QAAA;IAAA;;;;;;;;;;;;;;;;EAEH,IAAA,CAAK,IAAA,EAAM,aAAA,GAAgB,OAAA;EAEjC,QAAA,CAAS,IAAA,EAAM,aAAA,EAAe,GAAA,EAAK,eAAA,GAAkB,oBAAA;AAAA;;;AHevD;;;;;;cGFa,mBAAA,EAAmB,mBAA4B"}

package/dist/index.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.mjs","names":[],"sources":["../src/constants.ts","../src/imports.ts","../src/methods.ts","../src/classify.ts","../src/manifest.ts","../src/plugin.ts"],"sourcesContent":["// Plugin identity, kept in a leaf module so `classify.ts`, `imports.ts`, and `manifest.ts`\n// can all reach it without importing each other. Putting these next to the classifier\n// instead would make `imports.ts → classify.ts → imports.ts` a cycle.\n\n/**\n * Package-relative plugin name. Doubles as the prefix of every thrown message, so a caught\n * exception names the plugin that rejected the input. `manifest.ts` declares the same\n * string as `name`.\n */\nexport const EFFECTS_PRISMA_PLUGIN_NAME = \"effects-prisma\" as const\n\n/**\n * Shared derivedBy namespace. `manifest.ts` imports this same const for its\n * `derivedByPrefixes` entry, so the classifier's tag builder and the registry\n * declaration cannot drift.\n */\nexport const EFFECTS_PRISMA_DERIVED_BY_PREFIX = \"effects-plugin:prisma\" as const\n","import { hasMatchingImport } from \"@aburi/plugin-registry/plugin-input\"\nimport type { ImportEdge } from \"@aburi/types\"\nimport { EFFECTS_PRISMA_PLUGIN_NAME } from \"./constants\"\n\n/**\n * npm module specifiers that expose a `PrismaClient`. Any file that pulls in one of\n * these is treated as a Prisma consumer; files that reference the identifier without\n * importing Prisma are ignored so an unrelated `db.user.findMany()` from another ORM\n * does not get miscategorized.\n *\n * - `@prisma/client` — the default Prisma Client entry since v4.\n * - `@prisma/client/edge` — the Edge runtime entry used by Vercel Edge, Cloudflare\n *   Workers, and Prisma Accelerate. Different bundle, same delegate surface.\n *\n * The set is a literal source of truth. Extending the plugin for community builds or a\n * future Prisma bundle is a table edit here.\n */\nconst PRISMA_CLIENT_MODULES_LIST = [\"@prisma/client\", \"@prisma/client/edge\"] as const\n\nexport type PrismaClientModule = (typeof PRISMA_CLIENT_MODULES_LIST)[number]\n\nexport const PRISMA_CLIENT_MODULES: ReadonlySet<PrismaClientModule> = new Set(\n  PRISMA_CLIENT_MODULES_LIST,\n)\n\n/** Membership test against the closed set of Prisma Client entry points. */\nfunction isPrismaClientModule(source: string): boolean {\n  return (PRISMA_CLIENT_MODULES as ReadonlySet<string>).has(source)\n}\n\n/**\n * True when the file's import list contains any recognized Prisma Client module. An\n * empty source string on an ImportEdge is rejected by the shared guard: the language\n * plugin's contract is to emit normalized non-empty specifiers, and treating `\"\"` as\n * unmatched would silently hide upstream bugs.\n *\n * `filePath` is required and threaded into any thrown error message so a caught\n * exception in production tooling (CI logs, error reporters) points directly at the\n * offending source file rather than a bare \"empty source\" string.\n */\nexport function hasPrismaImport(imports: readonly ImportEdge[], filePath: string): boolean {\n  return hasMatchingImport(\n    imports,\n    { plugin: EFFECTS_PRISMA_PLUGIN_NAME, filePath },\n    isPrismaClientModule,\n  )\n}\n","/**\n * Prisma model delegate method vocabulary.\n *\n * Each `_LIST` is the single source of truth — the union type and the runtime `Set` are\n * both derived from it, so extending the vocabulary is a table edit in exactly one\n * place. Extending as Prisma ships new delegate methods keeps the classifier honest\n * without a code rewrite.\n *\n * Only methods that map cleanly onto core `db.read` / `db.write` vocabulary are listed.\n * Delegate helpers whose semantics do not match (metadata accessors, raw SQL escapes,\n * connection lifecycle) stay out — the plugin returns `null` for them so downstream\n * effect plugins get a chance.\n */\nconst PRISMA_READ_METHODS_LIST = [\n  \"findUnique\",\n  \"findUniqueOrThrow\",\n  \"findFirst\",\n  \"findFirstOrThrow\",\n  \"findMany\",\n  \"count\",\n  \"aggregate\",\n  \"groupBy\",\n] as const\n\nconst PRISMA_WRITE_METHODS_LIST = [\n  \"create\",\n  \"createMany\",\n  \"createManyAndReturn\",\n  \"update\",\n  \"updateMany\",\n  \"updateManyAndReturn\",\n  \"upsert\",\n  \"delete\",\n  \"deleteMany\",\n] as const\n\nexport type PrismaReadMethod = (typeof PRISMA_READ_METHODS_LIST)[number]\nexport type PrismaWriteMethod = (typeof PRISMA_WRITE_METHODS_LIST)[number]\n\n/** Top-level client method: `prisma.$transaction(...)`. Not nested under a model. */\nexport type PrismaTransactionMethod = \"$transaction\"\n\nexport const PRISMA_READ_METHODS: ReadonlySet<PrismaReadMethod> = new Set(PRISMA_READ_METHODS_LIST)\nexport const PRISMA_WRITE_METHODS: ReadonlySet<PrismaWriteMethod> = new Set(\n  PRISMA_WRITE_METHODS_LIST,\n)\nexport const PRISMA_TRANSACTION_METHOD: PrismaTransactionMethod = \"$transaction\"\n\nexport function isPrismaReadMethod(name: string): name is PrismaReadMethod {\n  return (PRISMA_READ_METHODS as ReadonlySet<string>).has(name)\n}\n\nexport function isPrismaWriteMethod(name: string): name is PrismaWriteMethod {\n  return (PRISMA_WRITE_METHODS as ReadonlySet<string>).has(name)\n}\n\nexport function isPrismaTransactionMethod(name: string): name is PrismaTransactionMethod {\n  return name === PRISMA_TRANSACTION_METHOD\n}\n","import { assertNonEmptySegments, type PluginInputOrigin } from \"@aburi/plugin-registry/plugin-input\"\nimport type { CallCandidate, ClassifyContext, EffectClassification } from \"@aburi/types\"\nimport { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME } from \"./constants\"\nimport { hasPrismaImport } from \"./imports\"\nimport { isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod } from \"./methods\"\n\n/**\n * Classify a CallCandidate against Prisma Client conventions.\n *\n * Recognition strategy:\n *   1. The owning file must import a Prisma Client module (see `hasPrismaImport`). No\n *      import → `null`, so callers can chain other effect plugins after this one.\n *   2. The target is split on `.`; the plugin looks at the trailing segments to match\n *      Prisma's fixed client surface. Two shapes are accepted:\n *        - `<...>.<model>.<verb>` (3+ segments) — a model delegate call. The client\n *          segment stops two-segment method collisions (Express `router.create(...)`)\n *          from false-classifying.\n *        - `<...>.$transaction` (2+ segments) — the top-level transaction API on the\n *          client itself.\n *   3. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the\n *      language plugin's contract is a normalized non-empty callee, so a violation\n *      here is an upstream bug we surface loudly instead of silently miscategorizing.\n *\n * The function is a pure lookup — no I/O, no state, no async — matching the per-call\n * timeout budget the core enforces (effect-plugin.md §5.1.1).\n */\nexport function classifyPrismaCall(\n  call: CallCandidate,\n  ctx: ClassifyContext,\n): EffectClassification | null {\n  const origin: PluginInputOrigin = { plugin: EFFECTS_PRISMA_PLUGIN_NAME, filePath: ctx.file.path }\n\n  // Fail-fast runs BEFORE the import gate — see `assertNonEmptySegments` for why the\n  // order is load-bearing.\n  const { segments: parts, last: method } = assertNonEmptySegments(call.target, origin)\n\n  if (!hasPrismaImport(ctx.file.imports, ctx.file.path)) return null\n\n  if (isPrismaTransactionMethod(method)) {\n    // Bare `$transaction()` (single segment) is not a Prisma call — the transaction\n    // API only makes sense as a method on the client (`<client>.$transaction(...)`).\n    if (parts.length < 2) return null\n    return {\n      effectId: \"db.transaction\",\n      confidence: \"high\",\n      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:tx`,\n    }\n  }\n\n  // Model delegate calls need `<client>.<model>.<verb>` to distinguish them from\n  // unrelated two-segment method calls (Express `router.create(...)`, an Array's\n  // hypothetical `.findMany` collision) that would otherwise false-positive in files\n  // that colocate Prisma with another library.\n  if (parts.length < 3) return null\n\n  if (isPrismaReadMethod(method)) {\n    return {\n      effectId: \"db.read\",\n      confidence: \"high\",\n      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:read`,\n    }\n  }\n\n  if (isPrismaWriteMethod(method)) {\n    return {\n      effectId: \"db.write\",\n      confidence: \"high\",\n      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:write`,\n    }\n  }\n\n  return null\n}\n","import type { EffectsManifest } from \"@aburi/types\"\nimport { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME } from \"./constants\"\n\n/**\n * Manifest for `@aburi/effects-prisma`. `as const satisfies EffectsManifest` keeps\n * every literal narrow so downstream registry checks see the exact shape.\n *\n * The plugin returns core-owned effect ids (`db.read` / `db.write` / `db.transaction`)\n * from `classify()`; per extension-vocab.md §5.1 core vocab lives in the reserved\n * namespace and MUST NOT appear in a plugin's `provides.effects`. The plugin's own\n * `x-prisma:*` namespace currently has no bindings — model-specific effects would sit there\n * once introduced. `derivedByPrefixes` shares its literal with the classifier's tag\n * builder so both stay in lockstep across edits.\n */\nexport const effectsPrismaManifest = {\n  $schema: \"https://aburi.kage1020.com/schema/aburi.plugin.v1.json\",\n  name: EFFECTS_PRISMA_PLUGIN_NAME,\n  version: \"0.0.0\",\n  type: \"effects\",\n  engines: { aburi: \"*\" },\n  provides: {\n    effects: [],\n    effectPrefixes: [],\n    extKinds: [],\n    extKindPrefixes: [],\n    derivedByPrefixes: [EFFECTS_PRISMA_DERIVED_BY_PREFIX],\n    frameworks: [],\n  },\n} as const satisfies EffectsManifest\n","import type {\n  CallCandidate,\n  ClassifyContext,\n  EffectClassification,\n  EffectPlugin,\n  PluginContext,\n} from \"@aburi/types\"\nimport { classifyPrismaCall } from \"./classify\"\nimport { effectsPrismaManifest } from \"./manifest\"\n\n/**\n * Prisma effect plugin. Sits behind the language plugin's `walkBody` output, mapping\n * `prisma.<model>.<verb>` and `prisma.$transaction` call expressions into the core\n * `db.read` / `db.write` / `db.transaction` effect vocabulary.\n *\n * `init` and `classify` are both pure with respect to plugin state — no lazy resources,\n * no per-run caches — so repeated invocations against the same CallCandidate produce\n * identical results. This matches the per-call timeout contract in\n * effect-plugin.md §5.1.1 and the \"pure classifier\" recommendation in §11.1.\n */\nclass PrismaEffectsPlugin implements EffectPlugin {\n  readonly manifest = effectsPrismaManifest\n\n  async init(_ctx: PluginContext): Promise<void> {}\n\n  classify(call: CallCandidate, ctx: ClassifyContext): EffectClassification | null {\n    return classifyPrismaCall(call, ctx)\n  }\n}\n\n/**\n * Ready-to-register instance. Callers pass this to `@aburi/plugin-registry` or a scan\n * pipeline. The type annotation is omitted deliberately: `class implements EffectPlugin`\n * already enforces the structural contract, and inferring the narrow class type keeps\n * the manifest literals (`readonly [\"effects-plugin:prisma\"]`, `\"effects-prisma\"`)\n * visible to consumers that want to compare against them without a separate manifest\n * import.\n */\nexport const prismaEffectsPlugin = new PrismaEffectsPlugin()\n\nexport { PrismaEffectsPlugin }\n"],"mappings":";;;;;;;;AASA,MAAa,6BAA6B;;;;;;AAO1C,MAAa,mCAAmC;;;;;;;;;;;;;;;;;ACChD,MAAM,6BAA6B,CAAC,kBAAkB,qBAAqB;AAI3E,MAAa,wBAAyD,IAAI,IACxE,0BACF;;AAGA,SAAS,qBAAqB,QAAyB;CACrD,OAAQ,sBAA8C,IAAI,MAAM;AAClE;;;;;;;;;;;AAYA,SAAgB,gBAAgB,SAAgC,UAA2B;CACzF,OAAO,kBACL,SACA;EAAE,QAAQ;EAA4B;CAAS,GAC/C,oBACF;AACF;;;;;;;;;;;;;;;;;ACjCA,MAAM,2BAA2B;CAC/B;CACA;CACA;CACA;CACA;CACA;CACA;CACA;AACF;AAEA,MAAM,4BAA4B;CAChC;CACA;CACA;CACA;CACA;CACA;CACA;CACA;CACA;AACF;AAQA,MAAa,sBAAqD,IAAI,IAAI,wBAAwB;AAClG,MAAa,uBAAuD,IAAI,IACtE,yBACF;AACA,MAAa,4BAAqD;AAElE,SAAgB,mBAAmB,MAAwC;CACzE,OAAQ,oBAA4C,IAAI,IAAI;AAC9D;AAEA,SAAgB,oBAAoB,MAAyC;CAC3E,OAAQ,qBAA6C,IAAI,IAAI;AAC/D;AAEA,SAAgB,0BAA0B,MAA+C;CACvF,OAAO,SAAS;AAClB;;;;;;;;;;;;;;;;;;;;;;;;AChCA,SAAgB,mBACd,MACA,KAC6B;CAC7B,MAAM,SAA4B;EAAE,QAAQ;EAA4B,UAAU,IAAI,KAAK;CAAK;CAIhG,MAAM,EAAE,UAAU,OAAO,MAAM,WAAW,uBAAuB,KAAK,QAAQ,MAAM;CAEpF,IAAI,CAAC,gBAAgB,IAAI,KAAK,SAAS,IAAI,KAAK,IAAI,GAAG,OAAO;CAE9D,IAAI,0BAA0B,MAAM,GAAG;EAGrC,IAAI,MAAM,SAAS,GAAG,OAAO;EAC7B,OAAO;GACL,UAAU;GACV,YAAY;GACZ,WAAW,GAAG,iCAAiC;EACjD;CACF;CAMA,IAAI,MAAM,SAAS,GAAG,OAAO;CAE7B,IAAI,mBAAmB,MAAM,GAC3B,OAAO;EACL,UAAU;EACV,YAAY;EACZ,WAAW,GAAG,iCAAiC;CACjD;CAGF,IAAI,oBAAoB,MAAM,GAC5B,OAAO;EACL,UAAU;EACV,YAAY;EACZ,WAAW,GAAG,iCAAiC;CACjD;CAGF,OAAO;AACT;;;;;;;;;;;;;;;AC1DA,MAAa,wBAAwB;CACnC,SAAS;CACT,MAAM;CACN,SAAS;CACT,MAAM;CACN,SAAS,EAAE,OAAO,IAAI;CACtB,UAAU;EACR,SAAS,CAAC;EACV,gBAAgB,CAAC;EACjB,UAAU,CAAC;EACX,iBAAiB,CAAC;EAClB,mBAAmB,CAAC,gCAAgC;EACpD,YAAY,CAAC;CACf;AACF;;;;;;;;;;;;;;ACRA,IAAM,sBAAN,MAAkD;CAChD,AAAS,WAAW;CAEpB,MAAM,KAAK,MAAoC,CAAC;CAEhD,SAAS,MAAqB,KAAmD;EAC/E,OAAO,mBAAmB,MAAM,GAAG;CACrC;AACF;;;;;;;;;AAUA,MAAa,sBAAsB,IAAI,oBAAoB"}

package/src/classify.ts

@@ -1,73 +0,0 @@
-import { assertNonEmptySegments, type PluginInputOrigin } from "@aburi/plugin-registry/plugin-input"
-import type { CallCandidate, ClassifyContext, EffectClassification } from "@aburi/types"
-import { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME } from "./constants"
-import { hasPrismaImport } from "./imports"
-import { isPrismaReadMethod, isPrismaTransactionMethod, isPrismaWriteMethod } from "./methods"
-
-/**
- * Classify a CallCandidate against Prisma Client conventions.
- *
- * Recognition strategy:
- *   1. The owning file must import a Prisma Client module (see `hasPrismaImport`). No
- *      import → `null`, so callers can chain other effect plugins after this one.
- *   2. The target is split on `.`; the plugin looks at the trailing segments to match
- *      Prisma's fixed client surface. Two shapes are accepted:
- *        - `<...>.<model>.<verb>` (3+ segments) — a model delegate call. The client
- *          segment stops two-segment method collisions (Express `router.create(...)`)
- *          from false-classifying.
- *        - `<...>.$transaction` (2+ segments) — the top-level transaction API on the
- *          client itself.
- *   3. Malformed targets (empty string, adjacent / leading / trailing dots) throw — the
- *      language plugin's contract is a normalized non-empty callee, so a violation
- *      here is an upstream bug we surface loudly instead of silently miscategorizing.
- *
- * The function is a pure lookup — no I/O, no state, no async — matching the per-call
- * timeout budget the core enforces (effect-plugin.md §5.1.1).
- */
-export function classifyPrismaCall(
-  call: CallCandidate,
-  ctx: ClassifyContext,
-): EffectClassification | null {
-  const origin: PluginInputOrigin = { plugin: EFFECTS_PRISMA_PLUGIN_NAME, filePath: ctx.file.path }
-
-  // Fail-fast runs BEFORE the import gate — see `assertNonEmptySegments` for why the
-  // order is load-bearing.
-  const { segments: parts, last: method } = assertNonEmptySegments(call.target, origin)
-
-  if (!hasPrismaImport(ctx.file.imports, ctx.file.path)) return null
-
-  if (isPrismaTransactionMethod(method)) {
-    // Bare `$transaction()` (single segment) is not a Prisma call — the transaction
-    // API only makes sense as a method on the client (`<client>.$transaction(...)`).
-    if (parts.length < 2) return null
-    return {
-      effectId: "db.transaction",
-      confidence: "high",
-      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:tx`,
-    }
-  }
-
-  // Model delegate calls need `<client>.<model>.<verb>` to distinguish them from
-  // unrelated two-segment method calls (Express `router.create(...)`, an Array's
-  // hypothetical `.findMany` collision) that would otherwise false-positive in files
-  // that colocate Prisma with another library.
-  if (parts.length < 3) return null
-
-  if (isPrismaReadMethod(method)) {
-    return {
-      effectId: "db.read",
-      confidence: "high",
-      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:read`,
-    }
-  }
-
-  if (isPrismaWriteMethod(method)) {
-    return {
-      effectId: "db.write",
-      confidence: "high",
-      derivedBy: `${EFFECTS_PRISMA_DERIVED_BY_PREFIX}:write`,
-    }
-  }
-
-  return null
-}

package/src/constants.ts

@@ -1,17 +0,0 @@
-// Plugin identity, kept in a leaf module so `classify.ts`, `imports.ts`, and `manifest.ts`
-// can all reach it without importing each other. Putting these next to the classifier
-// instead would make `imports.ts → classify.ts → imports.ts` a cycle.
-
-/**
- * Package-relative plugin name. Doubles as the prefix of every thrown message, so a caught
- * exception names the plugin that rejected the input. `manifest.ts` declares the same
- * string as `name`.
- */
-export const EFFECTS_PRISMA_PLUGIN_NAME = "effects-prisma" as const
-
-/**
- * Shared derivedBy namespace. `manifest.ts` imports this same const for its
- * `derivedByPrefixes` entry, so the classifier's tag builder and the registry
- * declaration cannot drift.
- */
-export const EFFECTS_PRISMA_DERIVED_BY_PREFIX = "effects-plugin:prisma" as const

package/src/imports.ts

@@ -1,47 +0,0 @@
-import { hasMatchingImport } from "@aburi/plugin-registry/plugin-input"
-import type { ImportEdge } from "@aburi/types"
-import { EFFECTS_PRISMA_PLUGIN_NAME } from "./constants"
-
-/**
- * npm module specifiers that expose a `PrismaClient`. Any file that pulls in one of
- * these is treated as a Prisma consumer; files that reference the identifier without
- * importing Prisma are ignored so an unrelated `db.user.findMany()` from another ORM
- * does not get miscategorized.
- *
- * - `@prisma/client` — the default Prisma Client entry since v4.
- * - `@prisma/client/edge` — the Edge runtime entry used by Vercel Edge, Cloudflare
- *   Workers, and Prisma Accelerate. Different bundle, same delegate surface.
- *
- * The set is a literal source of truth. Extending the plugin for community builds or a
- * future Prisma bundle is a table edit here.
- */
-const PRISMA_CLIENT_MODULES_LIST = ["@prisma/client", "@prisma/client/edge"] as const
-
-export type PrismaClientModule = (typeof PRISMA_CLIENT_MODULES_LIST)[number]
-
-export const PRISMA_CLIENT_MODULES: ReadonlySet<PrismaClientModule> = new Set(
-  PRISMA_CLIENT_MODULES_LIST,
-)
-
-/** Membership test against the closed set of Prisma Client entry points. */
-function isPrismaClientModule(source: string): boolean {
-  return (PRISMA_CLIENT_MODULES as ReadonlySet<string>).has(source)
-}
-
-/**
- * True when the file's import list contains any recognized Prisma Client module. An
- * empty source string on an ImportEdge is rejected by the shared guard: the language
- * plugin's contract is to emit normalized non-empty specifiers, and treating `""` as
- * unmatched would silently hide upstream bugs.
- *
- * `filePath` is required and threaded into any thrown error message so a caught
- * exception in production tooling (CI logs, error reporters) points directly at the
- * offending source file rather than a bare "empty source" string.
- */
-export function hasPrismaImport(imports: readonly ImportEdge[], filePath: string): boolean {
-  return hasMatchingImport(
-    imports,
-    { plugin: EFFECTS_PRISMA_PLUGIN_NAME, filePath },
-    isPrismaClientModule,
-  )
-}

package/src/index.ts

@@ -1,16 +0,0 @@
-export { classifyPrismaCall } from "./classify"
-export { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME } from "./constants"
-export { hasPrismaImport } from "./imports"
-export { effectsPrismaManifest } from "./manifest"
-export {
-  isPrismaReadMethod,
-  isPrismaTransactionMethod,
-  isPrismaWriteMethod,
-  PRISMA_READ_METHODS,
-  PRISMA_TRANSACTION_METHOD,
-  PRISMA_WRITE_METHODS,
-  type PrismaReadMethod,
-  type PrismaTransactionMethod,
-  type PrismaWriteMethod,
-} from "./methods"
-export { PrismaEffectsPlugin, prismaEffectsPlugin } from "./plugin"

package/src/manifest.ts

@@ -1,29 +0,0 @@
-import type { EffectsManifest } from "@aburi/types"
-import { EFFECTS_PRISMA_DERIVED_BY_PREFIX, EFFECTS_PRISMA_PLUGIN_NAME } from "./constants"
-
-/**
- * Manifest for `@aburi/effects-prisma`. `as const satisfies EffectsManifest` keeps
- * every literal narrow so downstream registry checks see the exact shape.
- *
- * The plugin returns core-owned effect ids (`db.read` / `db.write` / `db.transaction`)
- * from `classify()`; per extension-vocab.md §5.1 core vocab lives in the reserved
- * namespace and MUST NOT appear in a plugin's `provides.effects`. The plugin's own
- * `x-prisma:*` namespace currently has no bindings — model-specific effects would sit there
- * once introduced. `derivedByPrefixes` shares its literal with the classifier's tag
- * builder so both stay in lockstep across edits.
- */
-export const effectsPrismaManifest = {
-  $schema: "https://aburi.kage1020.com/schema/aburi.plugin.v1.json",
-  name: EFFECTS_PRISMA_PLUGIN_NAME,
-  version: "0.0.0",
-  type: "effects",
-  engines: { aburi: "*" },
-  provides: {
-    effects: [],
-    effectPrefixes: [],
-    extKinds: [],
-    extKindPrefixes: [],
-    derivedByPrefixes: [EFFECTS_PRISMA_DERIVED_BY_PREFIX],
-    frameworks: [],
-  },
-} as const satisfies EffectsManifest

package/src/methods.ts

@@ -1,59 +0,0 @@
-/**
- * Prisma model delegate method vocabulary.
- *
- * Each `_LIST` is the single source of truth — the union type and the runtime `Set` are
- * both derived from it, so extending the vocabulary is a table edit in exactly one
- * place. Extending as Prisma ships new delegate methods keeps the classifier honest
- * without a code rewrite.
- *
- * Only methods that map cleanly onto core `db.read` / `db.write` vocabulary are listed.
- * Delegate helpers whose semantics do not match (metadata accessors, raw SQL escapes,
- * connection lifecycle) stay out — the plugin returns `null` for them so downstream
- * effect plugins get a chance.
- */
-const PRISMA_READ_METHODS_LIST = [
-  "findUnique",
-  "findUniqueOrThrow",
-  "findFirst",
-  "findFirstOrThrow",
-  "findMany",
-  "count",
-  "aggregate",
-  "groupBy",
-] as const
-
-const PRISMA_WRITE_METHODS_LIST = [
-  "create",
-  "createMany",
-  "createManyAndReturn",
-  "update",
-  "updateMany",
-  "updateManyAndReturn",
-  "upsert",
-  "delete",
-  "deleteMany",
-] as const
-
-export type PrismaReadMethod = (typeof PRISMA_READ_METHODS_LIST)[number]
-export type PrismaWriteMethod = (typeof PRISMA_WRITE_METHODS_LIST)[number]
-
-/** Top-level client method: `prisma.$transaction(...)`. Not nested under a model. */
-export type PrismaTransactionMethod = "$transaction"
-
-export const PRISMA_READ_METHODS: ReadonlySet<PrismaReadMethod> = new Set(PRISMA_READ_METHODS_LIST)
-export const PRISMA_WRITE_METHODS: ReadonlySet<PrismaWriteMethod> = new Set(
-  PRISMA_WRITE_METHODS_LIST,
-)
-export const PRISMA_TRANSACTION_METHOD: PrismaTransactionMethod = "$transaction"
-
-export function isPrismaReadMethod(name: string): name is PrismaReadMethod {
-  return (PRISMA_READ_METHODS as ReadonlySet<string>).has(name)
-}
-
-export function isPrismaWriteMethod(name: string): name is PrismaWriteMethod {
-  return (PRISMA_WRITE_METHODS as ReadonlySet<string>).has(name)
-}
-
-export function isPrismaTransactionMethod(name: string): name is PrismaTransactionMethod {
-  return name === PRISMA_TRANSACTION_METHOD
-}

package/src/plugin.ts

@@ -1,41 +0,0 @@
-import type {
-  CallCandidate,
-  ClassifyContext,
-  EffectClassification,
-  EffectPlugin,
-  PluginContext,
-} from "@aburi/types"
-import { classifyPrismaCall } from "./classify"
-import { effectsPrismaManifest } from "./manifest"
-
-/**
- * Prisma effect plugin. Sits behind the language plugin's `walkBody` output, mapping
- * `prisma.<model>.<verb>` and `prisma.$transaction` call expressions into the core
- * `db.read` / `db.write` / `db.transaction` effect vocabulary.
- *
- * `init` and `classify` are both pure with respect to plugin state — no lazy resources,
- * no per-run caches — so repeated invocations against the same CallCandidate produce
- * identical results. This matches the per-call timeout contract in
- * effect-plugin.md §5.1.1 and the "pure classifier" recommendation in §11.1.
- */
-class PrismaEffectsPlugin implements EffectPlugin {
-  readonly manifest = effectsPrismaManifest
-
-  async init(_ctx: PluginContext): Promise<void> {}
-
-  classify(call: CallCandidate, ctx: ClassifyContext): EffectClassification | null {
-    return classifyPrismaCall(call, ctx)
-  }
-}
-
-/**
- * Ready-to-register instance. Callers pass this to `@aburi/plugin-registry` or a scan
- * pipeline. The type annotation is omitted deliberately: `class implements EffectPlugin`
- * already enforces the structural contract, and inferring the narrow class type keeps
- * the manifest literals (`readonly ["effects-plugin:prisma"]`, `"effects-prisma"`)
- * visible to consumers that want to compare against them without a separate manifest
- * import.
- */
-export const prismaEffectsPlugin = new PrismaEffectsPlugin()
-
-export { PrismaEffectsPlugin }