@aceshooting/lyra-ui 18.3.0 → 19.0.0

package/llms/components/lr-agent-workspace.md

@@ -83,10 +83,10 @@ Citation; truncated?: boolean; omittedTokens?: number; redactions?: ContextInspe
 - `composerStatus: ChatComposerStatus = 'idle'` (attribute `composer-status`) — `'idle' | 'sending' |
 'streaming'`, `lr-chat-composer`'s own union; invalid values read as `idle` without rewriting the
   host attribute
-- `composerPlaceholder: string = ''` (attribute `composer-placeholder`)
+- `composerPlaceholder?: string` (attribute `composer-placeholder`)
 - `composerMinRows: number = 1` (attribute `composer-min-rows`), `composerMaxRows: number = 8`
   (attribute `composer-max-rows`)
-- `label: string = ''` — accessible name and visible heading
+- `label?: string` — accessible name and visible heading; omission uses the localized default and an explicit empty string suppresses it
 - `accessibleLabel: string | null = null` (attribute `aria-label`) — host-level accessible-name
   override for the internal `role="region"` root
 

package/llms/components/lr-chart.md

@@ -100,10 +100,11 @@ structured points retain their y-value formatting.
     draws side by side with the first on that axis. Omitted series share one implicit group, so
     every chart written before `stack` existed sums exactly as it always did. Only meaningful on an
     axis that is actually stacked — see `stacked`/`stackedAxes` below.
-  `LyraChartPoint { readonly x: number; readonly
-  y: number; readonly r?: number; readonly label?: string }`: `r` is the bubble
-  radius, and the optional per-point `label` is retained by events, CSV export, keyboard
-  announcements, generated summaries, and the accessible table. Point wording is localized as
+  `LyraChartPoint { readonly x: number; readonly y: number; readonly r?: number; readonly id?:
+  string | number; readonly label?: string }`: `r` is the bubble radius, and the optional primitive
+  `id` is retained by activation events for application navigation or selection. Objects, symbols,
+  and non-finite numeric ids are omitted. The optional per-point `label` is retained by events, CSV
+  export, keyboard announcements, generated summaries, and the accessible table. Point wording is localized as
   whole messages: `chartPointCoordinates`, `chartBubblePointCoordinates`, and
   `chartLabeledPoint` own coordinate names, order, separators, and the label wrapper. A caller's
   point label is interpolated verbatim rather than translated or parsed. At runtime, non-record
@@ -381,9 +382,15 @@ const series = [
 point/segment, when a generated-table value is activated, or when Enter/Space activates the
 keyboard-current canvas datum; `detail: { datasetIndex: number, index: number, label: string |
 undefined, value: unknown }`). For scatter/bubble points, `label` prefers the per-point label and
-`value` is the complete `LyraChartPoint`, including optional `r` and `label`.
+`value` is the complete `LyraChartPoint`, including optional `r`, `id`, and `label`. A primitive
+`id` survives the same pointer, data-table, and keyboard activation paths; invalid ids are omitted.
 `lr-datum-activate` emits the same activation with `kind: 'bar'|'point'|'segment'|'slice'` for
-family-wide handling; `lr-point-click` remains as a compatibility event. Also
+family-wide handling. For scatter/bubble, both events carry the same `LyraChartPoint` value,
+including a string or finite-number `id` when supplied; invalid ids are omitted. The public
+`LyraChartPoint.id` type is `string | number`, while the activation event's heterogeneous `value`
+is typed `unknown`. Validate or explicitly narrow the value itself before reading point fields;
+checking `detail.kind === 'point'` alone does not narrow `detail.value` in TypeScript.
+`lr-point-click` remains as a compatibility event. Also
 `lr-before-legend-visibility-change` (cancelable proposal), and
 `lr-legend-visibility-change` (accepted commit). Both legend events carry
 `{ datasetIndex: number, visible: boolean, hiddenDatasets: readonly number[] }`; the latter is the

package/llms/components/lr-copy-button.md

@@ -35,12 +35,12 @@ buttons.
   Resolution prefers an element in the button's own root, then falls back to the owner document;
   a duplicate same-root id therefore wins without preventing a shadow-contained button from
   targeting an otherwise valid document-owned source.
-- `copyLabel: string = ''` (attribute `copy-label`) — built-in button accessible name and resting
-  tooltip text; empty uses localized `copy`.
-- `successLabel: string = ''` (attribute `success-label`) — confirmation name/tooltip text; empty
-  uses localized `copied`.
-- `errorLabel: string = ''` (attribute `error-label`) — failure name/tooltip text; empty uses
-  localized `copyFailed`.
+- `copyLabel?: string` (attribute `copy-label`) — built-in button accessible name and resting
+  tooltip text; omission uses localized `copy`, while an explicit empty string suppresses it.
+- `successLabel?: string` (attribute `success-label`) — confirmation name/tooltip text; omission
+  uses localized `copied`, while an explicit empty string suppresses it.
+- `errorLabel?: string` (attribute `error-label`) — failure name/tooltip text; omission uses
+  localized `copyFailed`, while an explicit empty string suppresses it.
 - `tooltip: 'full' | 'copy' | 'none' = 'full'` (reflected) — `full` shows the resting tooltip on
   hover/focus and feedback after activation, `copy` shows feedback only, and `none` disables it.
 - `tooltipPlacement: 'top' | 'right' | 'bottom' | 'left' = 'top'` (attribute

package/llms/components/lr-dialog.md

@@ -178,10 +178,12 @@ painted surface sits one boundary deeper. `<lr-drawer>` inherits this control an
 `<lr-icon-button>` itself.
 
 **The body is keyboard-reachable while it overflows.** `[part="body"]` is the element that scrolls,
-so it carries `tabindex="-1"` and joins the focus order **only while its content actually
-overflows** — a dialog whose content is nothing but prose, a table, or a rendered document used to
+so it carries `tabindex="0"` **only while its content actually overflows** — a dialog whose
+content is nothing but prose, a table, or a rendered document used to
 be scrollable with a mouse and completely unreachable from the keyboard, because a scroll container
-with no focusable child is not a stop of its own. A short body never becomes a gratuitous stop.
+with no focusable child is not a stop of its own. A short body keeps `tabindex="-1"` and never
+becomes a gratuitous stop. Resize and content changes update the body's tabindex as its overflow
+changes; `<lr-drawer>` uses the same behavior.
 
 It takes focus like any other stop, so it styles like one: `::part(body):focus-visible` draws the
 standard `--lr-focus-ring-*` ring, inset (`outline-offset` is negative) because the body is flush

package/llms/components/lr-export-button.md

@@ -9,7 +9,7 @@
 - **Release history** [CHANGELOG.md](../../CHANGELOG.md); family-wide breaking-change summaries: [llms-full.txt](../../llms-full.txt)
 - **Deprecations** none
 - **Optional peers** none
-- **Themeable via** 6 parts, 5 custom properties — see this component's own `@csspart`/`@cssprop` list below
+- **Themeable via** 6 parts, 14 custom properties — see this component's own `@csspart`/`@cssprop` list below
 - **Library-wide behavior** (events, form association, `locale`/`strings`, tokens, TS types): `llms/shared.md`
 
 ---
@@ -98,8 +98,16 @@ closes caused by disablement, loading, or an unusable format list emit neither e
 attempt regardless of outcome — style with `::part(trigger-error)`), `menu`, `menu-item`,
 `format-label`, `format-description`
 
-**Themeable custom properties:** shared tokens only, including `--lr-popover-viewport-clamp`
-(default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed
+**Themeable custom properties:** the trigger's paint is settable per state. At rest,
+`--lr-export-button-background`, `--lr-export-button-color` and `--lr-export-button-border`; on
+hover, `--lr-export-button-hover-background`, `--lr-export-button-hover-color` and
+`--lr-export-button-hover-border`; while pressed, `--lr-export-button-active-background`,
+`--lr-export-button-active-color` and `--lr-export-button-active-border`. Each layers over whatever
+the current `appearance` resolves to and leaves the other paints alone, so they are also the way to
+keep `appearance="outlined"` chrome while returning its label to neutral text — `outlined` paints
+the label `--lr-color-brand` and, unlike `lr-button`, this component has no `variant` of its own to
+opt out. Before 18.4.0 none of these existed and the only lever was `::part(trigger)`. Plus shared
+tokens, including `--lr-popover-viewport-clamp` (default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed
 against, alongside its own `20rem` cap and the positioner's available space. See `lr-tour` for the
 shared-clamp note.
 

package/llms/components/lr-file-input.md

@@ -87,8 +87,9 @@ enabled buttons retain pointer feedback.
   constrained spaces (a toolbar, a table cell) — the same convention as `lr-empty`'s `compact`. The
   dashed border stays; only the internal spacing shrinks. `false` (the default) keeps the full
   `--lr-space-l` dropzone.
-- `label: string = ''` and `hint: string = ''`; an empty `label` leaves the localized dropzone
-  instruction (`fileInputDefaultLabel`) as the visible fallback
+- `label?: string` — form-control label. Omission uses the localized dropzone instruction
+  (`fileInputDefaultLabel`); an explicit empty string suppresses that fallback. `hint: string = ''`
+  remains empty when omitted and can be supplied through the named slot as well
 - `errorText: string = ''` (attribute `error-text`) — plain-text owned validation feedback. When
   it is empty, a `customError` message is rendered when present; otherwise an intrinsic validation
   message appears after the control has been interacted with. Rich `error` slot content replaces

package/llms/components/lr-mcp-app.md

@@ -47,6 +47,11 @@ typed events. Capabilities are denied unless explicitly enabled in `resource.per
 request with exactly one of `{ frameGeneration, result }` or `{ frameGeneration, error }`. Missing,
 stale, or ambiguous correlation fails closed. Both methods are no-ops before a frame exists.
 
+The initial `host-context` message includes a document-bound nonce and transfers a `MessagePort` to
+the executable document. Frame requests and host messages after bootstrap use that port. A same-frame
+navigation closes the port, invalidates the nonce and generation, and mounts a fresh sandbox before
+host data can be delivered.
+
 **Exported types:** `McpAppResource`, `McpAppCsp`, `McpAppPermissions`,
 `McpAppToolCallDetail`, `McpAppToolResultOptions`, and `LyraMcpAppEventMap`.
 

package/llms/components/lr-retrieval-search.md

@@ -60,8 +60,8 @@ at the same size tier, so the toolbar row renders as one flush line.
   Remove any host `role="status"`/`role="alert"` hand-added before this property existed once it
   is set — otherwise the initial state is announced twice, through the native role and again
   through the shared sink
-- `placeholder: string = ''` — falls back to the localized generic "Search" placeholder, which also
-  becomes the field's accessible name
+- `placeholder?: string` — query-field placeholder. Omission uses the localized generic "Search"
+  placeholder; an explicit empty string suppresses that fallback
 - `label?: string` — fallback name for the `role="search"` landmark; omission uses the localized
   retrieval-search label, while an explicit empty string stays empty
 - `accessibleLabel: string | null = null` (attribute `aria-label`) — as a JS-only property while

package/llms-full.txt

@@ -22621,10 +22621,12 @@ painted surface sits one boundary deeper. `<lr-drawer>` inherits this control an
 `<lr-icon-button>` itself.
 
 **The body is keyboard-reachable while it overflows.** `[part="body"]` is the element that scrolls,
-so it carries `tabindex="-1"` and joins the focus order **only while its content actually
-overflows** — a dialog whose content is nothing but prose, a table, or a rendered document used to
+so it carries `tabindex="0"` **only while its content actually overflows** — a dialog whose
+content is nothing but prose, a table, or a rendered document used to
 be scrollable with a mouse and completely unreachable from the keyboard, because a scroll container
-with no focusable child is not a stop of its own. A short body never becomes a gratuitous stop.
+with no focusable child is not a stop of its own. A short body keeps `tabindex="-1"` and never
+becomes a gratuitous stop. Resize and content changes update the body's tabindex as its overflow
+changes; `<lr-drawer>` uses the same behavior.
 
 It takes focus like any other stop, so it styles like one: `::part(body):focus-visible` draws the
 standard `--lr-focus-ring-*` ring, inset (`outline-offset` is negative) because the body is flush
@@ -24874,8 +24876,16 @@ closes caused by disablement, loading, or an unusable format list emit neither e
 attempt regardless of outcome — style with `::part(trigger-error)`), `menu`, `menu-item`,
 `format-label`, `format-description`
 
-**Themeable custom properties:** shared tokens only, including `--lr-popover-viewport-clamp`
-(default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed
+**Themeable custom properties:** the trigger's paint is settable per state. At rest,
+`--lr-export-button-background`, `--lr-export-button-color` and `--lr-export-button-border`; on
+hover, `--lr-export-button-hover-background`, `--lr-export-button-hover-color` and
+`--lr-export-button-hover-border`; while pressed, `--lr-export-button-active-background`,
+`--lr-export-button-active-color` and `--lr-export-button-active-border`. Each layers over whatever
+the current `appearance` resolves to and leaves the other paints alone, so they are also the way to
+keep `appearance="outlined"` chrome while returning its label to neutral text — `outlined` paints
+the label `--lr-color-brand` and, unlike `lr-button`, this component has no `variant` of its own to
+opt out. Before 18.4.0 none of these existed and the only lever was `::part(trigger)`. Plus shared
+tokens, including `--lr-popover-viewport-clamp` (default `92vw`) — the shared narrow-viewport ceiling the `menu`'s max-inline-size is `min()`ed
 against, alongside its own `20rem` cap and the positioner's available space. See `lr-tour` for the
 shared-clamp note.
 
@@ -25004,12 +25014,12 @@ buttons.
   Resolution prefers an element in the button's own root, then falls back to the owner document;
   a duplicate same-root id therefore wins without preventing a shadow-contained button from
   targeting an otherwise valid document-owned source.
-- `copyLabel: string = ''` (attribute `copy-label`) — built-in button accessible name and resting
-  tooltip text; empty uses localized `copy`.
-- `successLabel: string = ''` (attribute `success-label`) — confirmation name/tooltip text; empty
-  uses localized `copied`.
-- `errorLabel: string = ''` (attribute `error-label`) — failure name/tooltip text; empty uses
-  localized `copyFailed`.
+- `copyLabel?: string` (attribute `copy-label`) — built-in button accessible name and resting
+  tooltip text; omission uses localized `copy`, while an explicit empty string suppresses it.
+- `successLabel?: string` (attribute `success-label`) — confirmation name/tooltip text; omission
+  uses localized `copied`, while an explicit empty string suppresses it.
+- `errorLabel?: string` (attribute `error-label`) — failure name/tooltip text; omission uses
+  localized `copyFailed`, while an explicit empty string suppresses it.
 - `tooltip: 'full' | 'copy' | 'none' = 'full'` (reflected) — `full` shows the resting tooltip on
   hover/focus and feedback after activation, `copy` shows feedback only, and `none` disables it.
 - `tooltipPlacement: 'top' | 'right' | 'bottom' | 'left' = 'top'` (attribute
@@ -28145,8 +28155,9 @@ enabled buttons retain pointer feedback.
   constrained spaces (a toolbar, a table cell) — the same convention as `lr-empty`'s `compact`. The
   dashed border stays; only the internal spacing shrinks. `false` (the default) keeps the full
   `--lr-space-l` dropzone.
-- `label: string = ''` and `hint: string = ''`; an empty `label` leaves the localized dropzone
-  instruction (`fileInputDefaultLabel`) as the visible fallback
+- `label?: string` — form-control label. Omission uses the localized dropzone instruction
+  (`fileInputDefaultLabel`); an explicit empty string suppresses that fallback. `hint: string = ''`
+  remains empty when omitted and can be supplied through the named slot as well
 - `errorText: string = ''` (attribute `error-text`) — plain-text owned validation feedback. When
   it is empty, a `customError` message is rendered when present; otherwise an intrinsic validation
   message appears after the control has been interacted with. Rich `error` slot content replaces
@@ -30794,10 +30805,11 @@ structured points retain their y-value formatting.
     draws side by side with the first on that axis. Omitted series share one implicit group, so
     every chart written before `stack` existed sums exactly as it always did. Only meaningful on an
     axis that is actually stacked — see `stacked`/`stackedAxes` below.
-  `LyraChartPoint { readonly x: number; readonly
-  y: number; readonly r?: number; readonly label?: string }`: `r` is the bubble
-  radius, and the optional per-point `label` is retained by events, CSV export, keyboard
-  announcements, generated summaries, and the accessible table. Point wording is localized as
+  `LyraChartPoint { readonly x: number; readonly y: number; readonly r?: number; readonly id?:
+  string | number; readonly label?: string }`: `r` is the bubble radius, and the optional primitive
+  `id` is retained by activation events for application navigation or selection. Objects, symbols,
+  and non-finite numeric ids are omitted. The optional per-point `label` is retained by events, CSV
+  export, keyboard announcements, generated summaries, and the accessible table. Point wording is localized as
   whole messages: `chartPointCoordinates`, `chartBubblePointCoordinates`, and
   `chartLabeledPoint` own coordinate names, order, separators, and the label wrapper. A caller's
   point label is interpolated verbatim rather than translated or parsed. At runtime, non-record
@@ -31075,9 +31087,15 @@ const series = [
 point/segment, when a generated-table value is activated, or when Enter/Space activates the
 keyboard-current canvas datum; `detail: { datasetIndex: number, index: number, label: string |
 undefined, value: unknown }`). For scatter/bubble points, `label` prefers the per-point label and
-`value` is the complete `LyraChartPoint`, including optional `r` and `label`.
+`value` is the complete `LyraChartPoint`, including optional `r`, `id`, and `label`. A primitive
+`id` survives the same pointer, data-table, and keyboard activation paths; invalid ids are omitted.
 `lr-datum-activate` emits the same activation with `kind: 'bar'|'point'|'segment'|'slice'` for
-family-wide handling; `lr-point-click` remains as a compatibility event. Also
+family-wide handling. For scatter/bubble, both events carry the same `LyraChartPoint` value,
+including a string or finite-number `id` when supplied; invalid ids are omitted. The public
+`LyraChartPoint.id` type is `string | number`, while the activation event's heterogeneous `value`
+is typed `unknown`. Validate or explicitly narrow the value itself before reading point fields;
+checking `detail.kind === 'point'` alone does not narrow `detail.value` in TypeScript.
+`lr-point-click` remains as a compatibility event. Also
 `lr-before-legend-visibility-change` (cancelable proposal), and
 `lr-legend-visibility-change` (accepted commit). Both legend events carry
 `{ datasetIndex: number, visible: boolean, hiddenDatasets: readonly number[] }`; the latter is the
@@ -32241,6 +32259,7 @@ These named interfaces and helper signatures are available to typed integrations
     readonly x: number;
     readonly y: number;
     readonly r?: number;
+    readonly id?: string | number;
     readonly label?: string;
   }`
   Import: `@aceshooting/lyra-ui/components/charts/chart/chart.class.js`.
@@ -38711,10 +38730,10 @@ Citation; truncated?: boolean; omittedTokens?: number; redactions?: ContextInspe
 - `composerStatus: ChatComposerStatus = 'idle'` (attribute `composer-status`) — `'idle' | 'sending' |
 'streaming'`, `lr-chat-composer`'s own union; invalid values read as `idle` without rewriting the
   host attribute
-- `composerPlaceholder: string = ''` (attribute `composer-placeholder`)
+- `composerPlaceholder?: string` (attribute `composer-placeholder`)
 - `composerMinRows: number = 1` (attribute `composer-min-rows`), `composerMaxRows: number = 8`
   (attribute `composer-max-rows`)
-- `label: string = ''` — accessible name and visible heading
+- `label?: string` — accessible name and visible heading; omission uses the localized default and an explicit empty string suppresses it
 - `accessibleLabel: string | null = null` (attribute `aria-label`) — host-level accessible-name
   override for the internal `role="region"` root
 
@@ -42622,6 +42641,11 @@ typed events. Capabilities are denied unless explicitly enabled in `resource.per
 request with exactly one of `{ frameGeneration, result }` or `{ frameGeneration, error }`. Missing,
 stale, or ambiguous correlation fails closed. Both methods are no-ops before a frame exists.
 
+The initial `host-context` message includes a document-bound nonce and transfers a `MessagePort` to
+the executable document. Frame requests and host messages after bootstrap use that port. A same-frame
+navigation closes the port, invalidates the nonce and generation, and mounts a fresh sandbox before
+host data can be delivered.
+
 **Exported types:** `McpAppResource`, `McpAppCsp`, `McpAppPermissions`,
 `McpAppToolCallDetail`, `McpAppToolResultOptions`, and `LyraMcpAppEventMap`.
 
@@ -45723,8 +45747,8 @@ at the same size tier, so the toolbar row renders as one flush line.
   Remove any host `role="status"`/`role="alert"` hand-added before this property existed once it
   is set — otherwise the initial state is announced twice, through the native role and again
   through the shared sink
-- `placeholder: string = ''` — falls back to the localized generic "Search" placeholder, which also
-  becomes the field's accessible name
+- `placeholder?: string` — query-field placeholder. Omission uses the localized generic "Search"
+  placeholder; an explicit empty string suppresses that fallback
 - `label?: string` — fallback name for the `role="search"` landmark; omission uses the localized
   retrieval-search label, while an explicit empty string stays empty
 - `accessibleLabel: string | null = null` (attribute `aria-label`) — as a JS-only property while

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aceshooting/lyra-ui",
-  "version": "18.3.0",
+  "version": "19.0.0",
   "description": "Free, independent Lit web components: an open-source alternative to Shoelace and Web Awesome with accessible forms, dashboards, charts, and agent UI.",
   "keywords": [
     "web-components",
@@ -2890,7 +2890,7 @@
     "test:translation-slices": "node scripts/generate-translation-slices.test.mjs",
     "check:default-strings": "node scripts/check-default-strings.mjs",
     "test:default-strings": "node scripts/check-default-strings.test.mjs",
-    "test:tooling": "node scripts/build-llms.test.mjs && node --test scripts/create-component.test.mjs && node --test scripts/full-engine-shard.test.mjs && node --test scripts/coverage-shard-runner.test.mjs && node --test scripts/lint-ci-shard.test.mjs && node --test scripts/web-test-runner-config.test.mjs && node scripts/component-families.test.mjs && node scripts/maplibre-peer-range.test.mjs && node scripts/migrate-wa.test.mjs && node scripts/visual-regression-compare.test.mjs && node --test scripts/visual-regression-shard.test.mjs && node scripts/visual-regression-config.test.mjs && node --test scripts/check-source-policy.test.mjs scripts/check-test-assertions.test.mjs && node scripts/bundle-budgets.test.mjs && node scripts/compact-build-js.test.mjs && node scripts/compact-build-css.test.mjs && node scripts/compact-build-declarations.test.mjs && node --test scripts/normalize-mixin-declarations.test.mjs && node --test scripts/check-palette-freshness.test.mjs && node --test scripts/is-main-module.test.mjs && node scripts/manifest-compact.test.mjs && node --test scripts/viewer-fixture-generators.test.mjs && node --test scripts/strip-css-comments.test.mjs && node scripts/editor-web-types.test.mjs && node scripts/check-migration-coverage.test.mjs && node --test scripts/generate-theme-bootstrap.test.mjs",
+    "test:tooling": "node scripts/build-llms.test.mjs && node --test scripts/build-testing-event-registry.test.mjs && node --test scripts/create-component.test.mjs && node --test scripts/full-engine-shard.test.mjs && node --test scripts/coverage-shard-runner.test.mjs && node --test scripts/lint-ci-shard.test.mjs && node --test scripts/web-test-runner-config.test.mjs && node scripts/component-families.test.mjs && node scripts/maplibre-peer-range.test.mjs && node scripts/migrate-wa.test.mjs && node scripts/visual-regression-compare.test.mjs && node --test scripts/visual-regression-shard.test.mjs && node scripts/visual-regression-config.test.mjs && node --test scripts/check-source-policy.test.mjs scripts/check-test-assertions.test.mjs && node scripts/bundle-budgets.test.mjs && node scripts/compact-build-js.test.mjs && node scripts/compact-build-css.test.mjs && node scripts/compact-build-declarations.test.mjs && node --test scripts/normalize-mixin-declarations.test.mjs && node --test scripts/check-palette-freshness.test.mjs && node --test scripts/is-main-module.test.mjs && node scripts/manifest-compact.test.mjs && node --test scripts/viewer-fixture-generators.test.mjs && node --test scripts/strip-css-comments.test.mjs && node scripts/editor-web-types.test.mjs && node scripts/check-migration-coverage.test.mjs && node --test scripts/generate-theme-bootstrap.test.mjs",
     "framework-types": "node scripts/generate-framework-types.mjs",
     "check:framework-types": "node scripts/check-framework-types.mjs",
     "test:framework-types": "node scripts/generate-framework-types.test.mjs",