@akanjs/cli 3.0.0-alpha.32 → 3.0.0-alpha.34

package/.build-stamp

@@ -1 +1 @@
-2099eccdeb7239ce6ccf7bf5c6a250594bfac9b4208510043dd0365fe7aa7e8f
+1ba5af5f113a1c106187a2b639d58cebb76b91f2b81154ec5fd690e268026a8e

package/guidelines/conventions/conventions.instruction.md

@@ -59,10 +59,13 @@ that looks wrong; do not "fix" it back.
 - **Never redeclare a generated CRUD endpoint name** in `*.signal.ts` (`no-redeclare-predefined-endpoint.grit`).
 - **Never type a `*.Util.tsx` / `*.Zone.tsx` prop as a `cnst` model** (`no-model-type-in-util-zone.grit`). Those two
   roles are always client components, so a `cnst.Banner` / `cnst.LightBanner` prop is a class instance the server has
-  to hand across the boundary; take `bannerId: string` and read the model from the store instead. Two shapes are
-  exempt because neither is an instance: `cnst.<Enum>["value"]`, whose indexed access resolves to a string union, and
-  a `ClientInit` / `ClientView` / `ClientEdit` type argument, which the framework maps to `GetStateObject<…>` plain
-  data. Any *other* indexed access is still flagged — `cnst.Banner["image"]` is a `File`.
+  to hand across the boundary; take `bannerId: string` and read the model from the store instead. Three shapes are
+  exempt because none of them is an instance: `cnst.<Enum>["value"]`, whose indexed access resolves to a string
+  union; a `ClientInit` / `ClientView` / `ClientEdit` type argument, which the framework maps to `GetStateObject<…>`
+  plain data; and a `ModelsProps<cnst.Setting>` type argument, whose only use of the model is the `onClickItem`
+  callback, so nothing model-shaped ever lands on a prop. `ModelProps<"setting", cnst.LightSetting>` is *not* exempt
+  — that one spreads the model onto the props themselves, and `Unit` / `View`, which take it, are server components
+  this rule does not cover. Any *other* indexed access is still flagged — `cnst.Banner["image"]` is a `File`.
   **Only prop positions are read** — a `*Props` interface or type alias, and the inline object type on the
   component's own parameter. A `cnst` type that never leaves the file is not a boundary crossing and stays legal: a
   local annotation, a callback parameter the framework itself types with the model
@@ -710,7 +713,11 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
   globally and a component cannot build one per render: pass the list it has — a slice's sort keys, the options a
   prop carried — and it is published and enforced the same way. Neither reaches a set that fills in *after* the
   first render, since a declaration is mount-static; put that in the tool's `guard`, which is re-read per call and
-  can name the current values in its refusal.
+  can name the current values in its refusal. **An argument type nothing can describe — a model class, `Any`, a
+  `Map` — withdraws the whole tool and says so on the console**, naming the tool, the argument and the type; the
+  callable still drives the click a person makes. It does not throw: a tool schema is built during render, and an
+  agent-tooling mistake that aborted the render would cost the route its server rendering. `st.useState`'s `set`
+  degrades the same way, to read-only.
 - **A component that renders once per row publishes nothing.** A tool registered under one name by fifty rows is
   forty-nine collisions and one survivor. The container publishes one tool taking the id instead —
   `removeTask(taskId)`, never fifty `removeTask` — and the agent reads the ids from the `<slice>.items` resource

package/package.json

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