@aceshooting/lyra-ui 9.0.0 → 9.1.1

package/llms/peers.md

@@ -46,7 +46,7 @@ changes the component library version without installing a supported SheetJS rel
 | `libphonenumber-js` | `>=1.11.0 <2` | `lr-phone-input` |
 | `mammoth` | `^1.12.1` | `lr-docx-viewer` |
 | `maplibre-gl` | `>=5 <7` | `lr-geojson-view`, `lr-geojson-viewer`, `lr-map` |
-| `marked` | `^18.0.9` | `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-widget-renderer` |
+| `marked` | `^18.0.10` | `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-widget-renderer` |
 | `papaparse` | `^5.6.0` | `lr-csv-viewer`, `lr-dataset-viewer` |
 | `pdfjs-dist` | `^6.2.108` | `lr-pdf-viewer` |
 | `postal-mime` | `^3.0.0` | `lr-email-viewer` |

package/llms/shared.md

@@ -1620,6 +1620,19 @@ files matter when scaffolding a project's editor configuration. Build tools can
 through the explicit `@aceshooting/lyra-ui/custom-elements.json` package export; native Node ESM
 uses `with { type: 'json' }` on that import.
 
+**Inherited members in `custom-elements.json`.** A subclass declaration's `cssParts` array is
+always the complete flattened set, including everything inherited from a superclass — `::part()`
+has no type-level inheritance chain a consumer could otherwise walk. `attributes`, `members`,
+`events`, `slots`, and `cssProperties` are the opposite: a subclass declaration lists only its own
+entries plus any inherited entry it explicitly overrides, pruning an inherited-and-unmodified entry
+of those four kinds. This is intentional, not a gap — a TypeScript/JS consumer already gets the
+full set for free from the generated `.d.ts` `extends` chain, the same resolution `web-types.json`
+and `vscode-html-data.json` perform ahead of time. A consumer reading `custom-elements.json`
+directly and needing the complete `attributes`/`members`/`events`/`slots`/`cssProperties` set for
+those four kinds must walk the declaration's own `superclass.name`/`superclass.module` across
+`modules[].declarations[]` itself, or read `web-types.json`/`vscode-html-data.json` instead, which
+are already fully resolved.
+
 ## Independence and migration
 
 Lyra has no runtime, theme, or design-token dependency on Shoelace or Web Awesome. Documented `wa-*`

package/llms-full.txt

@@ -1672,6 +1672,19 @@ files matter when scaffolding a project's editor configuration. Build tools can
 through the explicit `@aceshooting/lyra-ui/custom-elements.json` package export; native Node ESM
 uses `with { type: 'json' }` on that import.
 
+**Inherited members in `custom-elements.json`.** A subclass declaration's `cssParts` array is
+always the complete flattened set, including everything inherited from a superclass — `::part()`
+has no type-level inheritance chain a consumer could otherwise walk. `attributes`, `members`,
+`events`, `slots`, and `cssProperties` are the opposite: a subclass declaration lists only its own
+entries plus any inherited entry it explicitly overrides, pruning an inherited-and-unmodified entry
+of those four kinds. This is intentional, not a gap — a TypeScript/JS consumer already gets the
+full set for free from the generated `.d.ts` `extends` chain, the same resolution `web-types.json`
+and `vscode-html-data.json` perform ahead of time. A consumer reading `custom-elements.json`
+directly and needing the complete `attributes`/`members`/`events`/`slots`/`cssProperties` set for
+those four kinds must walk the declaration's own `superclass.name`/`superclass.module` across
+`modules[].declarations[]` itself, or read `web-types.json`/`vscode-html-data.json` instead, which
+are already fully resolved.
+
 ## Independence and migration
 
 Lyra has no runtime, theme, or design-token dependency on Shoelace or Web Awesome. Documented `wa-*`
@@ -10597,7 +10610,7 @@ row?: number; col?: number; date?: string }`, matched the same way as `annotatio
   persistent ring (independent of keyboard focus) over the matching cell, appends a "Selected: ..."
   description to the host's own `aria-label`, and adds localized selected wording to the keyboard
   announcement when the focused cell is the selection. Purely a controlled property — mirrors
-  `<lr-lite-chart>`'s `selectedIndex`, this component never mutates it itself. Unset (the default,
+  `<lr-lite-chart>`'s `selectedIndices`, this component never mutates it itself. Unset (the default,
   `null`) reproduces today's exact output.
 - `accessibleCells: boolean = false` (attribute `accessible-cells`) — renders `[part="cells"]` with
   at most 400 `[part="cell"]` native buttons around the active cell. The semantic grid exposes the
@@ -22394,8 +22407,8 @@ true}))` still invokes the anchor's native activation behavior if nothing calls
 
 ## `lr-attachment-trigger`
 
-A compact attach affordance designed for a chat composer's leading slot (see `lr-chat-composer`'s
-own `leading` slot, which this drops straight into, though it has no code dependency on it). First-
+A compact attach affordance designed for a chat composer's start slot (see `lr-chat-composer`'s
+own `start` slot, which this drops straight into, though it has no code dependency on it). First-
 party invention (no Web Awesome equivalent). Its shape adapts to how many attachment `capabilities`
 are configured: exactly one renders a single plain icon button; more than one renders a small
 anchored menu (composed from `lr-dropdown`/`lr-menu`/`lr-menu-item`) listing each
@@ -25551,6 +25564,11 @@ import. Opening a `.zip` through `<lr-document-viewer>` forwards `anchor`/`highl
 viewer, so a deep link into an entry name survives the registry hop. `.tar`, `.rar`, and other
 archive formats fall through to `<lr-document-preview>`'s generic download fallback.
 
+A granular consumer (not importing the `all.js` compatibility bundle) must import
+`@aceshooting/lyra-ui/components/viewers/archive-viewer/archive-viewer-register.js` once to install
+this registration; without it `<lr-document-viewer>` never recognizes `.zip` files and falls
+through to the generic download fallback described above.
+
 Remote resources are capped at 25 MB; exceeding it surfaces the localized
 `documentPreviewResourceTooLarge` message instead of the entry listing.
 
@@ -25617,6 +25635,9 @@ unambiguous beside other previous/next controls and are overridable through `.st
 matches `application/epub+zip` and `.epub` filenames, declaring `{ anchors: ['cfi', 'text-quote'],
 search: true, textSelect: true }` capabilities and forwarding `anchor`/`highlights` to the mounted
 viewer. The peer loader requires the callable EPUB factory; malformed module shapes fail closed.
+A granular consumer (not importing the `all.js` compatibility bundle) must also import
+`@aceshooting/lyra-ui/components/viewers/ebook-viewer/ebook-viewer-register.js` once to install
+this registration; without it `<lr-document-viewer>` never recognizes `.epub` files.
 
 Remote resources are capped at 25 MB; exceeding it surfaces the localized
 `documentPreviewResourceTooLarge` message instead of the ebook.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aceshooting/lyra-ui",
-  "version": "9.0.0",
+  "version": "9.1.1",
   "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",
@@ -949,6 +949,7 @@
     "./components/utility/visually-hidden/visually-hidden.class.js": "./dist/components/utility/visually-hidden/visually-hidden.class.js",
     "./components/utility/visually-hidden/visually-hidden.js": "./dist/components/utility/visually-hidden/visually-hidden.js",
     "./components/viewers": "./dist/components/viewers/index.js",
+    "./components/viewers/archive-viewer/archive-viewer-register.js": "./dist/components/viewers/archive-viewer/archive-viewer-register.js",
     "./components/viewers/archive-viewer/archive-viewer.class.js": "./dist/components/viewers/archive-viewer/archive-viewer.class.js",
     "./components/viewers/archive-viewer/archive-viewer.js": "./dist/components/viewers/archive-viewer/archive-viewer.js",
     "./components/viewers/calendar-viewer/calendar-viewer.class.js": "./dist/components/viewers/calendar-viewer/calendar-viewer.class.js",
@@ -968,6 +969,7 @@
     "./components/viewers/document-viewer/registry.js": "./dist/components/viewers/document-viewer/registry.js",
     "./components/viewers/docx-viewer/docx-viewer.class.js": "./dist/components/viewers/docx-viewer/docx-viewer.class.js",
     "./components/viewers/docx-viewer/docx-viewer.js": "./dist/components/viewers/docx-viewer/docx-viewer.js",
+    "./components/viewers/ebook-viewer/ebook-viewer-register.js": "./dist/components/viewers/ebook-viewer/ebook-viewer-register.js",
     "./components/viewers/ebook-viewer/ebook-viewer.class.js": "./dist/components/viewers/ebook-viewer/ebook-viewer.class.js",
     "./components/viewers/ebook-viewer/ebook-viewer.js": "./dist/components/viewers/ebook-viewer/ebook-viewer.js",
     "./components/viewers/email-viewer/email-viewer.class.js": "./dist/components/viewers/email-viewer/email-viewer.class.js",
@@ -2264,7 +2266,7 @@
     "libphonenumber-js": ">=1.11.0 <2",
     "mammoth": "^1.12.1",
     "maplibre-gl": ">=5 <7",
-    "marked": "^18.0.9",
+    "marked": "^18.0.10",
     "papaparse": "^5.6.0",
     "pdfjs-dist": "^6.2.108",
     "postal-mime": "^3.0.0",
@@ -2403,7 +2405,7 @@
     "libphonenumber-js": "^1.13.11",
     "mammoth": "^1.12.1",
     "maplibre-gl": "^6.4.0",
-    "marked": "^18.0.9",
+    "marked": "^18.0.10",
     "oxc-parser": "^0.144.0",
     "papaparse": "^5.6.0",
     "pdfjs-dist": "^6.2.108",

package/vscode-html-data.json

@@ -1329,7 +1329,7 @@
       "name": "lr-attachment-trigger",
       "description": {
         "kind": "markdown",
-        "value": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's leading slot (see `<lr-chat-composer>`'s own `leading`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |"
+        "value": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's start slot (see `<lr-chat-composer>`'s own `start`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |"
       },
       "attributes": [
         {

package/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@aceshooting/lyra-ui",
-  "version": "9.0.0",
+  "version": "9.1.1",
   "description-markup": "markdown",
   "contributions": {
     "html": {
@@ -1289,7 +1289,7 @@
         },
         {
           "name": "lr-attachment-trigger",
-          "description": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's leading slot (see `<lr-chat-composer>`'s own `leading`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |",
+          "description": "`<lr-attachment-trigger>` — a compact attach affordance designed for a\nchat composer's start slot (see `<lr-chat-composer>`'s own `start`\nslot, which this drops straight into, though this component has no code\ndependency on it). Its shape adapts to how many attachment `capabilities`\nare configured:\n - Exactly one capability: a single plain icon button ([part='trigger']).\n   Activating it performs that capability's action directly.\n - More than one: a small anchored menu ([part='menu'], composed from\n   `<lr-dropdown>`/`<lr-menu>`/`<lr-menu-item>`) listing each capability as a row.\n\nTwo of the four capabilities (`files`, `image`) are file-picker-backed:\nactivating them opens a hidden native `<input type=\"file\">` via a\nsynthetic `.click()`, and the resulting selection is re-emitted as\n`lr-files`. `accept` is shared across both — `image` defaults it to\n`'image/*'` unless the `accept` prop overrides it, `files` always uses\n`accept` as-is (empty means \"any file type\", matching a bare native\n`<input type=\"file\">` with no `accept` attribute).\n\n**`camera`/`audio` are scope-limited by design.** This component does not\nimplement any camera or microphone capture UI itself — no `getUserMedia`,\nno `<input capture>` — because that's entirely a host/browser concern with\nno single right answer (a desktop web app, a mobile PWA, and a native\nwrapper all want different things here). Activating `camera` fires\n`lr-camera-request`; activating `audio` fires `lr-audio-request`. The\nhost owns everything from that point on — typically opening\n`<lr-push-to-talk>` in a `<lr-overlay>`/popover for `audio`, then\nhanding the resulting blob to something like `<lr-attachment-chip>`.\n\n---\n\n**Component metadata**\n\n- Status: `stable`\n- Since: `4.0.0`\n- Rationale: This exact lr-* tag appears in a published Lyra release manifest and remains a supported public contract under semver.\n- Graduation: Already stable; it retains that status while its documented behavior, accessibility, compatibility, and cross-browser support remain part of the public contract.\n\n---\n\n**CSS Shadow Parts**\n\n| Name | Description |\n| --- | --- |\n| `expand-icon` | The disclosure chevron inside the multi-capability trigger button. Only rendered when `capabilities.length > 1`. |\n| `hidden-input` | The internal native `<input type=\"file\">` that actually opens the OS file picker. Hidden (`display: none`) by default; exposed as a part only so a consumer can override that with `::part(hidden-input)` in the unlikely case their integration needs to. `accessibleLabel` supplies an accessible-name override for either trigger shape. A host `aria-label`, including an explicit empty value, wins over it. |\n| `menu` | The `<lr-dropdown>` shell. Only rendered when `capabilities.length > 1`. |\n| `menu-trigger` | The multi-capability button slotted into `<lr-dropdown>`'s `trigger` slot. Only rendered when `capabilities.length > 1`. |\n| `trigger` | The single-capability icon button. Only rendered when `capabilities.length === 1`. |",
           "attributes": [
             {
               "name": "accept",