@jskit-ai/agent-docs 0.1.192 → 0.1.194

package/skills/jskit/references/patterns/app/shell-foundation/example/package.json

@@ -34,7 +34,7 @@
   "dependencies": {
     "@local/main": "0.1.0",
     "@fastify/static": "^10.1.3",
-    "@jskit-ai/kernel": "0.1.220",
+    "@jskit-ai/kernel": "0.1.222",
     "@tanstack/vue-query": "^5.101.0",
     "fastify": "^5.8.5",
     "json-rest-schema": "^1.0.17",
@@ -42,15 +42,15 @@
     "vue": "^3.5.43",
     "vue-router": "^5.3.1",
     "vuetify": "^4.1.2",
-    "@jskit-ai/http-runtime": "0.1.218",
+    "@jskit-ai/http-runtime": "0.1.220",
     "@mdi/js": "^7.4.47",
-    "@jskit-ai/shell-web": "0.1.224",
+    "@jskit-ai/shell-web": "0.1.226",
     "@fastify/fast-json-stringify-compiler": "^5.1.0",
     "@vue/devtools-api": "^8.2.1"
   },
   "devDependencies": {
-    "@jskit-ai/config-eslint": "0.1.217",
-    "@jskit-ai/jskit-catalog": "0.1.245",
+    "@jskit-ai/config-eslint": "0.1.219",
+    "@jskit-ai/jskit-catalog": "0.1.247",
     "@playwright/test": "1.61.1",
     "@vitejs/plugin-vue": "^6.0.7",
     "eslint": "^10.8.0",

package/skills/jskit/references/patterns/app/shell-foundation/example/packages/main/package.json

@@ -9,7 +9,7 @@
   },
   "description": "App-local runtime composition and lightweight glue.",
   "dependencies": {
-    "@jskit-ai/kernel": "0.1.220"
+    "@jskit-ai/kernel": "0.1.222"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/auth/supabase-auth/example/package.json

@@ -2,6 +2,6 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/auth-provider-supabase-core": "0.1.217"
+    "@jskit-ai/auth-provider-supabase-core": "0.1.219"
   }
 }

package/skills/jskit/references/patterns/connectors/calendar-cli/example/package.json

@@ -7,10 +7,10 @@
     "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
   },
   "dependencies": {
-    "@jskit-ai/connectors-core": "0.1.37",
-    "@jskit-ai/connector-google-calendar": "0.1.37",
-    "@jskit-ai/database-runtime": "0.1.220",
-    "@jskit-ai/database-runtime-mysql": "0.1.218",
+    "@jskit-ai/connectors-core": "0.1.39",
+    "@jskit-ai/connector-google-calendar": "0.1.39",
+    "@jskit-ai/database-runtime": "0.1.222",
+    "@jskit-ai/database-runtime-mysql": "0.1.220",
     "knex": "^3.1.0"
   }
 }

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.231",
-    "@jskit-ai/resource-crud-core": "0.1.162"
+    "@jskit-ai/crud-core": "0.1.233",
+    "@jskit-ai/resource-crud-core": "0.1.164"
   },
   "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.218"
+    "@jskit-ai/database-runtime-mysql": "0.1.220"
   }
 }

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.217"
+    "@jskit-ai/database-runtime-postgres": "0.1.219"
   }
 }

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.217",
-    "@jskit-ai/shell-web": "0.1.224"
+    "@jskit-ai/realtime": "0.1.219",
+    "@jskit-ai/shell-web": "0.1.226"
   }
 }

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

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.231",
-    "@jskit-ai/resource-crud-core": "0.1.162"
+    "@jskit-ai/crud-core": "0.1.233",
+    "@jskit-ai/resource-crud-core": "0.1.164"
   },
   "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.231",
-    "@jskit-ai/resource-crud-core": "0.1.162",
-    "@jskit-ai/workspaces-core": "0.1.198"
+    "@jskit-ai/crud-core": "0.1.233",
+    "@jskit-ai/resource-crud-core": "0.1.164",
+    "@jskit-ai/workspaces-core": "0.1.200"
   },
   "jskit": {
     "kind": "runtime",

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

@@ -30,52 +30,47 @@ contracts exported by `@jskit-ai/workspaces-core`.
 
 ## Transactional invitation participation
 
-Use the existing `workspaces.core` capability. During application feature setup,
-register one callback with
+Through `workspaces.core`, register one callback during feature setup with
 `workspaces.services.pendingInvitations.registerAcceptanceParticipant(fn)`.
 The built-in `workspace.invite.redeem` action invokes
-`fn({ invite, user }, { trx, context })` after recipient/state/expiry validation
-and membership activation inside the same uncommitted managed transaction.
-Forward `trx` to every application owner; throw on invalid reviewed associations
-or failed writes. The framework marks accepted and commits only after success.
-Do not perform external effects or complete the transaction in the participant.
-Non-functions, duplicate registrations and registrations after acceptance/refusal
-begins reject. Ordinary invitations can pass through without an association;
-expected-but-missing, stale, revoked or conflicting associations must fail closed.
-
-For deliberate invitation creation, use `members.prepareInvite(workspace, actor,
+`fn({ invite, user }, { trx, context })` after validating the recipient, state and
+expiry and activating membership in the uncommitted transaction. Forward `trx`
+to every application owner and propagate failures. JSKIT marks accepted and
+commits after the callback succeeds. Keep external effects out of the callback.
+Registration rejects non-functions, duplicates and calls after acceptance/refusal
+begins. Allow ordinary invitations; reject stale, revoked, conflicting or
+unexpectedly missing application associations.
+
+Use `members.prepareInvite(workspace, actor,
 payload, { trx, context })` in `repositories.workspaceInvites.withTransaction`
 or the same JSON REST API's managed `transaction`. It returns
 `{ createdInviteId, inviteTokenPreview }` without delivery. Lock the workspace
 with `repositories.workspaceInvites.lockWorkspaceForInvitations(workspace.id,
 { trx })` before application draft/receipt rows, and save the exact invitation
-association and retry receipt before commit. Failed association restores any
-prior pending invitation. A draft of intended access should not call preparation.
+association and retry receipt before commit. Failure restores the previous
+pending invitation. Keep access drafts separate: preparation creates a real token.
 
 After confirmed commit, call `members.sendInvite(workspace, actor, prepared,
 { context })`. A later attempt can pass only `{ createdInviteId }`. Delivery
-reloads the committed pending invitation and uses stored recipient/role/expiry;
-it does not replace the invitation. Its `inviteDelivery` is separate from
-persistence: `mailer_unconfigured` when no mailer is supplied, `failed` on a
-renderer/mailer exception, or the normalized controlled/provider result.
-Interruption or failure may still mean a provider accepted the message. Receipt
-idempotency and delivery retries are application-owned; email is not exactly once.
-Do not log the returned token/URL. No SMTP setup is required for testing.
+reloads the committed pending invitation and uses its saved recipient, role and
+expiry. `inviteDelivery` reports `mailer_unconfigured`, `failed` on a renderer/mailer
+exception, or the normalized mailer result. Persistence is unchanged by delivery
+failure. A provider may accept a message before failing; the application owns
+receipts and retries. Keep tokens/URLs out of logs and use controlled mailers in tests.
 
 `createInvite`, acceptance and refusal now own managed transactions and reject
-borrowed `options.trx`. Move transactional creation to preparation/post-commit
-sending and acceptance-related writes into the participant. Revocation may join
+borrowed `options.trx`. Use preparation followed by delivery after commit for
+transactional creation; put related acceptance writes in the participant. Revocation may join
 a managed transaction. Raw Knex/savepoint transactions cannot own resource
 writes. Invitation mutations lock workspace then invitation rows, revalidate
-current state and reject attempts to overwrite terminal state. Matching-recipient
-expiry rejection commits revocation before returning 409. Preserve transaction
+current state and reject changes to accepted/revoked invitations. Expiry rejection
+for the matching recipient commits revocation before returning 409. Preserve transaction
 outcomes and causes; a completion-hook error after commit cannot undo writes.
 
 See the human guide's **Workspace tenancy → Transactional invitation
 participation** for the full consumer example, errors, controlled mailer,
-compatibility notes and native verification commands. Application services still
-own authorization, identity/training linking, reviewed scope eligibility and
-required audit. This seam adds no application domain tables or policy.
+compatibility notes and native verification commands. Application services own
+authorization, identity/training linking, scope eligibility and required audit.
 
 ## Invariants
 

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

@@ -18,6 +18,38 @@ only when defining or diagnosing topology. Resolve current dynamic parameters
 to an absolute URL or route object for sibling/child links—never bind a route
 template or relative string raw to Vue Router `to`.
 
+## Back navigation
+
+Check every page for a visible Back button that returns to the previous page.
+Omit it only when returning makes no product sense, such as the app's root
+landing page or a completed flow that must not reopen an expired step. State
+the reason in the implementation or review result; a drawer link is not Back.
+
+Plain **Back** normally follows the person's actual route history, retaining
+the originating page's query, filters, tab, and pagination. Reuse the existing
+JSKIT screen/navigation owner and its public seams. For history traversal use
+the app's Vue Router instance (`useRouter()` from `vue-router`, then
+[`router.back()`](https://router.vuejs.org/guide/essentials/navigation.html#traverse-history));
+`usePaths().page()` from `@jskit-ai/shell-web/client/navigation/usePaths`
+resolves a destination, not history. Do not invent a second navigation stack.
+
+For direct links, new tabs, or no usable in-app history, use a deliberate safe
+fallback resolved through the existing surface/workspace-aware path helpers.
+Do not infer a usable previous page from `window.history.length` alone or send
+people outside the app unexpectedly. Keep existing unsaved-change guards.
+
+A fixed parent/list destination is valid when the task calls for it; name it
+explicitly, for example **Back to appointments**. It must not silently replace
+ordinary Back. Shared CRUD `listLocation`/`listUrlTemplate` links are fixed
+destinations, not proof of previous-page behavior. Keep Back distinct from
+Cancel, Close, and a wizard's Previous step.
+
+Place Back consistently near the start of the page's existing action region,
+before forward/primary actions in reading and keyboard order. Reuse shell or
+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.
+
 ## Application-owned files
 
 Pattern source is ordinary customizable application source. When replacing a
@@ -62,6 +94,9 @@ Exercise user-facing changes with Playwright at compact, medium, and expanded
 widths. Check overflow, clipped text, duplicate navigation, route placement,
 actions, skeleton replacement, error feedback, and target sizes. Use relative
 URLs. When `PLAYWRIGHT_BASE_URL` is provided, start no duplicate server.
+For Back, enter the same page from two different origins and verify each
+returns to its own origin with context intact. Also check direct entry, reload,
+browser back/forward, fixed-destination exceptions, and any unsaved-change guard.
 
 Vibe64 owns its managed browser and may provide
 `VIBE64_PLAYWRIGHT_STORAGE_STATE`; never print or commit that value, bypass it,