@jskit-ai/agent-docs 0.1.118 → 0.1.120

package/guide/agent/generators/advanced-cruds.md

@@ -249,7 +249,6 @@ migrations/
 
 packages/contacts/
   package.json
-  package.descriptor.mjs
   src/server/ContactsProvider.js
   src/server/actions.js
   src/server/registerRoutes.js
@@ -281,7 +280,7 @@ Two important notes:
 
 ## What each server file owns
 
-### `package.json` and `package.descriptor.mjs`
+### `package.json`
 
 These make the CRUD a real local package.
 
@@ -290,7 +289,7 @@ They own:
 - package identity
 - runtime dependencies
 - provider registration metadata
-- descriptor-driven install/runtime metadata
+- `package.json.jskit` install and runtime metadata
 
 They do **not** own CRUD behavior directly. They describe how the package plugs into the app.
 

package/guide/agent/generators/crud-generators.md

@@ -46,7 +46,6 @@ npx @jskit-ai/create-app notes \
 npm install
 
 npx --no-install jskit add package database-runtime-mysql
-npm install
 
 # Create and select a fresh disposable database, then create the live `notes` table.
 
@@ -56,7 +55,6 @@ npx --no-install jskit generate crud-server-generator scaffold \
   --ownership-filter public \
   --access public \
   --table-name notes
-npm install
 
 npx --no-install jskit generate crud-ui-generator crud notes \
   --resource-file packages/notes/src/shared/noteResource.js \
@@ -73,26 +71,29 @@ placement, so do not pre-install the shell as a workaround.
 
 ## Existing-app migration checklist
 
-JSKIT is still version 0, so this release uses a direct code migration rather
-than a legacy compatibility layer:
+Strict temporal resource values require one coordinated application migration.
+There is no compatibility alias or automatic coercion for JavaScript `Date`
+objects at resource boundaries:
 
-1. Commit the app's current work, then run `npm run jskit:update`.
-2. If the app declares `json-rest-schema` directly, install
-   `json-rest-schema@^1.0.17`.
+1. Commit the application's current work and update its direct `@jskit-ai/*`
+   dependencies to one coordinated, exact release set.
+2. If the application declares `json-rest-schema` directly, use
+   `json-rest-schema` 1.0.17 or newer and review its temporal validation before
+   installing dependencies.
 3. Replace resource-bound JavaScript `Date` values with strings. `date` is
    `YYYY-MM-DD`; `time` is offset-free `HH:MM[:SS[.fraction]]`; and `dateTime`
-   is RFC 3339 with seconds and a `Z` or numeric offset. Replace the removed
-   `timestamp` type with `epochMilliseconds` or `epochSeconds` only after
-   checking the existing numeric unit. Preserve `temporalPrecision`.
+   is RFC 3339 with seconds and a `Z` or numeric offset. Use
+   `epochMilliseconds` or `epochSeconds` only after checking the existing
+   numeric unit. Preserve `temporalPrecision`.
 4. For a standard generated view delete action, rerun the original
    `crud-ui-generator crud` command with `--delete-confirmation`. Add `--force`
-   only when you deliberately want to replace unchanged generated page output.
-   For a customized view, preserve the customization and add the public
-   `CrudViewScreen` `actions` slot plus `useCrudDeleteAction()` integration
-   described below.
-5. Keep every managed path recorded in `.jskit/lock.json`. Adapt managed shell
-   and browser tests in place; never delete them because a starter route was
-   replaced.
+   only when you deliberately want to replace generated page output. For a
+   customized view, preserve the customization and add the public
+   `CrudViewScreen` `actions` slot, `CrudDeleteAction`, and
+   `useCrudDeleteAction()` integration described below.
+5. Review the generated diff, keep application-owned customizations and browser
+   tests, then run the application's full verification suite before applying
+   database migrations.
 
 Generated generic CRUD repositories convert database temporal values at the
 resource boundary. Custom repositories still need to return strict temporal
@@ -359,7 +360,7 @@ installed. Later schema evolution must use a new immutable, package-owned
 additive migration in the table's app-local package, declared through
 `install-migration`.
 
-Create that source and descriptor mutation together with:
+Create that source and `package.json.jskit` mutation together with:
 
 ```bash
 npx jskit create migration \
@@ -368,7 +369,7 @@ npx jskit create migration \
 ```
 
 Implement the generated template before running
-`npx jskit migrations package @local/contacts`. SQL or Knex schema operations
+`npx jskit migrations sync`. SQL or Knex schema operations
 inside the source-controlled migration are supported. Running ad-hoc SQL
 against only one database is not, because it creates schema drift.
 
@@ -473,22 +474,6 @@ That file is the shared CRUD contract. The UI generator reads it to decide:
 
 So even though the server scaffold writes many files, the resource file is the bridge between the server and UI halves.
 
-### One install boundary to remember
-
-`crud-server-generator scaffold` also adds a new local app package dependency such as:
-
-```text
-@local/contacts
-```
-
-So before you build or run the app again, install that new local package:
-
-```bash
-npm install
-```
-
-The same rule applies after later server scaffolds such as `addresses` and `comments`. The UI generator can still read the generated resource file directly, but the app runtime needs the local package install boundary to be completed before the CRUD can boot normally.
-
 For standard CRUDs, that file is intentionally compact. It uses `defineCrudResource(...)` from `@jskit-ai/resource-crud-core`, authors the canonical `schema` / `searchSchema` / `defaultSort` / `autofilter` shape once, and lets JSKIT derive the standard CRUD operation contracts from it.
 
 The generated server action validators are compact for the same reason.
@@ -534,13 +519,13 @@ Vue files below `src/pages/`, so reusable Vue helpers must stay outside that
 directory or they become browser routes.
 
 `--delete-confirmation` is opt-in. When present, the generated view extends
-the public `CrudViewScreen` `actions` slot with a destructive Delete button and
-a Vuetify alert dialog. The public `useCrudDeleteAction()` composable resolves
-the current route id through the CRUD runtime, runs the shared resource's
-`DELETE` operation through `useCommand()`, disables duplicate submission,
-keeps a useful error on the record screen, invalidates the list query, and
-navigates to the generated list route after success. It supports custom
-`--id-param` names.
+the public `CrudViewScreen` `actions` slot with `CrudDeleteAction`. That shared
+component owns the destructive button and Vuetify alert dialog. The public
+`useCrudDeleteAction()` composable resolves the current route id through the
+CRUD runtime, runs the shared resource's `DELETE` operation through
+`useCommand()`, disables duplicate submission, keeps a useful error on the
+record screen, invalidates the list query, and navigates to the generated list
+route after success. It supports custom `--id-param` names.
 
 The generator rejects this option when list or view is omitted, or when the
 shared resource has no `DELETE` operation. Without the flag, no delete control
@@ -658,12 +643,6 @@ npx jskit generate crud-server-generator scaffold \
   --grant-role member
 ```
 
-Then install the generated local package:
-
-```bash
-npm install
-```
-
 ### Step 3: refine the generated lookup metadata by hand
 
 Open `packages/addresses/src/shared/addressResource.js` and add `labelKey: "fullName"` to the generated `contactId` relation:
@@ -836,12 +815,6 @@ npx jskit generate crud-server-generator scaffold \
   --grant-role member
 ```
 
-Then install the generated local package:
-
-```bash
-npm install
-```
-
 ### Step 3: refine the generated lookup metadata by hand
 
 Open `packages/comments/src/shared/commentResource.js` and add `labelKey: "fullName"` to the generated `contactId` relation:

package/guide/agent/generators/row-policies.md

@@ -360,7 +360,7 @@ class SafetyProvider {
 
 The organisation-units package never imports safety. Installing safety adds the grant; omitting safety leaves that grant absent.
 
-The package descriptor dependency must point in the same direction as the provider dependency: safety declares organisation-units, and organisation-units does not declare safety.
+The npm dependency must point in the same direction as the provider dependency: safety depends on organisation-units, and organisation-units does not depend on safety.
 
 ## Descendant visibility with a recursive CTE
 

package/package.json

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

package/patterns/INDEX.md

@@ -28,7 +28,7 @@ How to use it:
   - `live-actions.md`
 - ajax, fetch, API call, request, endpoint, HTTP client, `useCrudListScreen()`, `useCrudViewScreen()`, `useCrudAddEditScreen()`, `useList()`, `useView()`, `useAddEdit()`, `useEndpointResource()`, `usersWebHttpClient`
   - `client-requests.md`
-- playwright, browser test, e2e, ui verification, managed test, `.jskit/lock.json`, authenticated ui test, test auth, dev login as, dev auth bypass
+- playwright, browser test, e2e, ui verification, baseline test, authenticated ui test, test auth, dev login as, dev auth bypass
   - `ui-testing.md`
 - generated UI contract, design contract, navigation roles, density, placeholder copy, card shells, shared CRUD screens, row actions, synthetic rows, detail slots
   - `generated-ui-contract-tracking.md`

package/patterns/crud-scaffolding.md

@@ -97,8 +97,9 @@ Rules:
 - Use `--navigation-role` for CRUD list placement intent. Main resources can stay `primary`; nested/detail/workflow CRUD routes should usually be `secondary`, `workflow`, or `none`.
 - Add `--delete-confirmation` when the generated view needs the standard
   destructive record action. The flag requires list and view pages and a
-  resource with a `DELETE` operation; it uses the public view-screen action
-  slot and command composable rather than generated raw request code.
+  resource with a `DELETE` operation; it uses `CrudDeleteAction` in the public
+  view-screen action slot and the standard command composable rather than
+  generating page-local dialog or request code.
 
 ## Temporal values at resource boundaries
 
@@ -109,15 +110,13 @@ validators no longer coerce JavaScript `Date` objects:
 - `time` is offset-free `HH:MM[:SS[.fraction]]`
 - `dateTime` is RFC 3339 with seconds and `Z` or a numeric offset
 
-The removed `timestamp` type must become `epochMilliseconds` or
-`epochSeconds` after checking the stored unit. Preserve the field's
+Use `epochMilliseconds` or `epochSeconds` for numeric epoch values after
+checking the stored unit. Preserve the field's
 `temporalPrecision`; do not truncate meaningful fractional seconds.
 
 Generated generic CRUD repositories serialize database temporal outputs
 before resource validation. App-owned/custom repositories must return strict
 strings and must write ISO/RFC 3339 strings rather than passing `Date` objects.
-This is a version-0 breaking contract: update application code instead of
-adding a legacy temporal parser.
 
 ## Baseline generation versus later schema evolution
 
@@ -136,10 +135,10 @@ The initial CRUD scaffold and a later schema change are different operations:
   ```
 
 - The authoring command creates an editable migration template and adds its
-  `install-migration` mutation to the owning package descriptor in one
-  operation. Implement and test the template before materializing it.
-- Materialize the completed source with
-  `npx jskit migrations package <package-id>`, then apply it with
+  `install-migration` mutation to the owning package's `package.json.jskit` in
+  one operation. Implement and test the template before synchronizing it.
+- Synchronize the completed source with
+  `npx jskit migrations sync`, then apply it with
   `npm run db:migrate`.
 - SQL or Knex schema operations inside that source-controlled migration are
   supported. Ad-hoc SQL applied only to one database is not: it creates schema

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

@@ -4,7 +4,7 @@ Use this file to track the generator-level UI contract work. Keep entries concre
 
 ## Goal
 
-Generated JSKIT apps should feel like real adaptive apps by default, not framework demos. The contract must be enforced in generators, descriptors, docs, and tests so it does not drift.
+Generated JSKIT apps should feel like real adaptive apps by default, not framework demos. The contract must be enforced in generators, package metadata, docs, and tests so it does not drift.
 
 ## Current Scope
 
@@ -31,7 +31,7 @@ Generated JSKIT apps should feel like real adaptive apps by default, not framewo
 
 - [x] `npm run lint`
 - [x] `npm run check:runtime-deps`
-- [x] `npm run jskit -- lint-descriptors`
+- [x] `npx jskit lint-packages`
 - [x] `npm run catalog:build`
 - [x] `npm run agent-docs:build`
 - [x] `npm test --workspace @jskit-ai/kernel`
@@ -50,7 +50,7 @@ Generated JSKIT apps should feel like real adaptive apps by default, not framewo
 - Do not weaken semantic placement defaults while adding navigation inference.
 - Do not turn the contract into runtime business logic; it is generator and template policy.
 - 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.
+- Keep generated files deterministic and update catalog/agent-doc outputs when package metadata 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 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.

package/patterns/live-actions.md

@@ -27,10 +27,11 @@ Rules:
 
   `--delete-confirmation` requires generated list and view pages plus a shared
   resource with a `DELETE` operation. It extends the view through the public
-  `CrudViewScreen` `actions` slot and `useCrudDeleteAction()`: Vuetify owns the
-  alert dialog, `useCommand()` owns the request state, the shared resource owns
-  the DELETE contract, and successful deletion invalidates the list query and
-  navigates to the generated list route.
+  `CrudViewScreen` `actions` slot with `CrudDeleteAction` and wires it to
+  `useCrudDeleteAction()`: the shared component owns the alert dialog,
+  `useCommand()` owns the request state, the shared resource owns the DELETE
+  contract, and successful deletion invalidates the list query and navigates
+  to the generated list route.
 
 Good live-action pattern:
 

package/patterns/placements.md

@@ -58,8 +58,8 @@ Runtime behavior:
 - Runtime resolves the component token as `entry.componentToken || variant.renderers[entry.kind]`.
 - Entries without a resolvable component token do not render.
 - `when()` receives placement context including `app`, `surface`, `target`, `layoutClass`, runtime context, local outlet context, and context contributors.
-- The standard `ShellLayout` uses one `navigationItemSpacing` value (12px by default) for the icon-to-label gap and the widest label's logical-end gap. It remeasures its content-aware width after placement, locale, font, surface, spacing, and layout changes. Use `drawerWidth` only when a product needs a fixed width; do not add consumer `.v-navigation-drawer` overrides.
-- On medium and expanded layouts, closing the standard drawer produces an 80px Material navigation rail by default. Use `railWidth` to configure that width, or `desktopDrawerClosedMode="hidden"` only when another discoverable navigation surface exists.
+- The standard `ShellLayout` uses Material's 12px outer item inset and one `navigationItemSpacing` value (12px by default) for the icon-to-label gap and widest label's logical-end gap. It remeasures its content-aware width after placement, locale, font, surface, spacing, and layout changes. The surface label belongs once in the top app bar; do not add or restore a duplicate drawer subheader. Use `drawerWidth` only when a product needs a fixed width; do not add consumer `.v-navigation-drawer` overrides.
+- On medium and expanded layouts, closing the standard drawer produces an 80px Material navigation rail by default. Expanded and collapsed icons share one centreline. Use `railWidth` to configure an intentionally denser rail, or `desktopDrawerClosedMode="hidden"` only when another discoverable navigation surface exists.
 - The shell link renderers own rail centring, selected-state treatment, and opaque theme-aware tooltips. Applications should keep supplying the same semantic placement records rather than creating rail-only links or tooltip CSS.
 
 CLI and generators:

package/patterns/ui-testing.md

@@ -20,11 +20,11 @@ Rules:
 - Vibe64 supplies an authenticated context through `VIBE64_PLAYWRIGHT_STORAGE_STATE`. Treat that file as a temporary secret: do not commit it, print it, or retain it after the run.
 - Do not install a browser when the environment provides a managed browser runner.
 
-## Preserve managed baseline tests
+## Preserve baseline tests
 
-“App-owned” means customizable, not disposable while the package remains
-installed. Never delete or rename a test path recorded in `.jskit/lock.json`.
-Generated and managed infrastructure tests must be adapted in place.
+Generated baseline tests are app-owned and customizable. Adapt infrastructure
+tests in place when routes or behavior change so the baseline coverage remains
+truthful.
 
 When the starter product route is replaced, update the scaffold smoke test to
 visit and assert the new canonical route. Do not delete baseline browser
@@ -82,22 +82,15 @@ The generated config applies that state to Playwright contexts and omits its loc
 
 Do not call `loginAsExistingUser()` against a managed preview. It is deliberately localhost-only. An ordinary request to `/api/dev-auth/login-as` without the private exchange header must return `403`.
 
-## Recording verification
+## Run verification
 
-After the Playwright command succeeds, record it with:
+Run the focused Playwright command directly:
 
 ```bash
-npx jskit app verify-ui \
-  --command "npx playwright test tests/e2e/contacts.spec.ts -g filters" \
-  --feature "contacts filters" \
-  --auth-mode dev-auth-login-as
+npx playwright test tests/e2e/contacts.spec.ts -g filters
 ```
 
-Use `--auth-mode session-bootstrap` when a managed runner supplied authenticated storage state.
-
-`jskit app verify-ui` runs the command and records its command, auth-mode label, feature, and changed UI files in `.jskit/verification/ui.json`. The auth-mode option describes how the command was authenticated; it does not create a session or modify the Playwright context.
-
-For local pre-merge review, follow the recorded run with:
+For local pre-merge review, follow the focused run with:
 
 ```bash
 npx jskit doctor --against origin/main

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

@@ -303,9 +303,3 @@ Exports
 ### `src/shared/support/positiveInteger.js`
 Exports
 - `toPositiveInteger(value, fallback = 0)`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/assistant-runtime.md

@@ -234,9 +234,3 @@ Exports
 ### `templates/migrations/assistant_transcripts_initial.cjs`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/assistant.md

@@ -66,9 +66,3 @@ Exports
 ### `templates/src/pages/settings/assistant/index.vue`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

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

@@ -494,9 +494,3 @@ Exports
 - `runAuthSignOutFlow({ authApi, clearCsrfTokenCache = null, afterSignOut = null } = {})`
 Local functions
 - `normalizeAuthApi(authApi)`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/auth-provider-local-core.md

@@ -131,9 +131,3 @@ Local functions
 ### `src/server/providers/AuthProviderServiceProvider.js`
 Exports
 - `AuthProviderServiceProvider`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/auth-provider-local-db-core.md

@@ -48,9 +48,3 @@ Exports
 ### `templates/migrations/auth_local_db_initial.cjs`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/auth-provider-supabase-core.md

@@ -227,9 +227,3 @@ Local functions
 - `assertSelectedAuthProvider(env)`
 - `resolveOptionalRepositories(scope)`
 - `isDeferredJsonRestBootGap(app, error)`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/auth-web.md

@@ -312,9 +312,3 @@ Exports
 ### `templates/src/views/auth/SignOutView.vue`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

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

@@ -87,9 +87,3 @@ Exports
 ### `templates/migrations/console_core_generic_initial.cjs`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/console-web.md

@@ -29,9 +29,3 @@ Exports
 ### `templates/src/pages/console/settings/index.vue`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

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

@@ -371,9 +371,3 @@ Exports
 ### `src/shared/crudResource.js`
 Exports
 - `defineCrudResource`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/crud-server-generator.md

@@ -170,10 +170,6 @@ Exports
 Exports
 - None
 
-### `templates/src/local-package/package.descriptor.mjs`
-Exports
-- None
-
 ### `templates/src/local-package/server/actions.js`
 Exports
 - `createActions({ surface } = {})`
@@ -206,12 +202,6 @@ Exports
 Exports
 - `resource`
 
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None
-
 ### test-support
 
 ### `test-support/templateServerFixture.js`

package/reference/autogen/packages/crud-ui-generator.md

@@ -61,8 +61,7 @@ Local functions
 - `resolveCrudRelativePath(namespace = "")`
 - `buildListParentTitleImportLine(parentTitleMode = "contextual")`
 - `buildListHeadingTitleSetup({ parentTitleMode = "contextual", resourceNamespace = "", routeTitle = "Records" } = {})`
-- `buildViewDeleteActionSlot({ resourceNamespace = "resource", resourceSingularTitle = "Record" } = {})`
-- `buildViewDeleteDialog({ resourceNamespace = "resource", resourceSingularTitle = "Record" } = {})`
+- `buildViewDeleteActionSlot({ resourceSingularTitle = "Record" } = {})`
 - `buildViewDeleteSetup({ resourceNamespace = "resource" } = {})`
 
 ### `src/server/resourceSupport.js`
@@ -191,9 +190,3 @@ Exports
 ### `templates/src/pages/admin/ui-generator/ViewElement.vue`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/database-runtime-mysql.md

@@ -57,9 +57,3 @@ Local functions
 - `requireIdColumn(columns, idColumn)`
 - `requirePrimaryKeyContainsId(primaryKeyColumns, idColumn)`
 - `requireSupportedForeignKeys(foreignKeys, primaryKeyColumnsByTable)`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/database-runtime-postgres.md

@@ -31,9 +31,3 @@ Exports
 Exports
 - `DIALECT_ID`
 - `getDialectId`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/database-runtime.md

@@ -220,9 +220,3 @@ Exports
 ### `templates/knexfile.js`
 Exports
 - `default`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/feature-server-generator.md

@@ -30,14 +30,10 @@ Local functions
 - `buildActionsContext({ surface })`
 - `buildServiceContext({ featureName, mode })`
 - `buildRouteContext({ surface })`
-- `buildDescriptorContext({ featureName, mode })`
+- `buildManifestContext({ featureName, mode })`
 
 ### templates
 
-### `templates/src/local-package/package.descriptor.mjs`
-Exports
-- None
-
 ### `templates/src/local-package/server/actions.js`
 Exports
 - `featureActions`
@@ -66,9 +62,3 @@ Exports
 ### `templates/src/local-package/server/service.js`
 Exports
 - `createService({ featureRepository } = {})`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/google-rewarded-core.md

@@ -214,9 +214,3 @@ Exports
 ### `templates/migrations/google_rewarded_watch_sessions_initial.cjs`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/google-rewarded-web.md

@@ -63,9 +63,3 @@ Exports
 ### `src/shared/index.js`
 Exports
 - None
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

package/reference/autogen/packages/http-runtime.md

@@ -371,9 +371,3 @@ Exports
 Exports
 - `rewriteEmbeddedTransportSchemaRefs(value, { rootRef = "#", definitionRefByName = {} } = {})`
 - `createEmbeddableTransportSchemaDocument(schemaDocument = {}, rootDefinitionName = "TransportSchema")`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None

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

@@ -58,9 +58,3 @@ Local functions
 - `applyJsonRestDefaultExclusions(scopeOptions = {}, resource = {})`
 - `extractJsonApiInputRelationships(attributes = {}, resource = null, relationships = null)`
 - `isJsonRestSparseFieldError(error = null)`
-
-### root
-
-### `package.descriptor.mjs`
-Exports
-- None