@aceshooting/lyra-ui 21.0.0 → 21.1.0

package/llms/migration.md

@@ -1,4 +1,4 @@
-<!-- GENERATED by scripts/build-llms.mjs from scripts/fixtures/component-inventory.json — do not edit this file. -->
+<!-- GENERATED by scripts/build-llms.mjs from scripts/fixtures/component-inventory.json + scripts/fixtures/lyra-renames.json — do not edit this file. -->
 
 # Migrating to `lr-*`
 
@@ -68,6 +68,80 @@ set with a warning. Expand or classify them before applying, then rerun to verif
 | `lyra-v7` | `<lr-popup>` | `strategy="fixed"`, `placement="bottom-start"`, `distance="4"`, presence `flip`, presence `shift` |
 | `lyra-v7` | `<lr-tooltip>` | `distance="6"`, presence `without-arrow` |
 
+## Migrating from Lyra 21 to Lyra 22 (`--origin=lyra-v21`)
+
+Lyra 21 minor releases and Lyra 22 rename some Lyra-only attributes, properties, events, CSS parts,
+custom properties and slots. Each previous name keeps working as a deprecated alias until
+Lyra 23 removes it. Names mirrored from Web Awesome or Shoelace, and their defaults, never
+change. Run the CLI of the installed package after upgrading, within Lyra 21 or to Lyra 22. It
+applies only the entries the installed release ships, so running it again after a later upgrade
+picks up the rest:
+
+```bash
+npx lyra-ui-migrate --origin=lyra-v21 --diff src > lyra-v21.patch
+npx lyra-ui-migrate --origin=lyra-v21 --check --report=lyra-v21-migration.json src
+```
+
+`--diff` prints a patch and writes nothing. The profile rewrites a name only where the rewrite
+cannot change what the site reaches: attribute, property and slot bindings on the component in
+HTML, Lit, JSX, Vue, Svelte and Angular templates; `exportparts` and `::part()` or attribute
+selectors that name the component; and calls rooted at `querySelector('lr-…')`, `closest()` or
+`createElement()`. Events bubble and custom properties inherit, so a listener moves only when no
+other component already dispatches the new name, and an unowned listener or any custom-property
+use only when, in addition, every component with the old name renamed it the same way and the
+scanned code never dispatches the old name itself. Everything else is reported with a location;
+the old name keeps working meanwhile.
+
+| Code | Reported when |
+|---|---|
+| `RENAME_REVIEW` | An old name at a site that does not prove its component, or where another component keeps the name. |
+| `RENAME_TARGET_SHARED_REVIEW` | The new name is already used by another component, so renaming would widen the site. |
+| `NAME_GAINED_OWNER_REVIEW` | A listener, `::part()` selector or declaration of a name that more components use after the upgrade. |
+| `POLARITY_REVIEW` | A boolean replaced by its inverse is bound, assigned or selected, or set statically where a framework assigns properties. |
+| `DETAIL_SHAPE_REVIEW` | A listener may receive an event whose detail changed; details cannot be aliased. |
+| `DEPRECATED_MEMBER_REVIEW`, `DEPRECATED_CONTENT_REVIEW` | A deprecated member, tag or kind of slotted content without a mechanical replacement. |
+| `RENAME_CONFLICT_REVIEW` | The element already binds the new name, or the same receiver already listens to it with the same handler. |
+| `UNUSED_ACKNOWLEDGEMENT` | An acknowledgement comment matches no report. |
+
+After reviewing a site, add a comment containing `lyra-migrate-reviewed: CODE:name` (for example
+`DETAIL_SHAPE_REVIEW:lr-close`) on the reported line, alone on the line above it, or directly before
+the element's opening tag. Acknowledged reports no longer fail `--check`. Re-running the profile
+is idempotent. Templates rendered on the server must be re-rendered after migrating, because Lit
+hydration compares template strings.
+
+| Component | Kind | Deprecated name | New name | Handling |
+|---|---|---|---|---|
+| `<lr-markdown>` | attribute | `code-block-chrome` | `code-block-header` | Rewritten on the component; selectors reported (not reflected) |
+| `<lr-markdown>` | property | `codeBlockChrome` | `codeBlockHeader` | Rewritten where the component is proven |
+| `<lr-markdown-core>` | attribute | `code-block-chrome` | `code-block-header` | Rewritten on the component; selectors reported (not reflected) |
+| `<lr-markdown-core>` | property | `codeBlockChrome` | `codeBlockHeader` | Rewritten where the component is proven |
+| `<lr-media-card>` | event | `lr-before-media-download` | `lr-media-download-request` | Rewritten where the reach is unchanged, otherwise reported |
+| `<lr-message-parts>` | attribute | `code-block-chrome` | `code-block-header` | Rewritten on the component; selectors reported (not reflected) |
+| `<lr-message-parts>` | property | `codeBlockChrome` | `codeBlockHeader` | Rewritten where the component is proven |
+| `<lr-mutation-observer>` | attribute | `character-data` | `char-data` | Rewritten where the component is proven |
+| `<lr-mutation-observer>` | property | `characterData` | `charData` | Rewritten where the component is proven |
+| `<lr-streaming-text>` | attribute | `code-block-chrome` | `code-block-header` | Rewritten on the component; selectors reported (not reflected) |
+| `<lr-streaming-text>` | property | `codeBlockChrome` | `codeBlockHeader` | Rewritten where the component is proven |
+| `<lr-streaming-text-core>` | attribute | `code-block-chrome` | `code-block-header` | Rewritten on the component; selectors reported (not reflected) |
+| `<lr-streaming-text-core>` | property | `codeBlockChrome` | `codeBlockHeader` | Rewritten where the component is proven |
+
+| Component | Kind | Deprecated name | Replacement (manual) |
+|---|---|---|---|
+| `<lr-geojson-view>` | component | `lr-geojson-view` | `<lr-geojson-viewer>` |
+| `<lr-icon>` | attribute | `fixed-width` | `inline-size: var(--lr-size-1-5em) on that icon (or the --lr-icon-fixed-width value it used)` |
+| `<lr-icon>` | css-property | `--lr-icon-fixed-width` | `inline-size (the same value, on the fixed-width icons only)` |
+| `<lr-icon>` | property | `fixedWidth` | `inline-size: var(--lr-size-1-5em) on that icon (or the --lr-icon-fixed-width value it used)` |
+| `<lr-mutation-observer>` | attribute | `attributes` | `attr="*" (or just remove it where attr, attr-old-value or a non-empty attributeFilter is also set)` |
+| `<lr-mutation-observer>` | property | `observeAttributes` | `attr="*" (or just remove it where attr, attr-old-value or a non-empty attributeFilter is also set)` |
+| `<lr-sparkline>` | css-property | `--lr-sparkline-stroke-width` | `--line-width (the same value, declared on lr-sparkline itself)` |
+| `<lr-sparkline>` | part | `area` | `::part(fill)` |
+| `<lr-split-panel>` | part | `split-panel` | `::part(base)` |
+| `<lr-stat>` | slot | (default slot) | `slot="start"` |
+
+| Component | Slot | Reported content | Change |
+|---|---|---|---|
+| `<lr-menu>` | default | anything but `<hr>`, `<lr-divider>`, `<lr-dropdown-item>`, `<lr-menu-item>`, `<lr-menu-label>` | Only items, labels and separators belong in the menu list; move other content to slot="header" or slot="footer", which render it outside role="menu". |
+
 ## Classification summary
 
 | Ecosystem | Exact | Rewritten | Warning required | Conceptual only | Unsupported | Automatic | Manual |

package/llms/peers.md

@@ -59,7 +59,7 @@ for the page.
 | `marked` | `^18.0.11` | `lr-agent-workspace`, `lr-dashboard-grid`, `lr-eval-run`, `lr-markdown`, `lr-markdown-core`, `lr-message-parts`, `lr-notebook-viewer`, `lr-rag-answer`, `lr-streaming-text`, `lr-streaming-text-core`, `lr-widget-renderer` |
 | `papaparse` | `^5.7.0` | `lr-csv-viewer`, `lr-dataset-viewer` |
 | `pdfjs-dist` | `^6.3.289` | `lr-pdf-viewer` |
-| `postal-mime` | `^3.0.1` | `lr-email-viewer` |
+| `postal-mime` | `^3.0.1 || ^4.0.0` | `lr-email-viewer` |
 | `qrcode` | `^1.5.4` | `lr-qr-code` |
 | `react` | `>=19 <20` | type-only `@aceshooting/lyra-ui/custom-elements-jsx` entry (no runtime import) |
 | `shiki` | `^4.4.3` | `lr-agent-workspace`, `lr-code-block`, `lr-code-block-core`, `lr-dashboard-grid`, `lr-diff-view`, `lr-document-compare`, `lr-eval-result`, `lr-eval-run`, `lr-markdown`, `lr-markdown-core`, `lr-message-parts`, `lr-notebook-viewer`, `lr-rag-answer`, `lr-streaming-text`, `lr-streaming-text-core`, `lr-widget-renderer` |

package/llms/shared.md

@@ -30,15 +30,40 @@ customary M+1 warning period — `lr-usage-badge`'s `compact`, `lr-chart`'s `hor
 a mechanical migration listed in the 9.0.0 changelog entry and in `migration.md`. From 9.0.0 onward
 the M+2 rule applies as written; treat the above as a documented exception, not a precedent.
 
+Deprecation records also cover three things that are not a single member. Deprecated **slot
+content** is a kind of content inside a slot that stays supported (for example, content other than
+items in a menu's default slot); the slot's own description says which content is deprecated.
+Deprecated **package entry points** (an import path) and deprecated **exported types** are listed
+under "Deprecated package exports" at the end of `llms/index.md`; a deprecated type also carries
+`@deprecated` in its declaration, so editors strike it through. Each component's own deprecations
+are listed in its `llms/components/<tag>.md` header and in `custom-elements.json` (the declaration's
+`deprecations`, plus a `deprecation` on each deprecated member). These records are the complete
+list of deprecated APIs; audit an upgrade against them, not against console output.
+
+**Development warnings.** Some deprecations also log a development-mode `console.warn` naming the
+element, the deprecated API, and its replacement. A warning only ever fires for usage a component
+can observe cheaply and exactly — setting a deprecated property or attribute, connecting a
+deprecated tag, or vetoing through a deprecated alias event — and **not every deprecated API
+warns**: many deprecations have no runtime warning, among them `lr-icon`'s `auto-width`,
+`lr-stat`'s default-slot icon, `lr-menu`'s non-item default-slot content, the `lr-before-*` alias
+events of `lr-chart`, `lr-box-plot`, `lr-graph-legend` and `lr-graph-query-builder`, and
+`lr-command-palette`'s `lr-open` alias event, and deprecated CSS parts, custom properties, and
+custom states are styling hooks a component cannot observe, so they never warn. A silent console
+is therefore not evidence that an application uses no deprecated API. Where a warning exists, it
+fires once per page for each element name and deprecated API, and only when Lit runs its
+development build; production builds never warn. The deprecated form keeps working either
+way, and moving to the replacement removes the warning. A test suite that fails on console output
+while deliberately exercising a deprecated form can pre-seed Lit's development-mode
+`globalThis.litIssuedWarnings` set, before the element renders, with the key
+`lyra-deprecated:<tag>:<kind>:<name>` — `<kind>` and `<name>` as in the deprecation record.
+
 ### Release history and upgrade notes
 
-`since` records when a tag first appeared; it is not a history of later additions, fixes, or
-breaking changes. For every release after 9.0.0 — including minor and patch releases — read the
-package's shipped [CHANGELOG.md](../CHANGELOG.md) before upgrading. Family-wide breaking-change
-summaries sit at the start of the applicable authored `llms/<family>.md` file; each generated
-`llms/components/<tag>.md` header links that family summary when one exists. Component-specific
-version notes remain in the component's own section. `llms/migration.md` is narrower: it covers
-`wa-*`/`sl-*` renames and compatibility decisions, not Lyra release history.
+`since` records when a tag first appeared, not later changes. Before upgrading, read the
+package's [CHANGELOG.md](../CHANGELOG.md) (every release, including minor and patch).
+Family-wide breaking-change summaries open each authored `llms/<family>.md`, and each generated
+`llms/components/<tag>.md` header links its family summary. `llms/migration.md` covers only
+`wa-*`/`sl-*` renames, not Lyra release history.
 
 The major-version landmarks after 9.0.0 are:
 
@@ -2101,17 +2126,21 @@ override takes precedence over either page-level choice.
 
 To keep `<html lang>`/`dir` in step with `setLyraLocale()` — which everything _outside_ this library
 reads, from `:lang()` rules to spellcheck to a screen reader's pronunciation — use
-`bridgeLyraLocale()` from `@aceshooting/lyra-ui/utilities/localization.js` (see
+`bridgeLyraLocale()` from `@aceshooting/lyra-ui/localization.js` (see
 [Shared helpers](#shared-helpers-utilities)).
 
 The side-effect-free `@aceshooting/lyra-ui/localization.js` entry exports
 `registerLyraLocale`, `setLyraLocale`, `getLyraLocale`, `getLyraLocaleDirection`,
 `getRegisteredLyraLocales`, `getRegisteredLyraLocaleKeys`, `subscribeLyraLocaleRegistry`,
-`resolveLyraLocale`, `resolveLyraDirection`, `resolveLyraString`, `LYRA_DEFAULT_STRINGS`, and the types
+`subscribeLyraLocale`, `bridgeLyraLocale`, `resolveLyraLocale`, `resolveLyraDirection`,
+`resolveLyraString`, `resolveLyraScopedString`, `LYRA_DEFAULT_STRINGS`, and the types
 `LyraLocaleStrings`, `LyraLocaleMeta`, `LyraLocaleDirection`, `LyraMessageKey`, `LyraMessage`,
-`LyraPluralMessage` and `LyraPluralCategory`. The package root continues to re-export the same
-surface for compatibility and remains registration-free; use the dedicated entry when the
-application only needs locale setup and the narrower import graph.
+`LyraPluralMessage`, `LyraPluralCategory`, `LyraLocaleBridgeOptions` and `LyraLocaleBridgeCleanup`.
+The package root continues to re-export the runtime for compatibility and remains registration-free;
+use the dedicated entry when the application only needs locale setup and the narrower import graph.
+The `@aceshooting/lyra-ui/utilities/localization.js` entry point is deprecated, with removal not
+before 23.0.0: every name it exports is exported here as the identical binding, so change the import
+specifier to `@aceshooting/lyra-ui/localization.js` and nothing else.
 **`LYRA_DEFAULT_STRINGS` is the authoritative key list** (matching the `LyraMessageKey` union) —
 read it to find the key to override rather than guessing one. Date, number, byte, relative-time and
 calendar output goes through `Intl`.
@@ -2134,14 +2163,20 @@ category selection walks the same chain, so the two can never disagree:
    ceiling retains its exact tag, base language and English fallback without constructing an
    unbounded prefix ladder; malformed over-complex inherited input goes directly to English.
 2. **Then any registered, well-formed BCP-47 catalog sharing the base language**, which is how a
-   _regional-only_ catalog is reached from a less specific tag: `lang="zh"` and `lang="zh-Hans"`
-   both find the shipped `zh-CN` catalog, while `lang="pt"` reaches `pt-BR` and an exact `lang="pt-PT"`
-   selects the European Portuguese catalog. Order within this
-   step is deterministic and independent of import order — most shared subtags first
-   (`zh-Hant-TW` prefers a registered `zh-TW` over `zh-CN`), then alphabetically as the tie-break
-   (bare `zh` with both registered picks `zh-CN`). Register the regional tag you actually mean if
-   the tie-break isn't the answer you want. Legacy/custom tags are exact/truncation-addressable
-   only and do not become regional siblings accidentally.
+   _regional-only_ catalog is reached from a less specific tag (`lang="zh"` finds `zh-CN`,
+   `lang="pt"` finds `pt-BR`). Order is deterministic and independent of import order:
+   1. **Same likely script** — the explicit script subtag, else CLDR likely subtags via
+      `Intl.Locale#maximize()`. `zh-Hant`, `zh-HK`, `zh-MO` and `zh-Hant-CN` reach Traditional
+      `zh-TW`; `zh`, `zh-Hans`, `zh-SG` and `zh-Hans-HK` reach Simplified `zh-CN`. An unknown
+      script (none, `Zzzz`, or no `Intl.Locale`) never matches.
+   2. **Same likely region** — a region-less tag reaches its CLDR default region: bare `pt` picks
+      `pt-BR` even with `pt-PT` imported.
+   3. **Most shared subtags**, counting each occurrence (`pt-AO` and `pt-MZ` pick `pt-PT`;
+      `qaa-Hant-TW` picks `qaa-TW` over `qaa-CN`).
+   4. **Alphabetical**, as a stable tie-break.
+
+   Register the regional tag you mean if the ordering isn't what you want. Legacy/custom tags are
+   exact/truncation-addressable only and never become regional siblings.
 3. **Then `en`**, always available through the built-in English defaults.
 
 Step 1 always beats step 2: with both `zh` and `zh-CN` registered, `zh-Hans-CN` resolves to `zh`.
@@ -2184,7 +2219,7 @@ through to the next valid tier.
 sorted, deduped and canonically spelled. `subscribeLyraLocaleRegistry(listener: () => void): () =>
 void` fires when registry membership grows, including for a newly registered locale that is not
 active; extending an existing catalog does not change membership and does not fire it.
-`subscribeLyraLocale()` (on `@aceshooting/lyra-ui/utilities/localization.js`) instead fires when the
+`subscribeLyraLocale()` (also on `@aceshooting/lyra-ui/localization.js`) instead fires when the
 active selection changes or a registration can alter the active locale's messages/direction, and
 filters unrelated registrations. Both return an idempotent unsubscribe. Delivery uses the eligible
 starting listener snapshots: one callback failure cannot prevent later active, component or
@@ -2227,11 +2262,11 @@ import "@aceshooting/lyra-ui/translations/ar.js"; // declares dir: 'rtl'; direct
 import "@aceshooting/lyra-ui/translations/fa.js"; // fa-IR falls back to this base catalog
 import "@aceshooting/lyra-ui/translations/he.js"; // he-IL falls back to this base catalog
 import "@aceshooting/lyra-ui/translations/it.js"; // Italian
-import "@aceshooting/lyra-ui/translations/pt-BR.js"; // serves generic pt and pt-BR
-import "@aceshooting/lyra-ui/translations/pt-PT.js"; // European Portuguese
+import "@aceshooting/lyra-ui/translations/pt-BR.js"; // Brazilian: serves pt and pt-BR
+import "@aceshooting/lyra-ui/translations/pt-PT.js"; // European: serves pt-PT, pt-AO, pt-MZ
 import "@aceshooting/lyra-ui/translations/ro.js"; // Romanian
-import "@aceshooting/lyra-ui/translations/zh-CN.js"; // serves zh, zh-Hans and zh-Hans-CN
-import "@aceshooting/lyra-ui/translations/zh-TW.js"; // Traditional Chinese
+import "@aceshooting/lyra-ui/translations/zh-CN.js"; // Simplified: serves zh, zh-Hans, zh-SG and zh-Hans-CN
+import "@aceshooting/lyra-ui/translations/zh-TW.js"; // Traditional: serves zh-Hant, zh-HK and zh-MO
 ```
 
 Persian and Hebrew use CLDR plural categories (`fa`: `one`/`other`; `he`:
@@ -2243,10 +2278,11 @@ and `he` declare `dir: 'rtl'`, so `getLyraLocaleDirection()`
 answers for them (and for `ar-EG`, `fa-IR`, `he-IL`) — but locale selection still does not _force_
 writing direction: set `dir="rtl"` on the page or an ancestor yourself.
 
-`de-CH`, `pt-BR`, `pt-PT`, `zh-CN`, and `zh-TW` are regional catalogs. Step 2 of the lookup order above
-still makes each reachable from a less-specific language tag, while an exact `lang="de-CH"`,
-`lang="pt-PT"` or `lang="zh-TW"` selects its dedicated regional catalog. They are listed under their real tags in
-`getRegisteredLyraLocales()`.
+`de-CH`, `pt-BR`, `pt-PT`, `zh-CN`, and `zh-TW` are regional catalogs: an exact tag always selects
+its own catalog, and a less specific tag reaches one through step 2 only when nothing on its
+truncation walk answers first (with `de` imported, `lang="de-AT"` resolves to `de`, never `de-CH`).
+The same routing drives plural selection and `getLyraLocaleDirection()`. They are listed under
+their real tags in `getRegisteredLyraLocales()`.
 
 Import only the locales the application can actually offer — each is a separate module, so unimported
 ones cost nothing. A catalog registered this way is merged like any other, so a later
@@ -2382,6 +2418,14 @@ import {
   validates them on `tool-upsert` events and `tool-call` parts: a non-finite or non-number time, or
   a `redactedFields` that is not an array of at most 100 strings of at most 4,096 characters, fails
   the event as `invalid_stream_event`.
+- **Tool display name and incomplete calls** (21.1.0) — `ToolInvocation.displayName` is the
+  application's own, already-translated tool label; `<lr-message-parts>` (both `tool-display`
+  modes) and `<lr-tool-timeline>` show it in place of `name`, which still selects the result
+  renderer. `status: 'incomplete'` marks a call that ended without a result (an interrupted stream,
+  a cancelled run); set it yourself on a `tool-upsert` or `tool-call` part, since the adapters never
+  infer it. The runtime accepts both on `tool-upsert` events, `tool-call` parts and message
+  snapshots; a `displayName` that is not a string of at most `maxIdentifierCharacters` fails the
+  event as `invalid_stream_event`, and a later upsert that omits it keeps the retained one.
 - **Resource limits** — pass a partial `AgentStreamLimits` to `createAgentStreamState()`, or adapter
   limit options to the relevant adapter. The exported `DEFAULT_AGENT_STREAM_LIMITS`,
   `DEFAULT_AI_SDK_ADAPTER_LIMITS`, `DEFAULT_AG_UI_ADAPTER_LIMITS`, and
@@ -3222,9 +3266,12 @@ readonly politeness: AnnouncementPoliteness; messageTtlMs: number; announce(text
 release(): void }`, and `AnnouncerTimerHost { setTimeout(handler: () => void, timeout: number):
 number; clearTimeout(handle: number): void }`.
 - **`localization` → `subscribeLyraLocale(listener): () => void` and
-  `bridgeLyraLocale(options?): () => void`** — the _active-locale_ half of the locale runtime,
-  which the side-effect-free `@aceshooting/lyra-ui/localization.js` entry does not carry (that one
-  has `subscribeLyraLocaleRegistry()`, which answers a different question — see "Localization").
+  `bridgeLyraLocale(options?): () => void`** — the _active-locale_ half of the locale runtime.
+  **This `utilities/localization.js` entry point is deprecated**, with removal not before 23.0.0:
+  import every name below from the side-effect-free `@aceshooting/lyra-ui/localization.js` entry,
+  which exports the identical bindings and types. The extensionless `@aceshooting/lyra-ui/utilities`
+  barrel keeps exporting them. `subscribeLyraLocale()` is distinct from
+  `subscribeLyraLocaleRegistry()`, which answers a different question — see "Localization".
   `subscribeLyraLocale()` fires whenever the active selection changes, and when a newly registered
   or extended catalog can alter that selection's messages or direction. Registrations unrelated to
   the active lookup chain are filtered. An application can therefore re-render its **own**
@@ -3247,8 +3294,7 @@ number; clearTimeout(handle: number): void }`.
   Its exact options record is `LyraLocaleBridgeOptions { target?: Element; direction?: boolean }`.
 
   ```ts
-  import { bridgeLyraLocale } from "@aceshooting/lyra-ui/utilities/localization.js";
-  import { setLyraLocale } from "@aceshooting/lyra-ui/localization.js";
+  import { bridgeLyraLocale, setLyraLocale } from "@aceshooting/lyra-ui/localization.js";
   import "@aceshooting/lyra-ui/translations/ar.js";
 
   const stop = bridgeLyraLocale(); // mirrors onto <html>
@@ -3259,13 +3305,13 @@ number; clearTimeout(handle: number): void }`.
   `resolveLyraScopedString(/* public names: host, key, defaults, overrides, fallback, values */):
 unknown` is a scoped variant of `resolveLyraString()` (see "Localization"): the same
 override → fallback → registered-locale-catalog resolution chain, but against a caller-supplied
-`defaults` record instead of the complete `LYRA_DEFAULT_STRINGS` catalog. It lives on this
-tree-shakable entry rather than the side-effect-free `@aceshooting/lyra-ui/localization.js` one so
-that resolving a handful of an application's own messages never pulls in the full compatibility
-catalog to do it — pass a small `defaults` object of just the keys used.
+`defaults` record instead of the complete `LYRA_DEFAULT_STRINGS` catalog, so resolving a handful
+of an application's own messages never needs the full compatibility catalog — pass a small
+`defaults` object of just the keys used. `@aceshooting/lyra-ui/localization.js` is side-effect-free,
+so a bundler drops the unused catalog; an unbundled graph that imports it still loads the catalog.
 
   ```ts
-  import { resolveLyraScopedString } from "@aceshooting/lyra-ui/utilities/localization.js";
+  import { resolveLyraScopedString } from "@aceshooting/lyra-ui/localization.js";
 
   const label = resolveLyraScopedString(host, "save", { save: "Save" });
   ```
@@ -3662,6 +3708,7 @@ These named interfaces and helper signatures are available to typed integrations
   `ToolInvocation {
   id: unknown;
   name: unknown;
+  displayName: unknown;
   args: unknown;
   status: unknown;
   result: unknown;