@akanjs/cli 3.0.0-alpha.91 → 3.0.0-alpha.93

package/.build-stamp

@@ -1 +1 @@
-4555f9639a8471059ce45bf265787ab7caf5278c8509bf865e1d92e7193e66a0
+46684e220ad3b25561e71ed37a2ec4586818c4546d7eae1414ac8ad9dbdcd064

package/guidelines/conventions/conventions.instruction.md

@@ -555,6 +555,7 @@ Full contract — relevance ordering, `columns` / `weights`: `get_guideline` wit
 - Injected dependencies resolve by field-name convention: a field named `<refName>Service` resolves to the service registered under `<refName>`, and `<refName>Signal` likewise (`pkgs/akanjs/service/injectInfo.ts`).
 - The `Service`/`Signal` suffix is required — the injector strips it to derive the registry lookup key. Name the field after the target refName plus the suffix, not arbitrarily.
 - Preference order inside a service: `service<srv.XService>()` for another module's service · `plug(AdapterClass)` or `plug(StorageAdaptorRole)` for an adapter · `use<T>()` only to reach an `option.ts`-registered legacy singleton · `env(...)` for config.
+- **`memory(...)` takes a scalar or model class, not only a primitive** — `memory(Map, { of: CallStateInput })` serializes through the constant and travels as JSON text, so the Redis and sqlite-backed caches round-trip the same declaration. Never hand-encode JSON into a `String` memory.
 
 ### Adapters — `adapt()` And `plug()`
 
@@ -736,7 +737,11 @@ shape, so `cascade` never means "related" — it means one of exactly these:
   its owner, so the owner never learns about its children and a lib model can be extended by an app's. Three
   forms: a relation, an id with `ref`, or a polymorphic id with `refPath`. An array, a Map, `ref` together with
   `refPath`, and a field naming no owner each fail the class build.
-- **A `refPath` must name an `enumOf` field** — a free-form owner type is unknowable at build time.
+- **A `refPath` must name an `enumOf` field** — a free-form owner type is unknowable at build time. The one
+  exception is opt-in and priced: `polymorphic: "any"` alongside `cascade: "removeWith"` takes a free-form
+  `String` type field holding the owner's refName, and sweeps for children on **every** model's removal. The
+  sweep is one indexed probe, but a single wildcard edge turns every cascade in the app back to one document at
+  a time; the boot log names the edges in one `info` line.
 - **A cascade goes through the target's service, never its model** — that path is what runs the target's
   `_postRemove`, where a module puts the side effect the removal has to carry.
 - **Nothing checks whether another document still references the same target.** `File` in particular is deduped by

package/guidelines/queryRule/queryRule.instruction.md

@@ -121,6 +121,26 @@ shape, so `cascade` never means "related" — it means one of exactly these:
   `refPath`. An array, a Map, `ref` together with `refPath`, and a field naming no owner each fail the class build.
 - **A `refPath` must name an `enumOf` field** — a free-form owner type is unknowable at build time, so every
   model's removal would have to sweep the polymorphic table on the chance it is the owner.
+- **`polymorphic: "any"` buys that sweep on purpose**, for the one shape an enum cannot express: a child whose
+  owner is any model in the app, named by a free-form `String` holding the owner's refName.
+
+  ```ts
+  parent: field(ID, { refPath: "parentType", cascade: "removeWith", polymorphic: "any" }),
+  parentType: field(String),   // holds the owner's refName
+  ```
+
+  The lookup itself is cheap — the declaration auto-creates the same `{ removedAt, typeKey, fk }` index, so a
+  removal that owns nothing is one index probe returning zero rows, not a scan. **The price is bulk: one wildcard
+  edge anywhere turns every cascade in the app back to one document at a time**, because a query-level removal of
+  *any* model would be a removal whose wildcard children were never looked for. The boot log says so in one
+  `info` line naming the edges — that line is the answer to "why does this app remove everything per document".
+  The opt-in is what keeps an app that declared none on the fast path.
+
+  Refused at the class build: `polymorphic: "any"` on a `refPath` that already names an `enumOf` (the enum names
+  the candidates and indexes better — keep one), a `typeKey` that is not a `String` (the sweep matches a refName
+  against that column, and a column that cannot hold one silently finds nothing), and the option anywhere other
+  than a `cascade: "removeWith"` field with a `refPath`. A wildcard owner is also exempt from the mount check
+  that a monomorphic owner fails at boot — it names no module to mount.
 - **A cascade goes through the target's service, never its model** — that path is what runs the target's
   `_postRemove`, where a module puts the side effect the removal has to carry.
 - **Bulk is decided at boot, per target model, for both directions.** A target with no `remove` schema hook, no

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akanjs/cli",
-  "version": "3.0.0-alpha.91",
+  "version": "3.0.0-alpha.93",
   "sourceType": "module",
   "type": "module",
   "publishConfig": {
@@ -33,7 +33,7 @@
     "@langchain/openai": "^1.4.6",
     "@tailwindcss/node": "^4.3.0",
     "@trapezedev/project": "^7.1.4",
-    "akanjs": "3.0.0-alpha.91",
+    "akanjs": "3.0.0-alpha.93",
     "chalk": "^5.6.2",
     "commander": "^14.0.3",
     "dayjs": "^1.11.20",