@jskit-ai/agent-docs 0.1.295 → 0.1.297

package/skills/jskit/references/patterns/crud/crud-feature-package/PATTERN.md

@@ -132,7 +132,8 @@ so an action without an HTTP route would otherwise reach records that no route
 shows the user. The actions of an `internal: true` or `routes: false` feature
 therefore stay off `automation` (the assistant cannot call them) unless their
 permission names a permission (`require: "all"` or `"any"`), as the workspace
-scope's default `crud.<namespace>.<operation>` permissions do. Give such a
+scope's default `crud.<namespace>.<operation>` permissions do (the operation is
+`list`, `view`, `create`, `update` or `delete`; an HTTP `PATCH` is `update`). Give such a
 feature explicit `permissions` when the assistant should read it for the users
 who hold them; the default for other surfaces, `require: "authenticated"`,
 would admit every signed-in user. An additional action's own `channels`

package/skills/jskit/references/patterns/crud/crud-feature-package/example/packages/books/package.json

@@ -9,9 +9,9 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.25",
-    "@jskit-ai/resource-core": "0.1.209",
-    "@jskit-ai/resource-crud-core": "0.1.210"
+    "@jskit-ai/crud-core": "0.2.27",
+    "@jskit-ai/resource-core": "0.1.210",
+    "@jskit-ai/resource-crud-core": "0.1.212"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/database/mysql-application/example/package.json

@@ -9,7 +9,7 @@
     "test": "jskit test --databases"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime": "0.1.267",
-    "@jskit-ai/database-runtime-mysql": "0.1.265"
+    "@jskit-ai/database-runtime": "0.1.268",
+    "@jskit-ai/database-runtime-mysql": "0.1.266"
   }
 }

package/skills/jskit/references/patterns/database/postgres-application/example/package.json

@@ -9,7 +9,7 @@
     "test": "jskit test --databases"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime": "0.1.267",
-    "@jskit-ai/database-runtime-postgres": "0.1.264"
+    "@jskit-ai/database-runtime": "0.1.268",
+    "@jskit-ai/database-runtime-postgres": "0.1.265"
   }
 }

package/skills/jskit/references/patterns/realtime/realtime-application/example/package.json

@@ -2,7 +2,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/realtime": "0.2.26",
-    "@jskit-ai/shell-web": "0.2.23"
+    "@jskit-ai/realtime": "0.2.28",
+    "@jskit-ai/shell-web": "0.2.25"
   }
 }

package/skills/jskit/references/patterns/server/feature-package/example/booking-engine/package.json

@@ -5,7 +5,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/kernel": "0.2.18",
+    "@jskit-ai/kernel": "0.2.19",
     "json-rest-schema": "^1.0.20"
   },
   "exports": {

package/skills/jskit/references/patterns/users/user-administration-server/example/packages/users/package.json

@@ -10,9 +10,9 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.25",
-    "@jskit-ai/resource-crud-core": "0.1.210",
-    "@jskit-ai/users-core": "0.2.26"
+    "@jskit-ai/crud-core": "0.2.27",
+    "@jskit-ai/resource-crud-core": "0.1.212",
+    "@jskit-ai/users-core": "0.2.28"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/users/user-administration-server/example/packages/users-workspace/package.json

@@ -10,14 +10,14 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.25",
-    "@jskit-ai/resource-crud-core": "0.1.210",
-    "@jskit-ai/users-core": "0.2.26",
-    "@jskit-ai/workspaces-core": "0.2.26"
+    "@jskit-ai/crud-core": "0.2.27",
+    "@jskit-ai/resource-crud-core": "0.1.212",
+    "@jskit-ai/users-core": "0.2.28",
+    "@jskit-ai/workspaces-core": "0.2.28"
   },
   "peerDependencies": {
-    "@jskit-ai/kernel": "0.2.18",
-    "@jskit-ai/resource-runtime": "0.2.22"
+    "@jskit-ai/kernel": "0.2.19",
+    "@jskit-ai/resource-runtime": "0.2.24"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/workspaces/workspace-server/PATTERN.md

@@ -34,6 +34,22 @@ the other palette fields) that new workspaces start with.
 Use workspace routes, resources, scope helpers, tenancy profiles, and settings
 contracts exported by `@jskit-ai/workspaces-core`.
 
+## Role permissions
+
+A role's `permissions` grant names that something requires:
+
+| Grant | Covers |
+| --- | --- |
+| `crud.<namespace>.list`, `.view`, `.create`, `.update`, `.delete` | A workspace CRUD operation; an HTTP `PATCH` is `update` |
+| `crud.<namespace>.<action name>` | A custom CRUD action |
+| `<prefix>.*`, `*` | Every required permission under the prefix; every permission |
+
+At startup a grant that covers no permission an action, a route's `permission`
+or a surface access policy requires stops the server outside production, with
+a "did you mean"; production logs it. List a permission the application checks
+itself (a service, a row policy, `access.can()`) in
+`roleCatalog.customPermissions`.
+
 ## Role display labels
 
 Each `roleCatalog.roles[roleId]` definition may include an optional string

package/skills/jskit/references/typed-features.md

@@ -478,6 +478,13 @@ record declares `mode: "patch"`; a command never does.**
 - An input field lists its allowed values with `enum`; the kernel refuses
   `oneOf` on an input field at startup, because json-rest-schema checks no
   `oneOf` and the field would accept any value.
+- A check of the input that the schema cannot make until the application
+  runs (a value only boot resolves, such as the types a CRUD read's includes
+  reach) is the definition's `checkInput(input)`, never a check inside
+  `execute`. The kernel runs it on the validated input before the action and
+  answers the field errors it throws (`createValidationError`) as an
+  `ACTION_VALIDATION_FAILED`, exactly as a schema refusal, so HTTP clients and
+  assistant tools are told the field to correct.
 
 Why: a command whose required field is never enforced reaches the service
 without it.
@@ -1005,6 +1012,10 @@ and Vitest's `maxWorkers` come from `testConcurrency()`.**
   `node --test` and sets `--test-concurrency` to the budget.
   `testConcurrency()` from `@jskit-ai/jskit-catalog/test-budget` returns the
   same number for a config.
+- A Node test file is named `<name>.test.js`, and a database test
+  `<name>.integration.test.js`: given no files, `jskit test` runs node's
+  default pattern and fails on a `tests/` file it would leave out, such as
+  `<name>.integration.js` or `<name>.spec.js`.
 - No script passes a fixed concurrency or worker count. `jskit check` fails a
   package script that runs `node --test` directly or passes one, and a
   Playwright or Vitest config those scripts use whose workers do not come from