@jskit-ai/agent-docs 0.1.149 → 0.1.150

package/guide/agent/app-setup/existing-application-migration.md

@@ -50,12 +50,14 @@ generic CRUD merely to make the structure look uniform.
 
 ## 2. Plan one coordinated dependency and capability graph
 
-Use the installed JSKIT pattern index and package metadata to select the
-smallest complete package set. Plan the top-level dependencies and their
-ordinary npm closure before changing the lockfile, then install that planned
-closure once. Review `package.json` and the lockfile as source changes. Adopt
-the supported package-graph scripts and run `npm run jskit:update` before
-changing application source; see the **Upgrade JSKIT** guide in the agent docs.
+Use the [JSKIT source pattern library](/patterns/) and installed package
+metadata to select the smallest complete package set. Do not install an
+unrelated runtime package only to read its pattern. Plan the top-level
+dependencies and their ordinary npm closure before changing the lockfile, then
+install that planned closure once. Review `package.json` and the lockfile as
+source changes. Adopt the supported package-graph scripts and run `npm run
+jskit:update` before changing application source; see the **Upgrade JSKIT**
+guide in the agent docs.
 The updater aligns root and workspace declarations to one published release
 cohort, installs once at the project root, and verifies the resulting lockfile.
 It does not regenerate or synchronize application source.

package/guide/agent/app-setup/initial-scaffolding.md

@@ -13,7 +13,8 @@ agent can copy, adapt, compose, or use as evidence.
 
 ## The adaptive-shell foundation
 
-`app/shell-foundation` is the normal browser-product baseline. It includes:
+[`app/shell-foundation`](/patterns/app/shell-foundation) is the normal
+browser-product baseline. It includes:
 
 - Fastify server and health endpoint
 - Vue/Vite client bootstrap
@@ -29,15 +30,16 @@ when it is wrong for the product.
 
 ## The minimal foundation
 
-`app/minimal-foundation` keeps the same server/client/package boundaries but
-does not install the full adaptive shell. Use it for deliberately small or
-unusual products, not as a temporary hurdle before installing what was already
-known to be required.
+[`app/minimal-foundation`](/patterns/app/minimal-foundation) keeps the same
+server/client/package boundaries but does not install the full adaptive shell.
+Use it for deliberately small or unusual products, not as a temporary hurdle
+before installing what was already known to be required.
 
 ## Safe realization inside an existing repository
 
-Read the entire selected `PATTERN.md` first. Copy or author files directly in
-the initialized project. Always preserve `.git`; when present, also preserve
+Read the entire selected `PATTERN.md` first. Each public pattern page links its
+complete example source tree. Copy or author files directly in the initialized
+project. Always preserve `.git`; when present, also preserve
 existing project and agent context, including roots such as:
 
 ```text

package/guide/agent/app-setup/quickstart.md

@@ -17,19 +17,22 @@ cd exampleapp
 git init -b main
 ```
 
-Ask your agent to read the installed JSKIT skill, then describe the product in
-normal language. The opening conversation should make the product direction
+Give your agent the [JSKIT framework guide](/guide/) and describe the product
+in normal language. The opening conversation should make the product direction
 and any material technology choice clear. Explicitly choose JSKIT and any
 database integration you actually need. JSKIT does not ask the same questions
-again through a framework questionnaire.
+again through a framework questionnaire. An agent host may offer its own
+optional skills, but JSKIT does not require one.
 
 ## Select an application foundation
 
-The installed JSKIT skill and generated pattern index expose two initial
+The [public source pattern library](/patterns/) exposes two initial
 foundations:
 
-- `app/shell-foundation` for the normal responsive application shell
-- `app/minimal-foundation` for an intentionally smaller foundation
+- [`app/shell-foundation`](/patterns/app/shell-foundation) for the normal
+  responsive application shell
+- [`app/minimal-foundation`](/patterns/app/minimal-foundation) for an
+  intentionally smaller foundation
 
 The agent reads `PATTERN.md` and its complete `example/` tree. It copies or
 adapts the pattern into this existing repository, preserving `.git` and any

package/guide/agent/framework/application-operations.md

@@ -0,0 +1,91 @@
+<!-- Generated by `npm run agent-docs:build` from `packages/agent-docs/site/guide/framework/application-operations.md`. Do not edit manually. -->
+
+---
+title: Application operations
+description: Establish a JSKIT application, select capabilities, and realize product features from source patterns.
+---
+
+# Application operations
+
+Use this for establishing an application foundation, selecting package
+capabilities, and realizing product features from JSKIT patterns.
+
+## Establish a new application
+
+Start with an initialized Git repository and a clear product request. Use the
+request, current source, and ordinary project documentation. Ask the user for
+any material missing product decision before writing application source. Do
+not run a JSKIT questionnaire and do not create a temporary scaffold app.
+
+Read the [source pattern library](/patterns/). When the optional standalone
+JSKIT Agent Skill is installed, its pattern index contains the same
+version-matched pattern documents and examples. Do not install a runtime
+package only to read its documentation.
+
+For a browser product, inspect one foundation:
+
+- `app/shell-foundation` for the normal adaptive application shell
+- `app/minimal-foundation` when the product deliberately does not need that
+  shell yet
+
+Inspect the complete pattern before copying. Copy or author the useful files
+directly into the existing project. Preserve `.git` plus all unrelated project
+and agent context. Resolve every real destination collision explicitly.
+Rename the concrete example application in ordinary source and metadata.
+Retain the foundation's npm workspace declaration. App-local packages use
+their own exact versions in dependency declarations; do not replace them with
+`file:` links.
+
+The copied files immediately belong to the application. Do not add pattern
+receipts, generator provenance, completion ledgers, or hidden operation state.
+
+## Install and compose capabilities
+
+Plan the complete capability set before changing dependencies. Use the package
+catalogue and package-owned patterns to identify the required runtime packages,
+configuration, resources, and public APIs. Add one coherent package closure,
+then run `npm install` once for that planned change.
+
+Install the explicitly selected top-level packages through npm. Use one
+installation for the planned closure so npm can resolve their ordinary package
+dependencies together:
+
+```bash
+npm install --save-exact @jskit-ai/<selected-package>@latest [...]
+```
+
+Review the resulting `package.json` and lockfile as ordinary source changes.
+The installed package graph supplies runtime providers, migrations, patterns,
+and public APIs directly; no JSKIT synchronization or mutation command follows
+the npm installation.
+
+Do not add auth, users, workspaces, console, sample data, databases, or AI
+capabilities unless the product choice requires them.
+
+## Author database-backed CRUD
+
+Use a chosen database pattern plus a package-owned CRUD resource pattern. The
+normal order is:
+
+1. confirm the product resource, ownership, operations, and fields
+2. author a migration as normal application source
+3. author the shared resource contract through `resource-crud-core`
+4. use framework APIs for standard repository/service/action/route mechanics
+5. author product-specific screens from the relevant UI pattern
+6. run migrations and direct verification
+
+The database connection and schema are runtime evidence, not a questionnaire
+that owns source generation. Never patch fields into generated ASTs and never
+mark a resource valid because a generator once wrote it.
+
+## Verify current state
+
+Run verification against source, package graph, migrations, and runtime
+behavior. Runtime startup owns the capability/provider graph, loadability,
+ids, environment, and configuration. Builds own client imports; migration
+status and disposable rebuilds own schema state. App lint, tests, audit,
+browser checks, and CI own security, runtimes, and behavior.
+
+There is no supported `jskit doctor` command. Old CLI authoring-history
+warnings do not describe AI-first apps. Diagnose current contracts; never add
+metadata to satisfy an old tool.

package/guide/agent/framework/crud-operations.md

@@ -0,0 +1,83 @@
+<!-- Generated by `npm run agent-docs:build` from `packages/agent-docs/site/guide/framework/crud-operations.md`. Do not edit manually. -->
+
+---
+title: CRUD operations
+description: Implement JSKIT database resources, repositories, services, actions, and CRUD screens through public framework seams.
+---
+
+# CRUD operations
+
+Read this before database, schema, CRUD, repository, or persistence work.
+
+## Establish the product contract
+
+Take database, surface, access, ownership, operations, and fields from product
+intent and current source. Ask when a material choice is missing. Do not
+translate the work into generator options.
+
+Read the narrow package-owned pattern in the [source pattern
+library](/patterns/): `crud/resource-contract` for the resource,
+`crud/json-api-resource-package` for the server, and `crud/crud-screen-set`
+for routed UI. Child-resource and row-policy patterns own those variations.
+
+Normal CRUD tables use one non-null integer primary key. Foreign keys are
+single-column; composite unique indexes are business constraints, not
+identities. Only direct `workspace_id` and `user_id` columns imply ownership.
+Match visibility to real ownership and test allowed plus cross-owner cases.
+
+## Author the resource normally
+
+For a conventional resource:
+
+1. Write an immutable app-owned migration.
+2. Define the shared resource contract through `defineCrudResource()`.
+3. Use `defineCrudJsonApiFeature()` for standard repository, service, action,
+   permission, resource-host, and route mechanics.
+4. Customize through `decorateRepository`, `decorateService`,
+   `operationLifecycle`, and named `actions`; do not copy the standard CRUD
+   repository/action/route stack.
+5. Build routed screens from the matching `http-web`/CRUD UI pattern.
+
+The resource is canonical for fields, operations, validation, transport,
+messages, and route parameters. Do not duplicate its schema or serializers.
+Prefer `useCrudListScreen()`, `useCrudViewScreen()`, and
+`useCrudAddEditScreen()`; use `useCommand()` or `useEndpointResource()` for
+non-standard operations.
+
+Additional resource service methods are normal. Add them with
+`decorateService`; expose commands such as `confirm`, `publish`, or `cancel`
+through named `actions`. With `operationLifecycle`, mutation `before`,
+`execute`, and `after` share one repository transaction, `execute` receives
+`standard(nextInput)`, and `afterCommit` follows commit. Repositories persist;
+services and hooks orchestrate them. Durable external work uses a transactional
+outbox.
+
+## Record deletion
+
+Deletion requires an explicit shared `DELETE` operation and confirmation
+decision. Use `CrudDeleteAction` and `useCrudDeleteAction()` through the view
+actions slot; do not rebuild their confirmation, request, invalidation, and
+navigation flow.
+
+## Strict temporal values
+
+With `json-rest-schema` 1.0.17, temporal resource values are strings:
+
+- `date`: `YYYY-MM-DD`
+- `time`: offset-free `HH:MM[:SS[.fraction]]`
+- `dateTime`: RFC 3339 with seconds and `Z` or a numeric offset
+
+Convert JavaScript `Date` objects at the boundary, normally with
+`toISOString()`. Numeric epochs use `epochMilliseconds` or `epochSeconds`.
+Honor `temporalPrecision`; repositories return strict strings.
+
+## Migration ownership
+
+Migrations are immutable application source owned with their resource. Never
+make a live table or a generator the sole source of truth. Schema inspection
+is for adoption and diagnosis, not compulsory authoring.
+
+Before sign-off, rebuild from zero in a fresh disposable database, compare the
+schema, test ownership boundaries and failure cases, and run current-state
+verification. Do not create a workboard entry, ownership receipt, generation
+record, or historical proof that tooling ran.

package/guide/agent/framework/material-3.md

@@ -0,0 +1,112 @@
+<!-- Generated by `npm run agent-docs:build` from `packages/agent-docs/site/guide/framework/material-3.md`. Do not edit manually. -->
+
+---
+title: Material 3
+description: JSKIT's Vue and Vuetify Material 3 implementation and review contract.
+---
+
+# Material 3
+
+Read completely before any JSKIT Vue/Vuetify UI task.
+
+## Authority
+
+JSKIT uses Vue and the installed Vuetify 4 release. Material 3 is the UI
+contract; packages, shared screens, placements, shell components, and
+app-owned Vuetify configuration are its implementation seams.
+Use the installed public APIs rather than adding `@material/web`, another UI
+framework, or a parallel theme/component system.
+
+The request and Blueprint own brand, content, routes, and behavior. Material 3
+does not authorize a redesign.
+An established JSKIT prop or component wins over generic Material advice.
+
+## Implement through owned seams
+
+Use this order:
+
+1. Reuse the JSKIT package, source pattern, shared screen, shell, placement, or
+   high-level composable that owns the behavior.
+2. Use the matching Vuetify component and its public props, variants, slots,
+   density, responsive, theme, and accessibility behavior.
+3. Adapt app-owned wrappers or the central `createVuetify(...)` configuration.
+4. Add scoped CSS only for product layout or a documented gap. Never style
+   Vuetify internals or duplicate a component system in CSS.
+
+Do not replace a shared screen to restyle it. Use its public seams.
+
+## Theme and visual hierarchy
+
+- Define palettes and theme selection once through the established Vuetify
+  bootstrap. Preserve promised light, dark, or system behavior.
+- Prefer semantic roles such as primary, secondary, surface, surface variant,
+  on-surface, outline, success, warning, and error. Use Vuetify theme props,
+  classes, and `--v-theme-*` variables instead of repeated visual literals.
+- Keep contrast and meaning in every supported theme. Never communicate
+  status, selection, validation, or permission through color alone.
+- Use Vuetify 4 Material 3 display, headline, title, body, and label roles. Do
+  not recreate the old Material 2 type scale or a page-local typography system.
+- Use Vuetify spacing utilities and established JSKIT dimensions before raw
+  values. Preserve JSKIT shell widths, target sizes, and spacing props.
+- Use elevation `0` through `5`, shape props, and component variants instead of
+  arbitrary shadows and radii. Prefer a page header and direct `v-sheet` work
+  region; add cards or dialogs only for genuinely grouped or elevated objects.
+
+## Components, state, and feedback
+
+- Choose components by purpose. Prefer standard buttons, fields, lists,
+  tables, sheets, dialogs, menus, navigation, progress, alerts, snackbars, and
+  tooltips over custom imitations.
+- Give one primary action emphasis. Distinguish destructive, secondary, and
+  icon-only actions without relying on color; give icon controls accessible
+  names and fields meaningful labels, errors, and autocomplete behavior.
+- Preserve visible focus, logical tab order, keyboard operation, and at least
+  48 CSS-pixel interactive targets unless a tested dense operator surface owns
+  another contract.
+- Represent loading, empty, error, retry, disabled, selected, hover, focus,
+  pressed, and success states through shared JSKIT behavior. All user-visible
+  loading uses Material skeletons that reserve the final content geometry;
+  never use a generic spinner or circular progress indicator, and never let
+  content jump when data arrives. An action without a loading content region
+  uses a stable disabled/pending label and shared feedback, not a spinner.
+- Keep failures at their semantic owner. A resource that cannot render uses a
+  stable in-page error and retry state; field validation stays beside the
+  field. A user-triggered command uses JSKIT's shared action
+  feedback/snackbar path. Never insert a transient command-error alert above
+  page content where it shifts the working layout.
+- Use established transitions and honor reduced motion. Do not claim
+  unsupported Material 3 Expressive parity.
+
+## Adaptive layout
+
+Start compact, then verify medium and expanded layouts. Use Vuetify display
+APIs and the JSKIT adaptive shell rather than copying breakpoint numbers.
+Keep primary tasks reachable without incidental chrome. Let navigation,
+tables, filters, supporting content, and action groups change presentation;
+do not merely shrink an expanded screen. Prevent overflow, clipped labels,
+overlapping actions, duplicate navigation, and unreachable dialogs. Persist
+screen context in the route when it must survive navigation.
+
+## Material 3 audit
+
+Run this behavior-preserving audit over every affected screen:
+
+1. Identify the owning JSKIT surface, shared screen, shell, placement, theme,
+   and Vuetify components before judging local markup.
+2. Find parallel components, duplicated state chrome, page-local themes,
+   transient command errors that shift page content, content loaders using
+   generic spinners instead of geometry-preserving skeletons, raw visual
+   constants, CSS against Vuetify internals, nested generic cards, legacy
+   typography, elevation outside `0`-`5`, and desktop-only layout.
+3. Check hierarchy, token use, component purpose, responsive presentation,
+   interaction states, keyboard/focus behavior, labels, targets, contrast, and
+   reduced motion.
+4. Correct issues at the narrowest established owner. Consolidate only truly
+   repeated policy; avoid pass-through wrappers and speculative abstractions.
+5. Run focused tests and Playwright at compact, medium, and expanded widths.
+   Navigate away and back with warm query data when the screen persists state.
+
+Do not declare Material 3 compliance from visual resemblance alone. Report any
+unverified responsive, theme, accessibility, interaction, or browser behavior.
+For a missing or version-sensitive API, verify the installed Vuetify major and
+official docs; implement Material intent through supported JSKIT/Vuetify seams.

package/guide/agent/framework/ui-operations.md

@@ -0,0 +1,78 @@
+<!-- Generated by `npm run agent-docs:build` from `packages/agent-docs/site/guide/framework/ui-operations.md`. Do not edit manually. -->
+
+---
+title: UI operations
+description: Build JSKIT routes, surfaces, placements, responsive UI, and browser verification through framework-owned seams.
+---
+
+# UI operations
+
+Read this for routes, pages, surfaces, placements, responsive UI, and browser
+verification. Also read the complete [Material 3 contract](./material-3).
+
+## Pages, surfaces, and placements
+
+Take the surface and navigation role from the request, product context, and
+current app. They control routes, access, placement visibility, and often
+ownership. Inspect `app/shell-foundation` plus the narrow matching entry in
+the [source pattern library](/patterns/) before authoring source.
+
+Create route files and placement declarations as normal application code.
+Use semantic placement ids and shell public helpers; use concrete outlet ids
+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`.
+
+## Application-owned files
+
+Pattern source is ordinary customizable application source. When replacing a
+starter route, adapt its smoke test to the new canonical route instead of
+discarding browser coverage. Do not retain a generated-file marker, template
+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.
+- Use a page header and 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.
+- 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
+  `users-web` only for actual account/profile/user UI.
+
+## Adaptive shell drawer
+
+Use Vuetify Material navigation. Compact close dismisses the temporary drawer;
+wide layouts default to `desktopDrawerClosedMode="rail"`. Use `hidden` only
+when another navigation affordance remains.
+
+The drawer omits the app bar's surface label. Open and rail icons share a
+centreline. It uses a 12px outer item inset; `navigationItemSpacing` controls
+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.
+
+## Browser verification
+
+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.
+
+Vibe64 owns its managed browser and may provide
+`VIBE64_PLAYWRIGHT_STORAGE_STATE`; never print or commit that value, bypass it,
+or install another browser. For explicitly enabled direct-local auth, use
+`loginAsExistingUser()` from `@jskit-ai/auth-web/test/playwright`; never expose
+the exchange secret to browser code, URLs, or client environment.
+
+Run the narrow test directly:
+
+```bash
+npx playwright test <test-file> -g "<changed behavior>"
+```

package/guide/agent/index.md

@@ -19,6 +19,14 @@ apply or adapt. It does not prescribe an agent host or project orchestrator.
 - [Multi-homing](/guide/app-setup/multi-homing)
 - [Console](/guide/app-setup/console)
 
+## Framework reference
+
+- [Application operations](/guide/framework/application-operations)
+- [CRUD operations](/guide/framework/crud-operations)
+- [UI operations](/guide/framework/ui-operations)
+- [Material 3](/guide/framework/material-3)
+- [Complete source pattern library](/patterns/)
+
 ## Optional capabilities
 
 - [Mobile Capacitor](/guide/app-extras/mobile-capacitor)
@@ -28,9 +36,11 @@ apply or adapt. It does not prescribe an agent host or project orchestrator.
 ## How to use the guide
 
 Begin with the Quickstart and one application-foundation pattern. Add only the
-capabilities selected by the product. For implementation, the installed JSKIT
-skill routes the agent to package-owned `PATTERN.md` files and the smallest
-relevant public API reference.
+capabilities selected by the product. The public pattern library contains every
+published `PATTERN.md` and links its complete example tree. If a runtime package
+is installed, its package-owned copy is the version-matched implementation
+reference. The optional standalone JSKIT Agent Skill bundles the same pattern
+documents and examples, but no agent host is required to install it.
 
 There are no source-generator chapters. Package-owned patterns replace their
 useful source examples; questionnaire, mutation, and provenance machinery is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/agent-docs",
-  "version": "0.1.149",
+  "version": "0.1.150",
   "description": "Distributed JSKIT agent references, prompts, guides, and generated reference maps.",
   "type": "module",
   "files": [

package/patterns/feature-package/example/booking-engine/package.json

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

package/patterns/minimal-foundation/example/AGENTS.md

@@ -1,16 +1,16 @@
 # App Agent Instructions
 
-Use current project context, JSKIT public APIs, and the installed JSKIT pattern
-index as the source of truth for application work.
+Use current project context, JSKIT public APIs, and the official framework
+documentation as the source of truth for application work.
 
-Recommended references:
+Framework references:
 
-- `node_modules/@jskit-ai/agent-docs/guide/agent/index.md`
-- `node_modules/@jskit-ai/agent-docs/patterns/INDEX.md`
+- `https://mobily-enterprises.github.io/jskit-ai/guide/`
+- `https://mobily-enterprises.github.io/jskit-ai/patterns/`
 
-Before database, schema, CRUD, repository, or persistence work, inspect the
-relevant package-owned pattern from
-`node_modules/@jskit-ai/agent-docs/reference/autogen/PATTERN_INDEX.md`.
+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.
 
 Copied pattern source is ordinary application source. Do not add generator
 provenance, receipts, completion ledgers, or tooling-operation history. Keep

package/patterns/minimal-foundation/example/package.json

@@ -34,7 +34,7 @@
   "dependencies": {
     "@local/main": "0.1.0",
     "@fastify/static": "^10.1.3",
-    "@jskit-ai/kernel": "0.1.177",
+    "@jskit-ai/kernel": "0.1.178",
     "@tanstack/vue-query": "^5.101.0",
     "fastify": "^5.8.5",
     "json-rest-schema": "^1.0.17",
@@ -42,12 +42,11 @@
     "vue": "^3.5.38",
     "vue-router": "^5.1.0",
     "vuetify": "^4.1.2",
-    "@jskit-ai/http-runtime": "0.1.175"
+    "@jskit-ai/http-runtime": "0.1.176"
   },
   "devDependencies": {
-    "@jskit-ai/agent-docs": "0.1.149",
-    "@jskit-ai/config-eslint": "0.1.174",
-    "@jskit-ai/jskit-catalog": "0.1.202",
+    "@jskit-ai/config-eslint": "0.1.175",
+    "@jskit-ai/jskit-catalog": "0.1.203",
     "@playwright/test": "1.61.1",
     "@vitejs/plugin-vue": "^6.0.7",
     "eslint": "^10.8.0",

package/patterns/shell-foundation/example/AGENTS.md

@@ -1,16 +1,16 @@
 # App Agent Instructions
 
-Use current project context, JSKIT public APIs, and the installed JSKIT pattern
-index as the source of truth for application work.
+Use current project context, JSKIT public APIs, and the official framework
+documentation as the source of truth for application work.
 
-Recommended references:
+Framework references:
 
-- `node_modules/@jskit-ai/agent-docs/guide/agent/index.md`
-- `node_modules/@jskit-ai/agent-docs/patterns/INDEX.md`
+- `https://mobily-enterprises.github.io/jskit-ai/guide/`
+- `https://mobily-enterprises.github.io/jskit-ai/patterns/`
 
-Before database, schema, CRUD, repository, or persistence work, inspect the
-relevant package-owned pattern from
-`node_modules/@jskit-ai/agent-docs/reference/autogen/PATTERN_INDEX.md`.
+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.
 
 Copied pattern source is ordinary application source. Do not add generator
 provenance, receipts, completion ledgers, or tooling-operation history. Keep

package/patterns/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.177",
+    "@jskit-ai/kernel": "0.1.178",
     "@tanstack/vue-query": "^5.101.0",
     "fastify": "^5.8.5",
     "json-rest-schema": "^1.0.17",
@@ -42,14 +42,13 @@
     "vue": "^3.5.38",
     "vue-router": "^5.1.0",
     "vuetify": "^4.1.2",
-    "@jskit-ai/http-runtime": "0.1.175",
+    "@jskit-ai/http-runtime": "0.1.176",
     "@mdi/js": "^7.4.47",
-    "@jskit-ai/shell-web": "0.1.181"
+    "@jskit-ai/shell-web": "0.1.182"
   },
   "devDependencies": {
-    "@jskit-ai/agent-docs": "0.1.149",
-    "@jskit-ai/config-eslint": "0.1.174",
-    "@jskit-ai/jskit-catalog": "0.1.202",
+    "@jskit-ai/config-eslint": "0.1.175",
+    "@jskit-ai/jskit-catalog": "0.1.203",
     "@playwright/test": "1.61.1",
     "@vitejs/plugin-vue": "^6.0.7",
     "eslint": "^10.8.0",

package/patterns/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.177"
+    "@jskit-ai/kernel": "0.1.178"
   },
   "jskit": {
     "kind": "runtime",