@jskit-ai/agent-docs 0.1.114 → 0.1.115

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

@@ -184,7 +184,7 @@ The most important parts look like this:
     "@tanstack/vue-query": "^5.101.0",
     "@jskit-ai/http-runtime": "0.x",
     "fastify": "^5.8.5",
-    "json-rest-schema": "^1.0.16",
+    "json-rest-schema": "^1.0.17",
     "pinia": "^3.0.4",
     "vue": "^3.5.38",
     "vue-router": "^5.1.0",
@@ -211,6 +211,8 @@ That matters because JSKIT maintenance policy changes over time. If the scaffold
 
 The Playwright scaffold follows the same rule. `playwright.config.mjs` delegates to `@jskit-ai/jskit-cli/test/playwright`, and the starter browser specs delegate their shared responsive checks to published JSKIT helpers. The generated files stay small while later JSKIT package updates can change local server startup, managed `PLAYWRIGHT_BASE_URL` handling, and `VIBE64_PLAYWRIGHT_STORAGE_STATE` support without copying that logic into each new app.
 
+The scaffold also configures `src/typed-router.d.ts` as generated output. It is intentionally absent from a fresh scaffold and ignored by Git; the Vue Router Vite plugin writes it during the first `npm run dev` or `npm run build` route scan.
+
 `jskit app verify` is worth noticing specifically. Linting, tests, and builds check your source code and runtime behavior. The JSKIT part of that flow runs `doctor`, which checks JSKIT-managed app state: installed package visibility, lock-file-backed managed files, and other JSKIT-specific health rules. It is there because a JSKIT app is not only code. It is also a descriptor-driven managed project.
 
 The starter scaffold also writes `.github/workflows/jskit-verify.yml`. JSKIT generates and owns that workflow as a projection of installed package `ci` contracts. The baseline runs checkout, Node 26 setup, `npm ci`, and `npm run verify`. Packages can add job environment values, service containers, and explicit `before-verify` steps without taking ownership of the whole YAML file. For example, the database runtime adds migrations before verification. Its MySQL driver adds a MariaDB service with synthetic CI-only credentials and `DB_CLIENT=mysql2`; its Postgres driver adds the equivalent Postgres service and `DB_CLIENT=pg`.

package/package.json

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

package/patterns/generated-ui-contract-tracking.md

@@ -52,7 +52,7 @@ Generated JSKIT apps should feel like real adaptive apps by default, not framewo
 - Do not remove intentional cards from specialist UI components just to satisfy a broad scan.
 - Keep generated files deterministic and update catalog/agent-doc outputs when descriptors or exported symbols change.
 - Kernel shared UI contract must stay surface-id agnostic. Concrete mappings like admin/console to operator profile belong in generators or package templates.
-- Item 3 is complete for current generated surfaces: page, CRUD, shell, and starter outputs require compact/medium/expanded coverage, horizontal overflow checks, generated screen checks, and 48px tap target checks. Calendar/grid/bottom-sheet specialist generators remain future scope until those generators exist.
+- Item 3 is complete for current generated surfaces: page, CRUD, shell, and starter outputs require compact/medium/expanded coverage, horizontal overflow checks, generated screen checks, and compact generated-screen 48px tap target checks. Calendar/grid/bottom-sheet specialist generators remain future scope until those generators exist.
 - Item 5 is complete for current generators: `primary`, `secondary`, `utility`, `detail`, `workflow`, and `none` are centralized in the generated UI contract, generators consume that contract, and `utility` resolves to seeded `shell.global-actions` topology.
 - Item 6 is complete for the default shell: compact app bars use compact density and bounded top-left/top-right regions, while primary navigation remains in semantic bottom navigation instead of app-bar chrome.
 - CRUD filters are client-side by default: generated list pages create a page-local `listFilters.js` and pass it into `useCrudListScreen(...)`; the shared list screen wires `filterRuntime.queryParams` into the list request and renders `CrudListFilterSurface`. When server filtering is needed, promote the definitions into a shared package module and use `createCrudListFilterContract(...)` so route/action validators, JSON REST search schema, and repository query normalization stay derived from the same definition.

package/patterns/ui-testing.md

@@ -11,7 +11,7 @@ Rules:
 
 - Any chunk that adds or changes user-facing UI must include a Playwright flow that exercises the changed behavior before the chunk is done.
 - Generator or package template UI changes must be checked at compact phone, tablet-ish medium, and expanded desktop widths.
-- For generated UI, check horizontal overflow, clipped or invisible text, duplicate navigation, broken route placement, and tap targets under 48 px.
+- For generated UI, check horizontal overflow, clipped or invisible text, duplicate navigation, and broken route placement at every standard viewport. On compact screens, also check generated-screen tap targets under 48 px; medium and expanded layouts may use their documented denser controls.
 - Apps with `shell-web` installed should start from `tests/e2e/adaptive-shell.spec.ts` and extend it with feature-specific assertions.
 - Generated `playwright.config.mjs` delegates to `@jskit-ai/jskit-cli/test/playwright`. Do not copy base-URL, web-server, or storage-state logic into app tests.
 - Use relative paths such as `page.goto("/home")`. The shared config owns the browser base URL.

package/reference/autogen/packages/json-rest-api-core.md

@@ -41,9 +41,10 @@ Local functions
 - `cloneJsonRestResourceValue(value, { writeSerializers = {} } = {})`
 - `resolveCanonicalCalendarDate(value)`
 - `serializeJsonRestCalendarDate(value)`
+- `resolveCanonicalDateTime(value)`
 - `applyJsonRestCalendarDateWriteSerializers(scopeOptions = {})`
-- `normalizeJsonRestCalendarDateEntry(entry = null, scopes = {})`
-- `normalizeJsonRestCalendarDateDocument(document = null, scopes = {})`
+- `normalizeJsonRestTemporalEntry(entry = null, scopes = {})`
+- `normalizeJsonRestTemporalDocument(document = null, scopes = {})`
 - `normalizeScopeValue(value)`
 - `normalizeJsonRestText(value, { fallback = "" } = {})`
 - `normalizeJsonRestFilterValue(value)`

package/reference/autogen/packages/users-core.md

@@ -124,15 +124,12 @@ Exports
 
 ### `src/server/common/repositories/repositoryUtils.js`
 Exports
-- `toNullableDateTime`
 - `toIsoString`
 - `isDuplicateEntryError`
 - `normalizeText`
 - `normalizeLowerText`
 - `normalizeRecordId`
 - `normalizeDbRecordId`
-- `nowDb()`
-- `toNullableIso(value)`
 - `uniqueSorted(values)`
 - `parseJson(value, fallback = {})`
 - `toDbJson(value, fallback = {})`

package/reference/autogen/packages/workspaces-core.md

@@ -38,15 +38,12 @@ Exports
 
 ### `src/server/common/repositories/repositoryUtils.js`
 Exports
-- `toNullableDateTime`
 - `toIsoString`
 - `isDuplicateEntryError`
 - `normalizeText`
 - `normalizeLowerText`
 - `normalizeRecordId`
 - `normalizeDbRecordId`
-- `nowDb()`
-- `toNullableIso(value)`
 - `uniqueSorted(values)`
 - `parseJson(value, fallback = {})`
 - `toDbJson(value, fallback = {})`