@jskit-ai/agent-docs 0.1.296 → 0.1.298

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