@jskit-ai/agent-docs 0.1.279 → 0.1.281

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.10",
+    "@jskit-ai/kernel": "0.2.12",
     "json-rest-schema": "^1.0.17"
   },
   "exports": {

package/skills/jskit/references/patterns/shell/application-shell/PATTERN.md

@@ -55,12 +55,17 @@ placement registry, topology, and adaptive smoke helper exported by
   border widths to `0` and gives navigation a tonal surface, for example
   `rgb(var(--v-theme-surface-container-low))` when the theme defines it.
 - `createShellRouter()` from `@jskit-ai/kernel/client` installs
-  `shellScrollBehavior`: a new screen opens at the top (or its hash target),
-  Back/Forward restore the saved position, and query, hash, tab or sub-view
-  changes within the same page keep it. A tab or sub-view is the same page when
-  both locations share a parent page record below the surface root. Pass
-  `scrollBehavior` to replace it, or `scrollBehavior: false` to disable it; do
-  not wrap the router or reset scroll in page components.
+  `shellScrollBehavior`: a new screen opens at the top (or its hash target,
+  below the target's `scroll-margin-top`), Back/Forward restore the saved
+  position, and query, hash, tab or sub-view changes within the same page keep
+  it. A tab or sub-view is the same page when both locations share a parent
+  page record below the surface root that draws a component, a layout hosting
+  the tabs; a folder's component-less record, as file routing creates for
+  `bookings/`, makes its pages different pages. Pass `scrollBehavior` to replace it
+  (calling `shellScrollBehavior` for what it leaves to the shell), or
+  `scrollBehavior: false` to disable it. A `createRouter` that replaces the
+  behaviour it is given throws, so never set one there; do not wrap the router
+  or reset scroll in page components.
 - The adaptive browser check closes navigation through its public close control.
 
 ## Example files

package/skills/jskit/references/patterns/shell/application-shell/example/src/components/menus/SectionTabLinkItem.vue

@@ -0,0 +1,42 @@
+<script setup>
+import ShellSectionTabLinkItem from "@jskit-ai/shell-web/client/components/ShellSectionTabLinkItem";
+
+const props = defineProps({
+  label: {
+    type: String,
+    default: ""
+  },
+  to: {
+    type: String,
+    default: ""
+  },
+  icon: {
+    type: String,
+    default: ""
+  },
+  surface: {
+    type: String,
+    default: ""
+  },
+  scopedSuffix: {
+    type: String,
+    default: "/"
+  },
+  unscopedSuffix: {
+    type: String,
+    default: "/"
+  },
+  disabled: {
+    type: Boolean,
+    default: false
+  },
+  exact: {
+    type: Boolean,
+    default: false
+  }
+});
+</script>
+
+<template>
+  <ShellSectionTabLinkItem v-bind="props" />
+</template>

package/skills/jskit/references/patterns/shell/application-shell/example/src/pages/home.vue

@@ -14,7 +14,7 @@ import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

package/skills/jskit/references/patterns/shell/application-shell/example/src/views/NotFound.vue

@@ -6,7 +6,7 @@ const message = "The page you requested does not exist.";
 
 <template>
   <!-- The shell's top app bar carries the title, and its navigation leads back into the app. -->
-  <ShellLayout title="Not Found" subtitle="">
+  <ShellLayout title="Not Found">
     <section class="d-flex flex-column align-center text-center on-surface-variant py-16">
       <v-icon icon="$searchOff" size="48" />
       <p class="text-body-large mt-4 mb-0">{{ message }}</p>

package/skills/jskit/references/patterns/ui/page-and-placement/PATTERN.md

@@ -35,6 +35,12 @@ a filename alone.
 - Child links share an explicit section owner.
 - Topology maps each semantic placement to concrete responsive outlets.
 - Placed components are registered by token through a client provider.
+- Section navigation is Material 3 primary tabs: the section's `page.section-nav`
+  topology names a section-tab renderer (`ShellSectionTabLinkItem`, registered as
+  `local.main.ui.section-tab-link-item`), and the page draws the tab row (one
+  row over a 1dp `outline-variant` divider that scrolls sideways). A navigation
+  bar destination (`ShellTabLinkItem`) belongs to the shell's navigation bar
+  only; placed in a page it draws a section tab.
 - Compact navigation controls remain accessible and at least 48 CSS pixels.
 - Application source has no generated-file marker, receipt, or overwrite state.
 

package/skills/jskit/references/patterns/ui/page-and-placement/example/src/pages/home/reports.vue

@@ -8,10 +8,9 @@ definePage({ meta: { jskit: { title: "Reports" } } });
 
 <template>
   <section class="reports-section d-flex flex-column ga-4">
-    <nav aria-label="Report sections">
-      <v-tabs>
-        <ShellOutlet target="reports:section-nav" />
-      </v-tabs>
+    <!-- Material 3 primary tabs: one row over a divider, scrolling sideways when the tabs don't fit. -->
+    <nav class="reports-section__tabs" aria-label="Report sections">
+      <ShellOutlet target="reports:section-nav" />
     </nav>
 
     <div class="reports-section__content">
@@ -25,4 +24,10 @@ definePage({ meta: { jskit: { title: "Reports" } } });
 .reports-section__content {
   min-width: 0;
 }
+
+.reports-section__tabs {
+  border-bottom: 1px solid rgb(var(--v-theme-outline-variant));
+  display: flex;
+  overflow-x: auto;
+}
 </style>

package/skills/jskit/references/patterns/ui/page-and-placement/example/src/placementTopology.js

@@ -4,6 +4,8 @@ function addPlacementTopology(value = {}) {
   placements.push(value);
 }
 
+// The section's tabs: Material 3 primary tabs at every width (the shell's section-tab renderer), never navigation bar
+// destinations, which belong to the shell's navigation bar alone.
 addPlacementTopology({
   id: "page.section-nav",
   owner: "reports",
@@ -12,15 +14,15 @@ addPlacementTopology({
   variants: {
     compact: {
       outlet: "reports:section-nav",
-      renderers: { link: "local.main.ui.tab-link-item" }
+      renderers: { link: "local.main.ui.section-tab-link-item" }
     },
     medium: {
       outlet: "reports:section-nav",
-      renderers: { link: "local.main.ui.tab-link-item" }
+      renderers: { link: "local.main.ui.section-tab-link-item" }
     },
     expanded: {
       outlet: "reports:section-nav",
-      renderers: { link: "local.main.ui.tab-link-item" }
+      renderers: { link: "local.main.ui.section-tab-link-item" }
     }
   }
 });

package/skills/jskit/references/patterns/users/account-settings/PATTERN.md

@@ -38,6 +38,18 @@ app's language; the app does, for example
 `watch(useAccountLocale(), (code) => { if (code) i18n.global.locale.value = code; }, { immediate: true })`.
 Section titles may be plain text, a message key or `{ key, fallback }`.
 
+Sections are pages of the account surface, in Material 3's list-detail layout
+(shell-web's `ShellListDetail`): `/account` is the section list
+(`src/pages/account/index.vue`) and `/account/<section>` one section
+(`src/pages/account/[section].vue`, its `value`, such as
+`/account/preferences`), both rendering `AccountSettingsClientElement`, which
+reads the section from the route's `section` param. The section page's parent
+is the list, the surface's `"/"`. A phone or medium window shows the list or one
+section, and Up returns from the section to the list; an expanded or large
+window shows the list beside the open section, or beside the first section on
+the list's own page. A link to a section is its path, `/account/invites`, with
+`returnTo` in the query for Done.
+
 `runtime.signInMethods.methods` lists the auth provider's OAuth sign-in
 methods as `{ provider, label, linked, canLink, canUnlink }`, read from the
 settings security status. `link(provider)` leaves for the provider through
@@ -59,12 +71,19 @@ provider offers provider linking (`providerLinking` in its capabilities).
 - The route and placement owner agree.
 - The account surface renders in its own layout, `src/pages/account.vue`
   (`ShellLayout` around `<RouterView />`, `meta.jskit.surface: "account"`), so
-  the settings page's title, Up arrow and Done action are in the top app bar.
+  the settings page's title and Up arrow are in the top app bar. Up is the
+  page's only way out; `AccountSettingsClientElement` adds a Done action only
+  where Up can't go back (no parent, a section beside the list on a wide
+  window, or a returnTo on another origin).
   With no navigation items, the surface shows no navigation bar, rail or drawer.
+- Each section has its own address, `/account/<section>`, served by
+  `src/pages/account/[section].vue` with parent `"/"`; nothing selects a
+  section through the query.
 
 ## Example files
 
-`example/` contains the account surface's layout, an account route and four
+`example/` contains the account surface's layout, the section list's route
+(`account/index.vue`), a section's route (`account/[section].vue`) and four
 concrete settings sections.
 Adapt their fields and copy while retaining the shared account runtime.
 
@@ -77,7 +96,9 @@ notification vocabulary while keeping server-owned validation authoritative.
 
 Navigate away and back with warm cache, exercise browser back/forward, save and
 clear fields, verify toast errors, inspect skeleton geometry, and test keyboard
-operation at compact and expanded widths.
+operation at compact and expanded widths. At 390 px check that the list and a
+section show one at a time and Up returns from the section to the list; at
+1280 px that the list shows beside the open section, with no Up.
 
 ## Avoid
 

package/skills/jskit/references/patterns/users/account-settings/example/src/components/account/settings/AccountSettingsNotificationsSection.vue

@@ -35,11 +35,11 @@ const notifications = props.runtime.notifications;
           color="primary"
           hide-details
           disabled
-          class="mb-4"
         />
         <v-btn
           type="submit"
           color="primary"
+          class="mt-4"
           :loading="notifications.isSaving.value"
           :disabled="notifications.isRefreshing.value"
         >

package/skills/jskit/references/patterns/users/account-settings/example/src/components/account/settings/AccountSettingsPreferencesSection.vue

@@ -94,7 +94,7 @@ const preferences = props.runtime.preferences;
             />
           </v-col>
 
-          <v-col cols="12" md="3">
+          <v-col cols="12" md="4">
             <v-select
               v-model.number="preferences.form.avatarSize"
               label="Avatar size"
@@ -110,6 +110,7 @@ const preferences = props.runtime.preferences;
         <v-btn
           type="submit"
           color="primary"
+          class="mt-4"
           :loading="preferences.isSaving.value"
           :disabled="preferences.isRefreshing.value"
         >

package/skills/jskit/references/patterns/users/account-settings/example/src/components/account/settings/AccountSettingsProfileSection.vue

@@ -51,7 +51,7 @@ const profile = props.runtime.profile;
         </v-row>
 
         <v-row>
-          <v-col cols="12" md="6">
+          <v-col cols="12">
             <v-text-field
               v-model="profile.form.displayName"
               label="Display name"
@@ -63,7 +63,7 @@ const profile = props.runtime.profile;
             />
           </v-col>
 
-          <v-col cols="12" md="6">
+          <v-col cols="12">
             <v-text-field
               v-model="profile.form.email"
               label="Email"
@@ -79,6 +79,7 @@ const profile = props.runtime.profile;
         <v-btn
           type="submit"
           color="primary"
+          class="mt-4"
           :loading="profile.isSaving.value"
           :disabled="profile.isDeletingAvatar.value || profile.isRefreshing.value"
         >

package/skills/jskit/references/patterns/users/account-settings/example/src/pages/account/[section].vue

@@ -0,0 +1,23 @@
+<route lang="json">
+{
+  "meta": {
+    "guard": {
+      "policy": "authenticated"
+    },
+    "jskit": {
+      "title": "Account settings",
+      "parent": "/"
+    }
+  }
+}
+</route>
+
+<template>
+  <AccountSettingsClientElement />
+</template>
+
+<script setup>
+// One section of account settings (/account/preferences). Its parent is the section list, the surface's "/", so on a
+// phone Up returns to the list; a wide window shows the list beside the section.
+import AccountSettingsClientElement from "@jskit-ai/users-web/client/components/AccountSettingsClientElement";
+</script>

package/skills/jskit/references/patterns/users/account-settings/example/src/pages/account.vue

@@ -9,14 +9,15 @@
 </route>
 
 <script setup>
-// The account surface's layout: the shell's top app bar carries the settings page's title, its Up arrow back to home
-// and its Done action. The surface has no navigation items, so the shell draws no navigation bar, rail or drawer.
+// The account surface's layout: the shell's top app bar carries the settings page's title and its Up arrow back to
+// home, the page's only way out (a Done action shows only where Up can't go back, such as a returnTo on another of
+// the app's origins). The surface has no navigation items, so the shell draws no navigation bar, rail or drawer.
 import ShellLayout from "@/components/ShellLayout.vue";
 import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

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

@@ -10,8 +10,8 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.11",
-    "@jskit-ai/resource-crud-core": "0.1.201"
+    "@jskit-ai/crud-core": "0.2.13",
+    "@jskit-ai/resource-crud-core": "0.1.203"
   },
   "jskit": {
     "kind": "runtime",

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

@@ -10,9 +10,9 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.11",
-    "@jskit-ai/resource-crud-core": "0.1.201",
-    "@jskit-ai/workspaces-core": "0.2.12"
+    "@jskit-ai/crud-core": "0.2.13",
+    "@jskit-ai/resource-crud-core": "0.1.203",
+    "@jskit-ai/workspaces-core": "0.2.14"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/workspaces/workspace-surfaces/example/packages/main/src/client/components/AccountPendingInvitesCue.vue

@@ -57,16 +57,16 @@ const isVisible = computed(() => {
 
 const resolvedTo = computed(() => {
   const hasAccountSurface = Boolean(resolveSurfaceDefinitionFromPlacementContext(placementContext.value, "account"));
+  // The invitations section of account settings, /account/invites.
   const accountSettingsPath = hasAccountSurface
-    ? resolveSurfacePathFromPlacementContext(placementContext.value, "account", "/")
-    : "/account";
+    ? resolveSurfacePathFromPlacementContext(placementContext.value, "account", "/invites")
+    : "/account/invites";
   const accountSettingsNavigation = resolveSurfaceNavigationTargetFromPlacementContext(placementContext.value, {
     path: accountSettingsPath,
     surfaceId: "account"
   });
 
   const query = new URLSearchParams({
-    section: "invites",
     returnTo: accountSettingsNavigation.sameOrigin ? resolveReturnTo() : resolveReturnToHref()
   });
   return appendQueryString(accountSettingsPath, query.toString());

package/skills/jskit/references/patterns/workspaces/workspace-surfaces/example/src/surfaces/admin/root.vue

@@ -14,7 +14,7 @@ import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

package/skills/jskit/references/patterns/workspaces/workspace-surfaces/example/src/surfaces/app/root.vue

@@ -14,7 +14,7 @@ import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

package/skills/jskit/references/sanity-checks.md

@@ -0,0 +1,181 @@
+<!-- Generated from `packages/agent-docs/site/guide/framework/sanity-checks.md`. -->
+
+# Sanity checks
+
+Before calling a list, a save, a test, a refactor, a screen or a deployment
+done, measure what it actually costs and does, judge whether that is sane, and
+fix the cause when it is not. This page is the JSKIT part of that: the
+pitfalls JSKIT's own packages cause, then which JSKIT call, helper or setting
+applies each check, with one line on what the check catches and why.
+
+## JSKIT's own pitfalls
+
+### Theme and component defaults
+
+**Check:** after changing a theme, a Vuetify default, a material-web default
+or a shared component, use what it affects in a production build: open a
+select and type, press a segmented button at desktop width, tap neighbouring
+icon buttons, and leave a field to see whether the layout shifts under the
+next tap. A default reaches every component that renders the one it names, so
+a change made for one screen can break others that never import it
+([Material 3](material-3.md)).
+
+**Examples:**
+
+- A `VMenu: { VSheet: {} }` default broke a select's typeahead.
+- A common button padding squeezed segmented buttons into slivers.
+- A field that grew 32 px on blur moved the button under a person's tap.
+
+### Navigation metadata
+
+**Check:** open each inner page directly and by link, and see its Up arrow
+and title. Some navigation declarations look right but switch Up off, and
+some shapes leave pages the navigation rules cannot judge
+([Material 3](material-3.md)):
+
+- a parent declared beside `jskit.surface` is never read; the surface goes on
+  the layout page and the parent on the page it renders (`nav/surface-parent`
+  reports the two on one record);
+- an inner page repeating its surface becomes a root of its own, with no Up;
+- until a main-navigation placement is literal data, no page is judged for a
+  missing parent (`nav/placement-data`);
+- a layout that also renders its pages without `ShellLayout` leaves those
+  pages unjudged by `nav/missing-parent`, so a missing parent passes;
+- a package route is judged only when its client entry lists
+  `routeComponents` literally; a built map passes unjudged.
+
+**Example:** a design-system update moved a page title into a top app bar
+that one page did not have, so its title vanished; only the browser suite
+caught it.
+
+### Generated action and tool contracts
+
+**Check:** call each assistant tool the way the model will, with sparse
+`fields` and an `include`, and compare the result with the output contract it
+advertises. An action is a tool only when it has an input contract and a
+truthful model-facing output; the assistant validates the result against
+`extensions.assistant.output` and rejects unexpected fields, so a contract
+that promises what execution cannot return fails at run time, not at review
+([Assistant](/guide/app-extras/assistant#database-surface-action-tools)).
+
+**Example:** sparse primary fields stay sparse, and an included record is read
+from its lookup container (`items[0].lookups.pet.name`); a contract that
+expects the relationship id or an unselected field never gets it.
+
+## Applying each check
+
+### Every row
+
+- An unpaged JSON:API query returns the first 20 rows, and a page above the
+  resource's `queryMaxLimit` (100 unless it sets one) is cut to that size,
+  both without an error; CRUD `queryDocuments()` refuses such a `limit`. A
+  read its callers treat as complete uses `queryAllJsonRestCollectionRows()`
+  or the repository's `queryEveryDocument()`, because the missing rows
+  otherwise vanish from every picker and delivery built on it
+  ([Every row](typed-features.md#every-row)).
+- A lookup by a unique key matches at most one row, so it may read `rows[0]`
+  of a plain query.
+
+### Query counts and batches
+
+- Count a path's queries with `countQueries()` from
+  `@jskit-ai/database-runtime/server/testDatabases` at a few rows and at a
+  realistic number; the count should follow tables and pages, not rows
+  ([Query counts at realistic
+  sizes](typed-features.md#query-counts-at-realistic-sizes)).
+- A JSON:API read adds a few lookup and visibility queries per page and per
+  relationship field. That follows pages, so it is expected.
+- `getDocumentById()`, `queryDocuments()` or a service `get` inside a loop is
+  the usual per-row read; batch it with an id-list `searchSchema` filter or
+  `include`, grouped with `Map.groupBy()` ([Lists read related rows in
+  batches](typed-features.md#lists-read-related-rows-in-batches)).
+- A `rowPolicy` adds one correlated predicate to the query it is given, so
+  its cost follows the rows read, not the subject's history. It runs on every
+  single-record read, including a write's default `returning: "full"` read
+  back, so a write that discards its result passes `returning: "minimal"` and
+  a batch of creates uses `createDocuments()`, in the owner's transaction
+  ([Bounded access
+  checks](typed-features.md#bounded-access-checks)).
+
+### Tests
+
+- `jskit test` runs test files in parallel within the machine's test budget
+  (`V64_TEST_CONCURRENCY`, else half the CPUs), and Playwright's `workers` and
+  Vitest's `maxWorkers` come from `testConcurrency()`. `jskit check` reports a
+  script or config that runs files one at a time; a file that must run alone
+  says why on its first line, `// jskit-test: alone - <reason>` ([Test files
+  run in parallel](typed-features.md#test-files-run-in-parallel)).
+- Tests use `TEST_DB_NAME` and `BROWSER_TEST_DB_NAME`, both different from
+  `DB_NAME`, because tests write and delete rows and would destroy the
+  developer's data. A skip for want of a test database is a failure.
+- Test databases restore a stored snapshot checked by a digest of the
+  migration and seed sources, and the harness reports each preparation phase's
+  duration, so slow preparation shows ([Test databases are prepared
+  once](typed-features.md#test-databases-are-prepared-once),
+  [integration test
+  databases](/guide/app-setup/database-layer#integration-test-databases)).
+
+### Inputs and access
+
+- An action input declared `mode: "patch"` makes every field optional. Use it
+  only for an action that updates part of a record, and send that action
+  nothing to see what it does, because a missing field is then never refused.
+- A route that repetition can abuse declares `rateLimit`, which the kernel
+  refuses with 429 and `kernel.http.rateLimited`; auth's limits come from
+  `config.auth.rateLimits` ([Sign-in
+  protection](/guide/app-setup/authentication#sign-in-protection)). Each
+  limit needs a test expecting the 429, or a dropped one goes unseen.
+- Who acts comes from `resolveActor(context)` and the workspace from the
+  context's resolvers ([One reader per
+  fact](typed-features.md#one-reader-per-fact)); send another
+  workspace's id in the body and see the context win.
+
+### Refactors
+
+Before changing a JSKIT feature, list where its behaviour lives, with the test
+that covers each item, and walk the list again after: routes, actions and
+their input schemas, row policies, CRUD fields, lookups and hooks, placements
+and navigation meta, messages and their codes, events, jobs and migrations.
+These are the places a consolidation drops behaviour without a failing build.
+
+### Changes others depend on
+
+- After updating JSKIT packages, read [Upgrade
+  JSKIT](/guide/app-setup/upgrading-jskit) and each package changelog's
+  "Upgrading" notes, then boot, sign in and run the browser tests before
+  anything else, because a changed default shows only at run time.
+
+### Screens
+
+- A long list renders what is visible, with pages or `v-virtual-scroll`,
+  because every row rendered costs DOM nodes and main-thread time.
+- Command feedback goes through the shell's snackbar path: `ShellErrorHost`
+  keeps it clear of the FAB and the actions it reports on, and a full-screen
+  dialog puts its confirm action in the top bar, where a snackbar never covers
+  it ([Material 3](material-3.md)).
+- Up is the shell's, from `meta.jskit.parent`; the navigation rules forbid
+  `router.back()` and hand-made back controls, so Up lands inside the app
+  even on a page opened from a link.
+
+### Production settings
+
+- `NODE_ENV=production` is JSKIT's only production switch. Without it a
+  deployed server runs as development: no first-account setup code, and
+  development-only settings accepted.
+- On an empty production database, local auth asks for the first account's
+  setup code, so whoever reaches a new deployment first cannot own it ([The
+  first account in
+  production](/guide/app-setup/authentication#the-first-account-in-production-local-auth)).
+  Give any registration of your own the same protection.
+- `config.securityHeaders` sends the security headers, with the content
+  security policy reported, not enforced, by default; read them on a
+  production build ([Security
+  headers](/guide/app-setup/initial-scaffolding#security-headers)).
+- Email confirmation needs `auth.local.confirmation-sender` in production, or
+  the server refuses to start while anyone may register ([Email
+  confirmation](/guide/app-setup/authentication#email-confirmation-local-auth)).
+- Changing the assistant's instructions needs `assistant.settings.update` or
+  the surface's own permission ([Who may change the
+  instructions](/guide/app-extras/assistant#who-may-change-the-instructions)).
+  Its tools run as the typing user, through the `automation` channel, so an
+  action kept off that channel is never a tool.

package/skills/jskit/references/translation.md

@@ -193,6 +193,10 @@ and params to `details.fieldErrorCodes`, so an untranslated app shows exactly
 the English it showed before. The failed check's own params (for example
 `limit`) are sent too, and the coded entry's `params` win over them. JSKIT's
 own schemas use this form, which is why their field messages translate.
+With json-rest-schema 1.0.18 or later, which checks them, an array field's
+`minItems` and `maxItems` failures send `kernel.validation.field.minItems` and
+`kernel.validation.field.maxItems` with `{ min | max, actual }`, and its
+`messages.minItems` and `messages.maxItems` override them.
 
 ## Placement labels