@jskit-ai/agent-docs 0.1.241 → 0.1.243

package/skills/jskit/references/patterns/connectors/redshift-queries/PATTERN.md

@@ -42,7 +42,7 @@ invoking the service. Matching the configured warehouse is only a target check.
 The library does not resolve ambient AWS profiles or switch to a more privileged
 account after a denial. The application resolves its own credential bindings; editable references do
 not grant AWS permissions. This shared credential mode has no provider callback
-URL and does not depend on an Online registration or allocation.
+URL and does not depend on a hosting platform's registration or allocation.
 
 ## Framework APIs
 

package/skills/jskit/references/patterns/crud/crud-screen-set/PATTERN.md

@@ -76,9 +76,19 @@ id (or a distinct new-record marker) so form cache entries stay separate.
 The New/Edit examples supply it; list/view screen wrappers derive their
 standard keys from `resourceNamespace`.
 
+Each form fact has one input. `resource`, `input`, `buildPayload`,
+`mapPayloadToModel` and `createModel` are top-level `useCrudAddEditScreen()`
+options; `addEditOptions` carries only request and route options for
+`useAddEdit()` (such as `apiSuffix`, `queryKeyFactory`, `readEnabled`,
+`writeMethod`, URL templates, permissions, `client`, `transport` and
+`onSaveSuccess`) and rejects anything else. The save-error message is
+`addEditOptions.fallbackSaveError` when given, otherwise the resource's
+`messages.saveError`; the request error and its toast use the same string.
+
 Save navigation is configured in the top-level `saveSuccess` object. The default
 prefers a configured record-view URL, then the list. A create-and-list variation
-sets `navigateToView: false` and `listUrlTemplate` to its list route. Set both
+sets `navigateToView: false` and `saveSuccess.listUrlTemplate` to its list
+route; `addEditOptions.listUrlTemplate` does not drive save navigation. Set both
 `navigateToView` and `navigateToList` to `false` to stay on the form. A custom
 `addEditOptions.onSaveSuccess` replaces default invalidation and navigation;
 it is unnecessary for ordinary list navigation. The generic CRUD guide explains

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

@@ -8,8 +8,8 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.1.256",
-    "@jskit-ai/resource-crud-core": "0.1.187"
+    "@jskit-ai/crud-core": "0.1.257",
+    "@jskit-ai/resource-crud-core": "0.1.188"
   },
   "jskit": {
     "kind": "runtime",

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

@@ -8,6 +8,6 @@
     "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime-mysql": "0.1.243"
+    "@jskit-ai/database-runtime-mysql": "0.1.244"
   }
 }

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

@@ -8,6 +8,6 @@
     "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime-postgres": "0.1.242"
+    "@jskit-ai/database-runtime-postgres": "0.1.243"
   }
 }

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

@@ -2,7 +2,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/realtime": "0.1.243",
-    "@jskit-ai/shell-web": "0.1.250"
+    "@jskit-ai/realtime": "0.1.245",
+    "@jskit-ai/shell-web": "0.1.252"
   }
 }

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

package/skills/jskit/references/patterns/server/feature-package/example/booking-engine/src/server/actions.js

@@ -14,8 +14,6 @@ function createActions({ bookingEngine } = {}) {
       input: statusQueryInputValidator,
       output: null,
       idempotency: "none",
-      audit: { actionName: ACTION_GET_STATUS },
-      observability: {},
       async execute(input) {
         return bookingEngine.readStatus(input);
       }

package/skills/jskit/references/patterns/server/feature-package/example/variations/AvailabilityEngineProvider.js

@@ -1,5 +1,5 @@
 import { defineFeature } from "@jskit-ai/kernel/server/features";
-import { emptyInputValidator } from "@jskit-ai/kernel/shared/actions/actionContributorHelpers";
+import { emptyInputValidator } from "@jskit-ai/kernel/server/actions/actionContributorHelpers";
 import { createService } from "./orchestratorService.js";
 
 const AvailabilityEngineProvider = defineFeature({

package/skills/jskit/references/patterns/server/feature-package/example/variations/InvoiceRollupProvider.js

@@ -1,5 +1,5 @@
 import { defineFeature } from "@jskit-ai/kernel/server/features";
-import { emptyInputValidator } from "@jskit-ai/kernel/shared/actions/actionContributorHelpers";
+import { emptyInputValidator } from "@jskit-ai/kernel/server/actions/actionContributorHelpers";
 import { createRepository } from "./repository.js";
 
 const InvoiceRollupProvider = defineFeature({

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

@@ -43,10 +43,24 @@ placement registry, topology, and adaptive smoke helper exported by
   above the content so they never cover it. A full-viewport fixed screen on
   such a surface starts at `var(--shell-error-banners-inline-height, 0px)`, as
   `@jskit-ai/auth-web`'s login and reset views do.
-- Restyle shell chrome through its `--shell-chrome-*`, `--shell-app-bar-*`,
-  `--shell-navigation-*` and `--shell-bottom-navigation-*` custom properties,
-  not by overriding Vuetify internals; a Material 3 restyle removes the dividers
-  and separates surfaces tonally.
+- Restyle shell chrome through its custom properties, not by overriding
+  Vuetify internals: `--shell-chrome-border-width` and
+  `--shell-chrome-border-color` for the shared dividers,
+  `--shell-app-bar-border-width`, `--shell-navigation-border-width` and
+  `--shell-bottom-navigation-border-width` per edge, and
+  `--shell-app-bar-background`, `--shell-navigation-background` and
+  `--shell-bottom-navigation-background` for the surfaces. The defaults keep
+  one thin divider on each separating edge, because Vuetify's default themes
+  define no Material 3 surface-container roles. A Material 3 restyle sets the
+  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.
 - The adaptive browser check closes navigation through its public close control.
 
 ## Example files

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

@@ -15,16 +15,16 @@ const healthQuery = useQuery({
 });
 
 const health = computed(() => {
-  if (healthQuery.isPending.value || healthQuery.isFetching.value) {
-    return "loading...";
-  }
-
   if (healthQuery.error.value) {
     return "unreachable";
   }
 
   return healthQuery.data.value?.ok ? "ok" : "unhealthy";
 });
+
+const healthPending = computed(
+  () => healthQuery.isPending.value || healthQuery.isFetching.value
+);
 </script>
 
 <template>
@@ -36,7 +36,13 @@ const health = computed(() => {
     <v-sheet rounded="lg" border class="home-surface-screen__panel">
       <div class="home-surface-screen__status">
         <span class="text-caption text-medium-emphasis">Service health</span>
-        <strong>{{ health }}</strong>
+        <v-skeleton-loader
+          v-if="healthPending"
+          aria-label="Loading service health"
+          class="home-surface-screen__health-skeleton"
+          type="text"
+        />
+        <strong v-else>{{ health }}</strong>
       </div>
       <v-divider vertical class="d-none d-sm-block" />
       <div class="home-surface-screen__status">
@@ -71,6 +77,10 @@ const health = computed(() => {
   min-width: 9rem;
 }
 
+.home-surface-screen__health-skeleton {
+  max-width: 5rem;
+}
+
 @media (max-width: 640px) {
   .home-surface-screen__actions :deep(.v-btn) {
     min-height: 48px;

package/skills/jskit/references/patterns/shell/application-shell/example/tests/e2e/adaptive-shell.spec.ts

@@ -1,7 +1,7 @@
 import { expect, test } from "@playwright/test";
 import { DEFAULT_VIEWPORTS, runAdaptiveShellSmokeCase } from "@jskit-ai/shell-web/test/adaptiveShellSmoke";
 
-test.describe("generated adaptive shell smoke", () => {
+test.describe("adaptive shell smoke", () => {
   for (const viewport of DEFAULT_VIEWPORTS) {
     test(`${viewport.name} layout has reachable navigation and no horizontal overflow`, async ({ page }) => {
       await runAdaptiveShellSmokeCase({ page, expect, viewport });

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

@@ -9,8 +9,8 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.1.256",
-    "@jskit-ai/resource-crud-core": "0.1.187"
+    "@jskit-ai/crud-core": "0.1.257",
+    "@jskit-ai/resource-crud-core": "0.1.188"
   },
   "jskit": {
     "kind": "runtime",

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

@@ -9,9 +9,9 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.1.256",
-    "@jskit-ai/resource-crud-core": "0.1.187",
-    "@jskit-ai/workspaces-core": "0.1.223"
+    "@jskit-ai/crud-core": "0.1.257",
+    "@jskit-ai/resource-crud-core": "0.1.188",
+    "@jskit-ai/workspaces-core": "0.1.224"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/ui-operations.md

@@ -50,16 +50,8 @@ shared-screen controls; avoid duplicates, drawer-only access, or adding a page
 heading just to house it. Keep its meaning and accessible name clear at every
 supported width.
 
-### Scroll position
-
-`createShellRouter()` from `@jskit-ai/kernel/client` installs
-`shellScrollBehavior` by default: a new screen opens at the top (or at its
-hash target), Back/Forward restore the saved position, and query, hash, tab or
-sub-view changes within the same page keep the current position. A tab or
-sub-view counts as the same page when both locations share a parent page record
-below the surface root. Pass `scrollBehavior` to `createShellRouter()` to
-replace it with your own Vue Router function, or `scrollBehavior: false` to
-disable it. Do not wrap the router or reset scroll in page components.
+`createShellRouter()` owns scroll position (`shell/application-shell`
+pattern); never reset scroll in page components.
 
 ## Application-owned files
 
@@ -70,16 +62,10 @@ hash, pattern receipt, or tool-owned source declaration.
 
 ## Screen behavior
 
-- Keep screens phone/task-first with drawer-independent primary actions and
-  at least 48 CSS-pixel targets.
-- Never add page headers or standalone headings unless the user explicitly asks.
+- Keep screens phone/task-first with drawer-independent primary actions.
 - Use direct surfaces instead of needless nested cards.
 - Render all meaningful loading, empty, error, permission, and retry states.
-- Use structure-matching Material skeletons for visible loading; never use a
-  generic spinner or circular progress indicator.
-- Keep read failures local when the screen cannot render. Present transient
-  command success/failure through shared toast/snackbar feedback so the page
-  does not jump.
+- Follow the Material 3 contract for targets, loading and failure feedback.
 - Extend shared CRUD screens through public slots and composables.
 - Keep row actions and filters near the screen unless the framework owns them.
 - Import neutral request and CRUD UI APIs from `@jskit-ai/http-web`. Install
@@ -99,18 +85,8 @@ icon/label and label/end gaps. The normal 80px rail centres 48px targets;
 `railWidth` and `drawerWidth` are public density/width controls. Do not override
 the shell's private implementation CSS.
 
-The app bar, drawer/rail and compact bottom navigation follow the Vuetify theme
-and expose restyling tokens instead of hard-coded chrome: `--shell-chrome-border-width`
-and `--shell-chrome-border-color` for the shared dividers,
-`--shell-app-bar-border-width`, `--shell-navigation-border-width` and
-`--shell-bottom-navigation-border-width` per edge, and
-`--shell-app-bar-background`, `--shell-navigation-background` and
-`--shell-bottom-navigation-background` for the surfaces. The defaults keep one
-thin divider on each separating edge, because Vuetify's default themes define
-no Material 3 surface-container roles to separate surfaces tonally. A Material 3
-restyle sets the border widths to `0` and gives navigation a tonal surface, for
-example `--shell-navigation-background: rgb(var(--v-theme-surface-container-low))`
-when the theme defines that role.
+Restyle shell chrome only through the `--shell-*` tokens in the
+`shell/application-shell` pattern.
 
 ## Browser verification
 

package/templates/app/AGENTS.md

@@ -1,38 +0,0 @@
-# App Agent Instructions
-
-Use current project context, JSKIT public APIs, and the official framework
-documentation as the source of truth for application work.
-
-Framework references:
-
-- `https://mobily-enterprises.github.io/jskit-ai/guide/`
-- `https://mobily-enterprises.github.io/jskit-ai/patterns/`
-
-Before implementation, read the narrow relevant source pattern completely. If
-its owner package is installed, prefer that version-matched package-owned copy.
-Do not install an unrelated runtime package only to read documentation.
-
-Before adding or changing browser-test setup, read `patterns/ui-testing.md` in
-this package. Routine tests reuse the isolated schema and prepare fixtures once
-per suite invocation. Keep `BROWSER_TEST_DB_NAME` distinct from disposable
-`TEST_DB_NAME` and prove that disposable cleanup preserves browser migrations.
-Require repeat-start regression proof; do not rebuild the
-database or production frontend for each focused browser check.
-
-Keep verification output small. Run the relevant cases together, save complete
-stdout/stderr to local artifacts, and preserve the exit status. Report counts,
-duration, failed case names and artifact paths; read only actionable failure
-excerpts. Do not dump full JSON/TAP reports, passing assertions, request logs or
-traces into agent context. Wait on the existing run instead of restarting it or
-repeatedly printing unchanged output. Keep startup and cleanup errors visible.
-For browser evidence, use existing automated cases, targeted locators and
-meaningful visual checkpoints. Avoid a full DOM snapshot or screenshot after
-every action; retain the required viewport, identity and security checks.
-
-Pages never start with a page header, title block, welcome heading, or other
-standalone heading copy. Start with the useful content and actions. If the user
-wants a heading, they will ask for or add one.
-
-Copied pattern source is ordinary application source. Do not add generator
-provenance, receipts, completion ledgers, or tooling-operation history. Keep
-changes scoped to the user request and verify runtime behavior directly.