@oicl/openbridge-webcomponents 2.0.0-next.96 → 2.0.0-next.98

package/custom-elements.json

@@ -6874,7 +6874,8 @@
               "name": "layer-selection-changed",
               "type": {
                 "text": "Event"
-              }
+              },
+              "description": "{Event} Fired when the layer's `isSelected` state changes. Bubbles."
             }
           ],
           "attributes": [
@@ -6961,6 +6962,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcPoiObjectAton",
+          "slots": [
+            {
+              "description": "Icon content rendered inside the POI object.",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -11223,7 +11230,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-poi>` - Composite marker component that renders a target button with connector and pointer visuals.\n\n## Overview\nCombines `obc-poi-button`, `obc-poi-line`, and optional pointer visuals to display\ninteractive marker/callout targets in line, offset, point, or outside modes.\nKeywords: marker, callout, pin, label, target, pointer.\n\n## Features/Variants\n\nConfiguration defaults and behavior:\n- `type` (default: `line`):\n  - `line`: renders a vertical connector line from button to target.\n  - `offset`: renders a bent connector using `targetOffsetX - buttonOffsetX`.\n  - `point`: suppresses long connector behavior (line can collapse/skip based on state).\n  - `outside`: suppresses connector line; outside arrow is rendered when `hasPointer` is true.\n- `value` (default: `unchecked`):\n  - `unchecked`: default visual state.\n  - `checked`: selected-like visual and pointer behavior.\n  - `activated`: activated button visual state with selected-like pointer behavior.\n  - `overlapped`: compact overlap visual state.\n- `overlapOpaque` (default: `false`): controls overlapped opacity mode (`false` = translucent, `true` = opaque).\n- `state` (default: `enabled`):\n  - `enabled`: neutral alert ring and regular line style.\n  - `caution`/`warning`/`alarm`: applies alert-specific button/line styling.\n  - In `enabled`, pointer type resolution defaults to point.\n- `selected` (default: `false`): enables selected emphasis semantics (for example selected line style when not in alert state).\n- `hasPointer` (default: `false`):\n  - For `line`/`offset`/`point`, pointer visuals are shown when `hasPointer` is true.\n  - Checked-like values also force inline pointer visuals for non-`outside` types.\n  - For `outside`, `hasPointer` controls outside-arrow visibility.\n- `pointerType` (default: `null`, enum `point | button | camera`):\n  - Used when not in checked-like state and not `enabled`.\n  - Otherwise resolves to `point` for consistent selected/enabled behavior.\n- `pointerState` (default: `null`, enum `regular | selected | active | uncertain`):\n  - Checked-like non-`outside` values resolve to `selected`.\n  - Otherwise falls back to provided `pointerState` or `regular`.\n\nMotion and layout notes:\n- `animatePosition` (default: `false`): when true, enables short position transition timing for line/pointer movement.\n- `x` (default: `0`): host horizontal position; sets `--obc-poi-x` as `${x}px`.\n- `y` (default: `96`): absolute local target Y; non-finite values fall back to `0` in geometry calculations.\n- `buttonY` (default: `0`): when `fixedTarget=false`, anchors the button at its local Y while the target is derived below it from `y`; when `fixedTarget=true`, preserves the legacy host-anchor behavior.\n- `buttonOffsetX`/`targetOffsetX` (defaults: `0`/`0`): define connector bend delta via `targetOffsetX - buttonOffsetX`.\n- `boxWidth`/`boxHeight` (defaults: `null`/`null`): optional pointer frame size extras; invalid/non-finite values are ignored.\n- `outsideAngle` (default: `315`): controls outside-arrow direction in `outside` mode.\n\n## Usage Guidelines\n\n- Use `type=\"line\"` or `type=\"offset\"` when the button should connect to a remote target.\n- Use `type=\"point\"` for near-target placements where connector emphasis should be minimal.\n- Use `type=\"outside\"` with `hasPointer` for off-screen or directional guidance.\n- Keep `value`, `state`, and `selected` aligned with domain state so visual semantics stay consistent.\n- Provide finite numbers for layout props (`x`, `y`, `buttonY`, offsets) for predictable placement.\n\n## Slots/Content\n\n- Default slot: Main icon/content rendered inside `obc-poi-button`.\n- `header`: Optional custom header content rendered above the POI object.\n\n## Events\n\nThis component does not emit custom events.\n\n## Best Practices\n\n- Pass finite numeric values for layout properties to avoid fallback-to-zero behavior.\n- Enable `animatePosition` only for intentional motion transitions and moving targets.\n- Prefer enum values for `type`, `value`, `state`, `pointerType`, and `pointerState`.\n\n## Example\n\n```html\n<obc-poi type=\"line\" value=\"unchecked\" state=\"enabled\">\n  <obi-placeholder></obi-placeholder>\n</obc-poi>\n```",
+          "description": "`<obc-poi>` - Composite marker component that renders a target button with connector and pointer visuals.\n\n## Overview\nCombines `obc-poi-button`, `obc-poi-line`, and optional pointer visuals to display\ninteractive marker/callout targets in line, offset, point, or outside modes.\nKeywords: marker, callout, pin, label, target, pointer.\n\n## Features/Variants\n\nConfiguration defaults and behavior:\n- `type` (default: `line`):\n  - `line`: renders a vertical connector line from button to target.\n  - `offset`: renders a bent connector using `targetOffsetX - buttonOffsetX`.\n  - `point`: suppresses long connector behavior (line can collapse/skip based on state).\n  - `outside`: suppresses connector line; outside arrow is rendered when `hasPointer` is true.\n- `value` (default: `unchecked`):\n  - `unchecked`: default visual state.\n  - `checked`: selected-like visual and pointer behavior.\n  - `activated`: activated button visual state with selected-like pointer behavior.\n  - `overlapped`: compact overlap visual state.\n- `overlapOpaque` (default: `false`): controls overlapped opacity mode (`false` = translucent, `true` = opaque).\n- `state` (default: `enabled`):\n  - `enabled`: neutral alert ring and regular line style.\n  - `caution`/`warning`/`alarm`: applies alert-specific button/line styling.\n  - In `enabled`, pointer type resolution defaults to point.\n- `selected` (default: `false`): enables selected emphasis semantics (for example selected line style when not in alert state).\n- `hasPointer` (default: `false`):\n  - For `line`/`offset`/`point`, pointer visuals are shown when `hasPointer` is true.\n  - Checked-like values also force inline pointer visuals for non-`outside` types.\n  - For `outside`, `hasPointer` controls outside-arrow visibility.\n- `pointerType` (default: `null`, enum `point | button | camera`):\n  - Used when not in checked-like state and not `enabled`.\n  - Otherwise resolves to `point` for consistent selected/enabled behavior.\n- `pointerState` (default: `null`, enum `regular | selected | active | uncertain`):\n  - Checked-like non-`outside` values resolve to `selected`.\n  - Otherwise falls back to provided `pointerState` or `regular`.\n\nMotion and layout notes:\n- `animatePosition` (default: `false`): when true, enables short position transition timing for line/pointer movement.\n- `x` (default: `0`): host horizontal position; sets `--obc-poi-x` as `${x}px`.\n- `y` (default: `96`): absolute local target Y; non-finite values fall back to `0` in geometry calculations.\n- `buttonY` (default: `0`): when `fixedTarget=false`, anchors the button at its local Y while the target is derived below it from `y`; when `fixedTarget=true`, preserves the legacy host-anchor behavior.\n- `buttonOffsetX`/`targetOffsetX` (defaults: `0`/`0`): define connector bend delta via `targetOffsetX - buttonOffsetX`.\n- `boxWidth`/`boxHeight` (defaults: `null`/`null`): optional pointer frame size extras; invalid/non-finite values are ignored.\n- `outsideAngle` (default: `315`): controls outside-arrow direction in `outside` mode.\n\n## Usage Guidelines\n\n- Use `type=\"line\"` or `type=\"offset\"` when the button should connect to a remote target.\n- Use `type=\"point\"` for near-target placements where connector emphasis should be minimal.\n- Use `type=\"outside\"` with `hasPointer` for off-screen or directional guidance.\n- Keep `value`, `state`, and `selected` aligned with domain state so visual semantics stay consistent.\n- Provide finite numbers for layout props (`x`, `y`, `buttonY`, offsets) for predictable placement.\n\n## Slots/Content\n\n- Default slot: Main icon/content rendered inside `obc-poi-button`.\n- `button`: Optional custom button element replacing the default `obc-poi-button`.\n- `header`: Optional header content. Relocated into the inner `obc-poi-button` at runtime by a `MutationObserver` (there is no `<slot name=\"header\">` element).\n\n## Events\n\nThis component does not emit custom events.\n\n## Best Practices\n\n- Pass finite numeric values for layout properties to avoid fallback-to-zero behavior.\n- Enable `animatePosition` only for intentional motion transitions and moving targets.\n- Prefer enum values for `type`, `value`, `state`, `pointerType`, and `pointerState`.\n\n## Example\n\n```html\n<obc-poi type=\"line\" value=\"unchecked\" state=\"enabled\">\n  <obi-placeholder></obi-placeholder>\n</obc-poi>\n```",
           "name": "ObcPoi",
           "slots": [
             {
@@ -11231,7 +11238,11 @@
               "name": ""
             },
             {
-              "description": "Optional custom header content.",
+              "description": "Optional custom button element replacing the default `obc-poi-button`.",
+              "name": "button"
+            },
+            {
+              "description": "Optional header content, relocated into the inner `obc-poi-button` at runtime.",
               "name": "header"
             }
           ],
@@ -12678,6 +12689,16 @@
           "kind": "class",
           "description": "",
           "name": "ObcAutomationBadge",
+          "slots": [
+            {
+              "description": "Custom silhouette/outline icon, rendered behind the default slot content when no built-in badge type matches.",
+              "name": "icon-silhouette"
+            },
+            {
+              "description": "Default slot for custom badge content, rendered when no built-in badge type matches.",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -14792,6 +14813,44 @@
           "kind": "class",
           "description": "",
           "name": "ObcAutomationButton",
+          "slots": [
+            {
+              "description": "Content projected into the top-right badge position of the button.",
+              "name": "badge-top-right"
+            },
+            {
+              "description": "Content projected into the top-left badge position of the button.",
+              "name": "badge-top-left"
+            },
+            {
+              "description": "Content projected into the bottom-left badge position of the button.",
+              "name": "badge-bottom-left"
+            },
+            {
+              "description": "Content projected into the bottom-right badge position of the button.",
+              "name": "badge-bottom-right"
+            },
+            {
+              "description": "Primary icon shown inside the button (regular, double, flat and square variants).",
+              "name": "icon"
+            },
+            {
+              "description": "Silhouette/outline icon shown behind the primary icon (flat variant only).",
+              "name": "icon-silhouette"
+            },
+            {
+              "description": "Custom icon for the alert frame, shown when alert==true and positioning==\"point\".",
+              "name": "alert-icon"
+            },
+            {
+              "description": "Label for the alert frame, shown when alert==true and positioning==\"point\".",
+              "name": "alert-label"
+            },
+            {
+              "description": "Timer for the alert frame, shown when alert==true and positioning==\"point\".",
+              "name": "alert-timer"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -15265,6 +15324,24 @@
           "kind": "class",
           "description": "",
           "name": "ObcAutomationInputModal",
+          "slots": [
+            {
+              "description": "Header content shown at the top of the modal.",
+              "name": "header"
+            },
+            {
+              "description": "Preview content shown in the body of the modal.",
+              "name": "preview"
+            },
+            {
+              "description": "Primary action control shown in the actions row.",
+              "name": "action-primary"
+            },
+            {
+              "description": "Secondary action control shown in the actions row.",
+              "name": "action-secondary"
+            }
+          ],
           "members": [],
           "superclass": {
             "name": "LitElement",
@@ -15458,7 +15535,7 @@
               "name": "current-value"
             },
             {
-              "description": "Content for additional detail rows.",
+              "description": "Detail rows below the main readout, shown in the regular (non-compact, non-static) layout. Slot an `<obc-readout-list>` of `<obc-readout-list-item>` rows — it owns the row typography and cross-row column alignment; the tank renders a divider above it automatically when the slot is filled.",
               "name": "rich"
             },
             {
@@ -15703,15 +15780,6 @@
               "description": "Number of fraction digits used to format the percent readout in the\nnon-compact (regular) layout. Defaults to `0` (integer percent). The\ncompact layout always renders integer percent to keep its fixed-width\nfootprint stable. The static layout renders capacity (`max` + `unit`)\nrather than percent, so this property has no effect there — pass a\npre-formatted value through the `max-value` slot if fractional\nprecision is needed (see the `WithFractionDigits` story).",
               "attribute": "percentFractionDigits"
             },
-            {
-              "kind": "field",
-              "name": "readout",
-              "type": {
-                "text": "TankReadoutItem[]"
-              },
-              "default": "[]",
-              "description": "Rich detail rows shown below the main percent/value block in the regular\n(non-compact, non-static) layout, separated by a divider. When empty (the\ndefault), nothing is rendered — neither the divider nor the list. In\nvertical orientation the chart cell shrinks to make room; in horizontal\norientation the readout column already has reserved whitespace so the\nchart is unaffected.\n\nValues are formatted using `percentFractionDigits`. Consumers that need\nfull control over the markup can replace the entire fallback by slotting\narbitrary content into `slot=\"rich\"` (note: this is a different name from\nthe existing `slot=\"readout\"` which replaces the whole readout block)."
-            },
             {
               "kind": "field",
               "name": "badgeControl",
@@ -15782,6 +15850,16 @@
               "privacy": "private",
               "default": "false"
             },
+            {
+              "kind": "field",
+              "name": "_hasRichSlot",
+              "type": {
+                "text": "boolean"
+              },
+              "privacy": "private",
+              "default": "false",
+              "description": "Tracks whether the `rich` slot has assigned content, so the regular\n(non-compact) layout only draws the rich divider when a consumer has\nslotted detail rows (canonically an `<obc-readout-list>`). Mirrors\n`_hasBadges` / `_hasTagSlot`."
+            },
             {
               "kind": "field",
               "name": "_chartResizeObserver",
@@ -15892,6 +15970,24 @@
                 }
               ]
             },
+            {
+              "kind": "method",
+              "name": "_onRichSlotChange",
+              "privacy": "private",
+              "return": {
+                "type": {
+                  "text": "void"
+                }
+              },
+              "parameters": [
+                {
+                  "name": "e",
+                  "type": {
+                    "text": "Event"
+                  }
+                }
+              ]
+            },
             {
               "kind": "method",
               "name": "_syncChartResizeObserver",
@@ -35616,6 +35712,24 @@
           "kind": "class",
           "description": "",
           "name": "ObcAlertList",
+          "slots": [
+            {
+              "description": "Default slot for the alert list items.",
+              "name": ""
+            },
+            {
+              "description": "Icon shown when the list is empty.",
+              "name": "empty-icon"
+            },
+            {
+              "description": "Title shown when the list is empty.",
+              "name": "empty-title"
+            },
+            {
+              "description": "Description shown when the list is empty.",
+              "name": "empty-description"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -36384,7 +36498,8 @@
               "name": "scale-dimensions-changed",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} Fired when the scale's computed layout thickness changes; a parent chart listens for this to reserve space for the scale. Bubbles and is composed."
             }
           ],
           "attributes": [
@@ -37476,7 +37591,8 @@
               "name": "scale-dimensions-changed",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} Fired when the scale's computed layout thickness changes; a parent chart listens for this to reserve space for the scale. Bubbles and is composed."
             }
           ],
           "attributes": [
@@ -40065,17 +40181,13 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-advice-floating-item>` – A floating advice notification component for transient, context-sensitive messages.\n\nDisplays a brief advice or informational message that overlays the interface, typically used to provide non-blocking feedback, guidance, or status updates. This component is a specialized variant of a floating message (toast/snackbar) with a visual emphasis on advice or recommendations.\n\nAppears temporarily above the UI and can include icons, timestamps, actions, and multi-line content. Designed for scenarios where users need timely, non-intrusive advice or suggestions without interrupting their workflow.\n\n## Features\n- **Advice Notification Style:** Uses a distinct advice icon and color to visually differentiate advice messages from other notifications.\n- **Variants (type):**\n  - `regular` (default): Standard advice message with a single advice icon.\n  - `application`: Enhanced advice message supporting an additional icon (e.g., to indicate application context or source).\n- **Layout Directions:** Supports `horizontal` (side-by-side) or `vertical` (stacked) layouts to adapt to available space.\n- **Line Type:** Choose between `singleLine` (compact, one-line message) or `multiLine` (for longer advice or descriptions).\n- **Timestamp and Day Labels:** Optionally display a time and/or day label for context.\n- **Action Buttons:** Supports up to two action buttons (primary and secondary) for user response or quick actions.\n- **Slot-based Content:** Flexible content insertion for icons, title, description, time, day, and actions.\n- **Automatic Icon Handling:** Advice icon is rendered automatically; developers can override or supplement with their own icons via slots.\n\n## Usage Guidelines\nUse `<obc-advice-floating-item>` to present brief, non-blocking advice, tips, or contextual guidance to users. Ideal for situations where you want to draw attention to a recommended action, best practice, or informational update without requiring immediate user intervention.\n\n- Suitable for transient feedback, inline help, or system-generated suggestions.\n- Not intended for critical alerts or persistent warnings—use a dialog or alert banner for those cases.\n- For advice that requires user action, enable one or both action buttons.\n- If the advice is related to a specific time or event, use the timestamp and day labels for clarity.\n\n**TODO(designer):** Confirm if there are recommended durations for auto-dismiss, or if all advice messages require manual dismissal.\n\n## Slots\n| Slot Name      | Renders When...                      | Purpose                                                      |\n| -------------- | ------------------------------------ | ------------------------------------------------------------ |\n| primary-icon   | Always (unless overridden)           | Main advice icon (default: `<obi-notification-advice-active>`) or custom icon. |\n| secondary-icon | Only when `type=\"application\"`       | Additional icon for application-type advice messages.         |\n| title          | Always                               | Title or heading of the advice message.                      |\n| description    | Always                               | Detailed advice or message text.                             |\n| time           | If `hasTimestamp` is true            | Timestamp label (e.g., \"09:12:46\").                          |\n| day            | If `hasTimestamp` and `hasDay`       | Day label (e.g., \"Yesterday\").                               |\n| action         | If `action` is true                  | Primary action button label/content.                         |\n| action2        | If `action2` is true                 | Secondary action button label/content.                       |\n\n## Events\n- `action-click` – Fired when the primary action button is clicked.\n- `action2-click` – Fired when the secondary action button is clicked.\n- `dismiss-click` – Fired when the advice message is dismissed (e.g., close icon or auto-hide).\n\n## Best Practices\n- Use concise, actionable advice text to maximize clarity.\n- Limit to one or two actions to avoid overwhelming the user.\n- For longer advice, use the `multiLine` line type to improve readability.\n- Only use the secondary action for supplementary or \"undo\" actions.\n- Ensure advice messages do not overlap or stack excessively; only one should be visible at a time if possible.\n\n## Example:\n```html\n<obc-advice-floating-item type=\"application\" direction=\"vertical\" hasTimestamp action>\n  <div slot=\"primary-icon\"><obi-placeholder></obi-placeholder></div>\n  <span slot=\"title\">Advice title</span>\n  <span slot=\"description\">An advice message with meaningful content for the user.</span>\n  <span slot=\"time\">09:12:46</span>\n  <span slot=\"action\">Close</span>\n</obc-advice-floating-item>\n```",
+          "description": "`<obc-advice-floating-item>` – A floating advice notification component for transient, context-sensitive messages.\n\nDisplays a brief advice or informational message that overlays the interface, typically used to provide non-blocking feedback, guidance, or status updates. This component is a specialized variant of a floating message (toast/snackbar) with a visual emphasis on advice or recommendations.\n\nAppears temporarily above the UI and can include icons, timestamps, actions, and multi-line content. Designed for scenarios where users need timely, non-intrusive advice or suggestions without interrupting their workflow.\n\n## Features\n- **Advice Notification Style:** Uses a distinct advice icon and color to visually differentiate advice messages from other notifications.\n- **Variants (type):**\n  - `regular` (default): Standard advice message with a single advice icon.\n  - `application`: Enhanced advice message supporting an additional icon (e.g., to indicate application context or source).\n- **Layout Directions:** Supports `horizontal` (side-by-side) or `vertical` (stacked) layouts to adapt to available space.\n- **Line Type:** Choose between `singleLine` (compact, one-line message) or `multiLine` (for longer advice or descriptions).\n- **Timestamp and Day Labels:** Optionally display a time and/or day label for context.\n- **Action Buttons:** Supports up to two action buttons (primary and secondary) for user response or quick actions.\n- **Slot-based Content:** Flexible content insertion for icons, title, description, time, day, and actions.\n- **Automatic Icon Handling:** Advice icon is rendered automatically; developers can override or supplement with their own icons via slots.\n\n## Usage Guidelines\nUse `<obc-advice-floating-item>` to present brief, non-blocking advice, tips, or contextual guidance to users. Ideal for situations where you want to draw attention to a recommended action, best practice, or informational update without requiring immediate user intervention.\n\n- Suitable for transient feedback, inline help, or system-generated suggestions.\n- Not intended for critical alerts or persistent warnings—use a dialog or alert banner for those cases.\n- For advice that requires user action, enable one or both action buttons.\n- If the advice is related to a specific time or event, use the timestamp and day labels for clarity.\n\n**TODO(designer):** Confirm if there are recommended durations for auto-dismiss, or if all advice messages require manual dismissal.\n\n## Slots\n| Slot Name      | Renders When...                      | Purpose                                                      |\n| -------------- | ------------------------------------ | ------------------------------------------------------------ |\n| primary-icon   | Only when `type=\"application\"`       | Custom main icon (the built-in advice icon is used otherwise). |\n| title          | Always                               | Title or heading of the advice message.                      |\n| description    | Always                               | Detailed advice or message text.                             |\n| time           | If `hasTimestamp` is true            | Timestamp label (e.g., \"09:12:46\").                          |\n| day            | If `hasTimestamp` and `hasDay`       | Day label (e.g., \"Yesterday\").                               |\n| action         | If `action` is true                  | Primary action button label/content.                         |\n| action2        | If `action2` is true                 | Secondary action button label/content.                       |\n\n## Events\n- `action-click` – Fired when the primary action button is clicked.\n- `action2-click` – Fired when the secondary action button is clicked.\n- `dismiss-click` – Fired when the advice message is dismissed (e.g., close icon or auto-hide).\n\n## Best Practices\n- Use concise, actionable advice text to maximize clarity.\n- Limit to one or two actions to avoid overwhelming the user.\n- For longer advice, use the `multiLine` line type to improve readability.\n- Only use the secondary action for supplementary or \"undo\" actions.\n- Ensure advice messages do not overlap or stack excessively; only one should be visible at a time if possible.\n\n## Example:\n```html\n<obc-advice-floating-item type=\"application\" direction=\"vertical\" hasTimestamp action>\n  <div slot=\"primary-icon\"><obi-placeholder></obi-placeholder></div>\n  <span slot=\"title\">Advice title</span>\n  <span slot=\"description\">An advice message with meaningful content for the user.</span>\n  <span slot=\"time\">09:12:46</span>\n  <span slot=\"action\">Close</span>\n</obc-advice-floating-item>\n```",
           "name": "ObcAdviceFloatingItem",
           "slots": [
             {
-              "description": "Main advice icon (default: `<obi-notification-advice-active>`), or custom icon.",
+              "description": "Custom main icon, projected into the child only when `type=\"application\"` (the built-in advice icon is used otherwise).",
               "name": "primary-icon"
             },
-            {
-              "description": "Additional icon for application-type advice messages.",
-              "name": "secondary-icon"
-            },
             {
               "description": "Title or heading of the advice message.",
               "name": "title"
@@ -40492,44 +40604,12 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-advice-message-item>` – A compact, actionable message component for displaying system advice, recommendations, or notifications.\n\nThis component presents a brief advice or recommendation message, optionally with a title, description, timestamp(s), and action(s). It is designed for use in notification panels, topbars, or summary lists where users need to quickly review and act on advice items. The component supports several display variants, including simple messages, messages with action buttons, and inactive/empty states.\n\n---\n\n### Features\n- **Display Types:**\n  - `simple`: Standard advice message with optional title, description, and timestamp.\n  - `with-button`: Includes a text action button (label set via `actionLabel`).\n  - `with-icon-button`: Shows an icon button for quick actions (e.g., dismiss or close).\n  - `inactive`: Indicates an empty or inactive state, typically used when there are no active advice messages.\n- **Size Variants:**\n  - `regular`: Default compact layout.\n  - `tall`: Provides a larger, more spacious layout for increased content or emphasis.\n- **Content Options:**\n  - Title and description can be shown or hidden independently.\n  - Supports one or two timestamps (primary and secondary) for time or duration display.\n  - Optional secondary icon overlay for additional status or categorization.\n  - Customizable empty state text for when no advice is present.\n- **Actions:**\n  - Text action button (with customizable label) or icon button, depending on type.\n  - Clickable message area for additional interactions.\n- **Accessibility & Responsiveness:**\n  - Truncates long titles/descriptions with ellipsis for readability.\n  - Layout adapts to size variant and content presence.\n\n---\n\n### Usage Guidelines\nUse `<obc-advice-message-item>` to present actionable advice, recommendations, or notifications that require user attention or review. Ideal for notification panels, summary lists, or topbars where users may need to quickly scan and act on advice items. Choose the `with-button` or `with-icon-button` types when an immediate action (such as \"View\", \"Acknowledge\", or \"Dismiss\") is needed. Use the `inactive` type (or set `empty` to true) to indicate that there are currently no active advice messages.\n\n- For persistent or critical alerts, consider using a dedicated alert/banner component.\n- For simple, informational messages without actions, use the `simple` type.\n- Use the `tall` size for layouts where more space is available or when emphasizing the advice.\n- The secondary icon slot can be used to indicate priority, category, or additional status.\n\n**TODO(designer):** Confirm if there are recommended icon choices or color conventions for different advice types, and if there are character limits for title/description.\n\n---\n\n### Slots\n| Slot Name         | Renders When...                                 | Purpose                                                      |\n|-------------------|------------------------------------------------|--------------------------------------------------------------|\n| `primary-icon`    | Always                                          | Main icon representing the advice (default: advice icon).    |\n| `secondary-icon`  | `hasSecondaryIcon` is true                     | Optional overlay icon for additional status or category.      |\n| `title`           | `hasTitle` is true and `title` is set          | Title or heading of the advice message.                      |\n| `description`     | `hasDescription` is true and `description` set | Detailed message text.                                       |\n| `time`            | `hasTimestamp` is true and `time` is set       | Primary timestamp (e.g., time of advice).                    |\n| `time-secondary`  | `hasTimestamp2` is true and `timeSecondary` set| Secondary timestamp (e.g., duration, relative time).         |\n| `action-text`     | `type=\"with-button\"`                           | Label for the primary action button.                         |\n| `action-icon`     | `type=\"with-icon-button\"`                      | Icon for the action button (default: close icon).            |\n| `empty`           | `type=\"inactive\"` or `empty` is true           | Text to display in the empty/inactive state.                 |\n\n---\n\n### Events\n- `message-click` – Fired when the main message area is clicked.\n- `action-click` – Fired when the action button (text or icon) is clicked.\n\n---\n\n### Best Practices & Constraints\n- Only one action (text or icon) is shown at a time, depending on the `type`.\n- Use concise titles and descriptions for optimal readability; long content will be truncated.\n- The `large` and `empty` properties are deprecated; use `size=\"tall\"` and `type=\"inactive\"` instead.\n- For accessibility, ensure action labels are descriptive and icons have appropriate meaning.\n\n---\n\n**Example:**\n```html\n<obc-advice-message-item\n  title=\"System Recommendation\"\n  description=\"Your system performance can be improved\"\n  time=\"10:30:15\"\n  type=\"with-button\"\n  actionLabel=\"View\"\n>\n</obc-advice-message-item>\n```\n\nIn this example, the advice message displays a title, description, timestamp, and a \"View\" action button.",
+          "description": "`<obc-advice-message-item>` – A compact, actionable message component for displaying system advice, recommendations, or notifications.\n\nThis component presents a brief advice or recommendation message, optionally with a title, description, timestamp(s), and action(s). It is designed for use in notification panels, topbars, or summary lists where users need to quickly review and act on advice items. The component supports several display variants, including simple messages, messages with action buttons, and inactive/empty states.\n\n---\n\n### Features\n- **Display Types:**\n  - `simple`: Standard advice message with optional title, description, and timestamp.\n  - `with-button`: Includes a text action button (label set via `actionLabel`).\n  - `with-icon-button`: Shows an icon button for quick actions (e.g., dismiss or close).\n  - `inactive`: Indicates an empty or inactive state, typically used when there are no active advice messages.\n- **Size Variants:**\n  - `regular`: Default compact layout.\n  - `tall`: Provides a larger, more spacious layout for increased content or emphasis.\n- **Content Options:**\n  - Title and description can be shown or hidden independently.\n  - Supports one or two timestamps (primary and secondary) for time or duration display.\n  - Optional secondary icon overlay for additional status or categorization.\n  - Customizable empty state text for when no advice is present.\n- **Actions:**\n  - Text action button (with customizable label) or icon button, depending on type.\n  - Clickable message area for additional interactions.\n- **Accessibility & Responsiveness:**\n  - Truncates long titles/descriptions with ellipsis for readability.\n  - Layout adapts to size variant and content presence.\n\n---\n\n### Usage Guidelines\nUse `<obc-advice-message-item>` to present actionable advice, recommendations, or notifications that require user attention or review. Ideal for notification panels, summary lists, or topbars where users may need to quickly scan and act on advice items. Choose the `with-button` or `with-icon-button` types when an immediate action (such as \"View\", \"Acknowledge\", or \"Dismiss\") is needed. Use the `inactive` type (or set `empty` to true) to indicate that there are currently no active advice messages.\n\n- For persistent or critical alerts, consider using a dedicated alert/banner component.\n- For simple, informational messages without actions, use the `simple` type.\n- Use the `tall` size for layouts where more space is available or when emphasizing the advice.\n- The secondary icon slot can be used to indicate priority, category, or additional status.\n\n**TODO(designer):** Confirm if there are recommended icon choices or color conventions for different advice types, and if there are character limits for title/description.\n\n---\n\n### Slots\n| Slot Name         | Renders When...            | Purpose                                                  |\n|-------------------|----------------------------|----------------------------------------------------------|\n| `secondary-icon`  | `hasSecondaryIcon` is true | Optional overlay icon for additional status or category. |\n\nAll other content (title, description, timestamps, action label/icon, empty-state\ntext) is driven by properties and rendered internally; it is not exposed as slots.\n\n---\n\n### Events\n- `message-click` – Fired when the main message area is clicked.\n- `action-click` – Fired when the action button (text or icon) is clicked.\n\n---\n\n### Best Practices & Constraints\n- Only one action (text or icon) is shown at a time, depending on the `type`.\n- Use concise titles and descriptions for optimal readability; long content will be truncated.\n- The `large` and `empty` properties are deprecated; use `size=\"tall\"` and `type=\"inactive\"` instead.\n- For accessibility, ensure action labels are descriptive and icons have appropriate meaning.\n\n---\n\n**Example:**\n```html\n<obc-advice-message-item\n  title=\"System Recommendation\"\n  description=\"Your system performance can be improved\"\n  time=\"10:30:15\"\n  type=\"with-button\"\n  actionLabel=\"View\"\n>\n</obc-advice-message-item>\n```\n\nIn this example, the advice message displays a title, description, timestamp, and a \"View\" action button.",
           "name": "ObcAdviceMessageItem",
           "slots": [
-            {
-              "description": "Main icon representing the advice (always present)",
-              "name": "primary-icon"
-            },
             {
               "description": "Optional overlay icon for additional status/category (shown when `hasSecondaryIcon` is true)",
               "name": "secondary-icon"
-            },
-            {
-              "description": "Title or heading of the advice (shown when `hasTitle` is true)",
-              "name": "title"
-            },
-            {
-              "description": "Detailed message text (shown when `hasDescription` is true)",
-              "name": "description"
-            },
-            {
-              "description": "Primary timestamp (shown when `hasTimestamp` is true)",
-              "name": "time"
-            },
-            {
-              "description": "Secondary timestamp (shown when `hasTimestamp2` is true)",
-              "name": "time-secondary"
-            },
-            {
-              "description": "Label for the action button (when `type=\"with-button\"`)",
-              "name": "action-text"
-            },
-            {
-              "description": "Icon for the action button (when `type=\"with-icon-button\"`)",
-              "name": "action-icon"
-            },
-            {
-              "description": "Text to display in the empty/inactive state (when `type=\"inactive\"` or `empty` is true)",
-              "name": "empty"
             }
           ],
           "members": [
@@ -41103,8 +41183,38 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "",
+          "description": "`<obc-alert-floating-item>` – A floating alert message that overlays the interface with a built-in alert icon.",
           "name": "ObcAlertFloatingItem",
+          "slots": [
+            {
+              "description": "Custom main icon, projected into the child only when `type=\"application\"` (the built-in alert icon is used otherwise).",
+              "name": "primary-icon"
+            },
+            {
+              "description": "Title or heading of the alert message.",
+              "name": "title"
+            },
+            {
+              "description": "Detailed message text.",
+              "name": "description"
+            },
+            {
+              "description": "Timestamp label (e.g., \"09:12:46\").",
+              "name": "time"
+            },
+            {
+              "description": "Day label (e.g., \"Yesterday\").",
+              "name": "day"
+            },
+            {
+              "description": "Primary action button label/content.",
+              "name": "action"
+            },
+            {
+              "description": "Secondary action button label/content.",
+              "name": "action2"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -41163,19 +41273,22 @@
               "name": "action-click",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} When the primary action button is clicked."
             },
             {
               "name": "action2-click",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} When the secondary action button is clicked."
             },
             {
               "name": "dismiss-click",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} When the alert message is dismissed."
             }
           ],
           "attributes": [
@@ -41925,13 +42038,21 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-alert-menu-item>` – A list item component for displaying alert or notification entries with status, icons, and action controls.\n\nPresents a concise summary of an alert or message, including status, title, description, and optional icons. Designed for use in alert menus, notification drawers, or similar lists where users need to review and acknowledge alerts efficiently.\n\n### Features\n- **Status Variants:** Supports multiple alert states via the `status` property:\n  - **Unacknowledged:** Shows an action button (ACK) for user acknowledgment.\n  - **Caution, Acknowledged, Rectified:** Display different visual cues for alert progression.\n  - **NoAckAlarm / NoAckWarning:** Show special icons indicating unacknowledged alarms or warnings.\n- **Icon Support:** Optional secondary icon (e.g., system or source) and a primary alert icon. Tertiary \"shelved\" icon appears if the alert is shelved.\n- **Time and Day Display:** Optionally shows day and/or time for the alert occurrence.\n- **Expandable:** Can be toggled open/closed for additional details (via click).\n- **Action Buttons:** Displays an \"ACK\" button for unacknowledged alerts and an optional secondary action (label set via `secondaryActionLabel`); each triggers an event when clicked.\n  - Each action's appearance is controlled independently via `primaryActionState` / `secondaryActionState` (`enabled`, `disabled`, or `none`).\n- **Animated Intro:** Optional animation when the item appears.\n- **Size Options:** Supports single-line or multi-line layouts (see `size` property).\n\n### Usage Guidelines\nUse `obc-alert-menu-item` to represent individual alerts or notifications in a menu, list, or notification center. Ideal for scenarios where users need to quickly scan, identify, and acknowledge alerts. The component is best suited for transient or actionable notifications rather than persistent banners.\n\n- Use the `status` property to reflect the current state of the alert.\n- Provide a relevant icon in the `alert-icon` slot to visually indicate the alert type.\n- Use the `icon` slot for a source/system icon if needed.\n- Only show the \"ACK\" action for alerts that require acknowledgment.\n- Provide `secondaryActionLabel` to add a second action alongside ACK.\n- Use `primaryActionState` / `secondaryActionState` to temporarily disable an action (`disabled`) or remove it without leaving a gap (`none`).\n- Use the `shelved` property to indicate alerts that are temporarily deferred.\n\n### Slots\n| Slot Name     | Renders When...                | Purpose                                              |\n|---------------|-------------------------------|------------------------------------------------------|\n| alert-icon    | Always                        | Main alert icon representing the alert type.         |\n| icon          | If `hasIcon` is true          | Secondary icon (e.g., system/source of alert).       |\n\n### Events\n- **ack-click** – Fired when the ACK action button is clicked.\n- **ack-secondary-click** – Fired when the secondary action button is clicked.\n- **item-click** – Fired when the alert menu item is clicked (toggles open/closed).\n\n### Best Practices\n- Only display the ACK action for alerts that require acknowledgment.\n- Use concise titles and descriptions for quick scanning.\n- For grouped alerts, ensure each item has a unique status and icon as appropriate.\n- Avoid overloading with too many icons; use secondary and tertiary icons only when necessary.\n- Follow standard notification design guidelines: keep actionable items prominent, and use color/iconography to indicate severity or status.\n\n**Example:**\n```\n<obc-alert-menu-item\n  status=\"unacknowledged\"\n  title=\"Engine Temperature High\"\n  description=\"Port main engine temperature exceeds normal operating range\"\n  time=\"14:30\"\n  hasIcon\n>\n  <obc-alert-icon slot=\"alert-icon\" type=\"alarm\" active></obc-alert-icon>\n  <obi-engine slot=\"icon\"></obi-engine>\n</obc-alert-menu-item>\n```",
+          "description": "`<obc-alert-menu-item>` – A list item component for displaying alert or notification entries with status, icons, and action controls.\n\nPresents a concise summary of an alert or message, including status, title, description, and optional icons. Designed for use in alert menus, notification drawers, or similar lists where users need to review and acknowledge alerts efficiently.\n\n### Features\n- **Status Variants:** Supports multiple alert states via the `status` property:\n  - **Unacknowledged:** Shows an action button (ACK) for user acknowledgment.\n  - **Caution, Acknowledged, Rectified:** Display different visual cues for alert progression.\n  - **NoAckAlarm / NoAckWarning:** Show special icons indicating unacknowledged alarms or warnings.\n- **Icon Support:** Optional secondary icon (e.g., system or source) and a primary alert icon. Tertiary \"shelved\" icon appears if the alert is shelved.\n- **Time and Day Display:** Optionally shows day and/or time for the alert occurrence.\n- **Expandable:** Can be toggled open/closed for additional details (via click).\n- **Action Buttons:** Displays an \"ACK\" button for unacknowledged alerts and an optional secondary action (label set via `secondaryActionLabel`); each triggers an event when clicked.\n  - Each action's appearance is controlled independently via `primaryActionState` / `secondaryActionState` (`enabled`, `disabled`, or `none`).\n- **Animated Intro:** Optional animation when the item appears.\n- **Size Options:** Supports single-line or multi-line layouts (see `size` property).\n\n### Usage Guidelines\nUse `obc-alert-menu-item` to represent individual alerts or notifications in a menu, list, or notification center. Ideal for scenarios where users need to quickly scan, identify, and acknowledge alerts. The component is best suited for transient or actionable notifications rather than persistent banners.\n\n- Use the `status` property to reflect the current state of the alert.\n- Provide a relevant icon in the `alert-icon` slot to visually indicate the alert type.\n- Use the `icon` slot for a source/system icon if needed.\n- Only show the \"ACK\" action for alerts that require acknowledgment.\n- Provide `secondaryActionLabel` to add a second action alongside ACK.\n- Use `primaryActionState` / `secondaryActionState` to temporarily disable an action (`disabled`) or remove it without leaving a gap (`none`).\n- Use the `shelved` property to indicate alerts that are temporarily deferred.\n\n### Slots\n| Slot Name     | Renders When...                | Purpose                                              |\n|---------------|-------------------------------|------------------------------------------------------|\n| alert-icon    | Always                        | Main alert icon representing the alert type.         |\n| title         | Always                        | Title content; falls back to the `title` property.   |\n| description   | Always                        | Description content; falls back to the `description` property. |\n| icon          | If `hasIcon` is true          | Secondary icon (e.g., system/source of alert).       |\n\n### Events\n- **ack-click** – Fired when the ACK action button is clicked.\n- **ack-secondary-click** – Fired when the secondary action button is clicked.\n- **item-click** – Fired when the alert menu item is clicked (toggles open/closed).\n\n### Best Practices\n- Only display the ACK action for alerts that require acknowledgment.\n- Use concise titles and descriptions for quick scanning.\n- For grouped alerts, ensure each item has a unique status and icon as appropriate.\n- Avoid overloading with too many icons; use secondary and tertiary icons only when necessary.\n- Follow standard notification design guidelines: keep actionable items prominent, and use color/iconography to indicate severity or status.\n\n**Example:**\n```\n<obc-alert-menu-item\n  status=\"unacknowledged\"\n  title=\"Engine Temperature High\"\n  description=\"Port main engine temperature exceeds normal operating range\"\n  time=\"14:30\"\n  hasIcon\n>\n  <obc-alert-icon slot=\"alert-icon\" type=\"alarm\" active></obc-alert-icon>\n  <obi-engine slot=\"icon\"></obi-engine>\n</obc-alert-menu-item>\n```",
           "name": "ObcAlertMenuItem",
           "slots": [
             {
               "description": "The main alert icon representing the alert type.",
               "name": "alert-icon"
             },
+            {
+              "description": "Title content; falls back to the `title` property when empty.",
+              "name": "title"
+            },
+            {
+              "description": "Description content; falls back to the `description` property when empty.",
+              "name": "description"
+            },
             {
               "description": "Optional secondary icon (e.g., source/system).",
               "name": "icon"
@@ -42277,7 +42398,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-alert-menu>` – A tabbed alert summary panel for displaying, acknowledging, and managing active alerts.\n\nProvides a compact, interactive menu for reviewing current alerts, grouped by status (e.g., unacknowledged, active, shelved). Users can acknowledge visible alerts, silence notifications, or navigate to a full alert list. Designed for quick triage and management of alert items in a sidebar or overlay context.\n\n### Features\n- **Tabbed organization:** Switch between \"Unacked\", \"Active\", and (optionally) \"Shelved\" tabs for focused alert review.\n- **Alert filtering:** Each tab displays only relevant alerts (e.g., \"Unacked\" shows only unacknowledged, non-shelved items).\n- **Bulk actions:** \"ACK visible\" button allows acknowledging all currently visible (filtered) alerts at once.\n- **Silence and navigation:** Dedicated buttons to silence alerts or jump to the full alert list.\n- **Dynamic content:** Supports any number of `<obc-alert-menu-item>` children, with automatic empty-state messaging and icons per tab.\n- **Responsive layout:** Adapts to available space, with scrollable alert lists and sticky action bar.\n- **Customizable:** Optionally show/hide the \"Shelved\" tab via `hasShelved` property; enable/disable bulk ACK via `canAckAll`.\n\n### Usage Guidelines\nUse `<obc-alert-menu>` to provide users with a focused, actionable summary of current alerts, typically in a sidebar, overlay, or dashboard context. Ideal for scenarios where users need to quickly review, acknowledge, or silence multiple alerts without leaving their current workflow. Avoid using for persistent, always-visible alert banners; for that, use a dedicated alert banner or notification system.\n\n- Place one or more `<obc-alert-menu-item>` elements as children to populate the alert list.\n- Use the `hasShelved` property to enable the \"Shelved\" tab if your application supports alert shelving.\n- Use the `canAckAll` property to control whether the \"ACK visible\" button is enabled (e.g., only when there are unacknowledged alerts in view).\n- Listen for custom events (`ack-all-visible-click`, `silence-click`, `go-to-alert-list-click`) to handle user actions.\n\n**TODO(designer):** Confirm if there are recommended maximum numbers of alerts to display, or if there are best practices for when to use the \"Shelved\" tab.\n\n### Slots\n\n| Slot Name                        | Renders When...                  | Purpose                                                        |\n|----------------------------------|----------------------------------|----------------------------------------------------------------|\n| (default)                        | Always                           | Place one or more `<obc-alert-menu-item>` elements as alert rows. |\n| empty-unacked-title              | Unacked tab, when empty          | Custom title for empty unacknowledged alerts.                  |\n| empty-unacked-description        | Unacked tab, when empty          | Custom description for empty unacknowledged alerts.            |\n| empty-unacked-icon               | Unacked tab, when empty          | Custom icon for empty unacknowledged alerts.                   |\n| empty-all-title                  | Active tab, when empty    | Custom title for empty active alerts.                          |\n| empty-all-description            | Active tab, when empty    | Custom description for empty active alerts.                    |\n| empty-all-icon                   | Active tab, when empty    | Custom icon for empty active alerts.                           |\n| empty-shelved-title              | Shelved tab, when empty          | Custom title for empty shelved alerts.                         |\n| empty-shelved-description        | Shelved tab, when empty          | Custom description for empty shelved alerts.                   |\n| empty-shelved-icon               | Shelved tab, when empty          | Custom icon for empty shelved alerts.                          |\n\n### Properties\n- `hasShelved` (boolean): If true, displays the \"Shelved\" tab and enables shelving support. Default: false.\n- `canAckAll` (boolean): If true, enables the \"ACK visible\" button for bulk acknowledgment. Default: false.\n- `showSilenceButton` (boolean): If true, shows the \"Silence\" button. Default: true.\n- `showAlertListButton` (boolean): If true, shows the \"Alerts\" navigation button. Default: true.\n\n### Events\n- **ack-all-visible-click** – Fired when the \"ACK visible\" button is clicked. The event detail includes the list of visible alert elements and the current tab name.\n- **alert-list-click** – Fired when the \"Alerts\" navigation button is clicked.\n- **silence-click** – Fired when the \"Silence\" button is clicked.\n- **go-to-alert-list-click** – Fired when the \"Alerts\" navigation button is clicked.\n\n### Best Practices and Constraints\n- Only enable \"ACK visible\" when there are actionable, unacknowledged alerts in the current view.\n- Use the \"Shelved\" tab only if your application supports shelving alerts; otherwise, omit it for simplicity.\n- For accessibility, ensure that all alert items and action buttons are keyboard navigable.\n- Do not use this component for persistent, always-on-screen alerts; use banners or dialogs for critical, persistent notifications.\n\n### Example\n```\n<obc-alert-menu hasShelved canAckAll>\n  <obc-alert-menu-item active hasTime>\n    <obi-placeholder slot=\"alert-icon\"></obi-placeholder>\n    <span slot=\"title\">Engine Overheat</span>\n    <span slot=\"description\">Main engine temperature exceeds threshold</span>\n    <span slot=\"time\">09:12:34</span>\n  </obc-alert-menu-item>\n  <!-- More alert items... -->\n</obc-alert-menu>\n```",
+          "description": "`<obc-alert-menu>` – A tabbed alert summary panel for displaying, acknowledging, and managing active alerts.\n\nProvides a compact, interactive menu for reviewing current alerts, grouped by status (e.g., unacknowledged, active, shelved). Users can acknowledge visible alerts, silence notifications, or navigate to a full alert list. Designed for quick triage and management of alert items in a sidebar or overlay context.\n\n### Features\n- **Tabbed organization:** Switch between \"Unacked\", \"Active\", and (optionally) \"Shelved\" tabs for focused alert review.\n- **Alert filtering:** Each tab displays only relevant alerts (e.g., \"Unacked\" shows only unacknowledged, non-shelved items).\n- **Bulk actions:** \"ACK visible\" button allows acknowledging all currently visible (filtered) alerts at once.\n- **Silence and navigation:** Dedicated buttons to silence alerts or jump to the full alert list.\n- **Dynamic content:** Supports any number of `<obc-alert-menu-item>` children, with automatic empty-state messaging and icons per tab.\n- **Responsive layout:** Adapts to available space, with scrollable alert lists and sticky action bar.\n- **Customizable:** Optionally show/hide the \"Shelved\" tab via `hasShelved` property; enable/disable bulk ACK via `canAckAll`.\n\n### Usage Guidelines\nUse `<obc-alert-menu>` to provide users with a focused, actionable summary of current alerts, typically in a sidebar, overlay, or dashboard context. Ideal for scenarios where users need to quickly review, acknowledge, or silence multiple alerts without leaving their current workflow. Avoid using for persistent, always-visible alert banners; for that, use a dedicated alert banner or notification system.\n\n- Place one or more `<obc-alert-menu-item>` elements as children to populate the alert list.\n- Use the `hasShelved` property to enable the \"Shelved\" tab if your application supports alert shelving.\n- Use the `canAckAll` property to control whether the \"ACK visible\" button is enabled (e.g., only when there are unacknowledged alerts in view).\n- Listen for custom events (`ack-all-visible-click`, `silence-click`, `go-to-alert-list-click`) to handle user actions.\n\n**TODO(designer):** Confirm if there are recommended maximum numbers of alerts to display, or if there are best practices for when to use the \"Shelved\" tab.\n\n### Slots\n\n| Slot Name                        | Renders When...                  | Purpose                                                        |\n|----------------------------------|----------------------------------|----------------------------------------------------------------|\n| (default)                        | Always                           | Place one or more `<obc-alert-menu-item>` elements as alert rows. |\n| empty-<tab>-title                | Selected tab is empty            | Custom title for the empty state (`<tab>` is one of `unacked`, `all`, `shelved`). |\n| empty-<tab>-description          | Selected tab is empty            | Custom description for the empty state (`<tab>` is one of `unacked`, `all`, `shelved`). |\n| empty-<tab>-icon                 | Selected tab is empty            | Custom icon for the empty state (`<tab>` is one of `unacked`, `all`, `shelved`). |\n\n### Properties\n- `hasShelved` (boolean): If true, displays the \"Shelved\" tab and enables shelving support. Default: false.\n- `canAckAll` (boolean): If true, enables the \"ACK visible\" button for bulk acknowledgment. Default: false.\n- `showSilenceButton` (boolean): If true, shows the \"Silence\" button. Default: true.\n- `showAlertListButton` (boolean): If true, shows the \"Alerts\" navigation button. Default: true.\n\n### Events\n- **ack-all-visible-click** – Fired when the \"ACK visible\" button is clicked. The event detail includes the list of visible alert elements and the current tab name.\n- **silence-click** – Fired when the \"Silence\" button is clicked.\n- **go-to-alert-list-click** – Fired when the \"Alerts\" navigation button is clicked.\n\n### Best Practices and Constraints\n- Only enable \"ACK visible\" when there are actionable, unacknowledged alerts in the current view.\n- Use the \"Shelved\" tab only if your application supports shelving alerts; otherwise, omit it for simplicity.\n- For accessibility, ensure that all alert items and action buttons are keyboard navigable.\n- Do not use this component for persistent, always-on-screen alerts; use banners or dialogs for critical, persistent notifications.\n\n### Example\n```\n<obc-alert-menu hasShelved canAckAll>\n  <obc-alert-menu-item active hasTime>\n    <obi-placeholder slot=\"alert-icon\"></obi-placeholder>\n    <span slot=\"title\">Engine Overheat</span>\n    <span slot=\"description\">Main engine temperature exceeds threshold</span>\n    <span slot=\"time\">09:12:34</span>\n  </obc-alert-menu-item>\n  <!-- More alert items... -->\n</obc-alert-menu>\n```",
           "name": "ObcAlertMenu",
           "slots": [
             {
@@ -42285,40 +42406,16 @@
               "name": ""
             },
             {
-              "description": "Custom title for empty unacknowledged alerts (Unacked tab)",
-              "name": "empty-unacked-title"
-            },
-            {
-              "description": "Custom description for empty unacknowledged alerts (Unacked tab)",
-              "name": "empty-unacked-description"
-            },
-            {
-              "description": "Custom icon for empty unacknowledged alerts (Unacked tab)",
-              "name": "empty-unacked-icon"
-            },
-            {
-              "description": "Custom title for empty active alerts (Active tab)",
-              "name": "empty-all-title"
-            },
-            {
-              "description": "Custom description for empty active alerts (Active tab)",
-              "name": "empty-all-description"
-            },
-            {
-              "description": "Custom icon for empty active alerts (Active tab)",
-              "name": "empty-all-icon"
-            },
-            {
-              "description": "Custom title for empty shelved alerts (Shelved tab)",
-              "name": "empty-shelved-title"
+              "description": "Custom empty-state title for the selected tab (`<tab>` is one of `unacked`, `all`, `shelved`)",
+              "name": "empty-<tab>-title"
             },
             {
-              "description": "Custom description for empty shelved alerts (Shelved tab)",
-              "name": "empty-shelved-description"
+              "description": "Custom empty-state description for the selected tab (`<tab>` is one of `unacked`, `all`, `shelved`)",
+              "name": "empty-<tab>-description"
             },
             {
-              "description": "Custom icon for empty shelved alerts (Shelved tab)",
-              "name": "empty-shelved-icon"
+              "description": "Custom empty-state icon for the selected tab (`<tab>` is one of `unacked`, `all`, `shelved`)",
+              "name": "empty-<tab>-icon"
             }
           ],
           "members": [
@@ -42422,10 +42519,6 @@
                 "text": "CustomEvent"
               },
               "description": "{CustomEvent} - Fired when the go to alert list button is clicked"
-            },
-            {
-              "description": "{CustomEvent} - Fired when the alert list button is clicked",
-              "name": "alert-list-click"
             }
           ],
           "attributes": [
@@ -45286,8 +45379,14 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "",
+          "description": "`<obc-chat-message>` – A single chat message bubble with optional name and date header.",
           "name": "ObcChatMessage",
+          "slots": [
+            {
+              "description": "The message content (body of the chat bubble).",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -48128,18 +48227,8 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-elevated-card-radio>` – A single radio button presented within an elevated card container for visually distinct selection in a group.\n\nThis component combines a radio input with an elevated card layout, making each option in a set more prominent and easier to scan. It is ideal for scenarios where radio choices need to be visually separated or require additional emphasis compared to standard radio groups.\n\n---\n\n### Features\n- **Elevated Card Presentation:** Each radio option is wrapped in an elevated card, improving clarity and touch target size.\n- **Integrated Radio Button:** Uses an underlying `<obc-radio>` for native group behavior and accessibility.\n- **Customizable Appearance:** Supports `position` (layout), `size`, `graphicBorder`, and `border` for visual adjustments.\n- **Label Support:** Displays a label next to the radio for clear identification.\n- **Disabled and Required States:** Can be disabled or marked as required for form validation.\n- **Light DOM Rendering:** Renders in the light DOM to allow native radio grouping via the `name` property.\n\n---\n\n### Usage Guidelines\nUse `obc-elevated-card-radio` when you want to present a set of mutually exclusive options with greater visual separation than standard radio buttons. This is especially useful in forms or settings panels where choices should stand out or be easily tappable.\n\n- Group multiple `obc-elevated-card-radio` components with the same `name` property to create a radio group.\n- Prefer this component over plain radios when you need a more prominent or card-like selection UI.\n- For simple, inline choices, use a standard `<obc-radio>` instead.\n- **TODO(designer):** Confirm if there are recommended use cases or design constraints for when to use the card radio versus other selection controls.\n\n---\n\n### Slots\n| Slot Name     | Renders When... | Purpose                                 |\n|-------------- |-----------------|-----------------------------------------|\n| leading-icon  | Always          | Contains the radio button itself.       |\n| label         | Always          | Displays the label text for the option. |\n\n---\n\n### Properties and Attributes\n- `position`: Controls the card's layout position (default: Regular).\n- `size`: Sets the card size (default: SingleLine).\n- `graphicBorder`/`border`: Toggles visual borders on the card.\n- `name`: Groups radios for mutual exclusivity (must match across group).\n- `value`: The value submitted when this radio is selected.\n- `label`: Text label shown next to the radio.\n- `checked`: Whether this radio is selected.\n- `disabled`: Disables the radio and card interaction.\n- `required`: Marks the radio as required for form validation.\n\n---\n\n### Best Practices\n- Ensure all radios in a group share the same `name` for correct selection behavior.\n- Only one radio in a group should be `checked` at a time.\n- Use concise, descriptive labels for each option.\n- For accessibility, labels are linked to their radio via the `for` and `inputId` attributes.\n\n---\n\n### Example:\n```html\n<obc-elevated-card-radio\n  name=\"choices\"\n  value=\"option1\"\n  label=\"Option 1\"\n  ?checked=${true}\n></obc-elevated-card-radio>\n<obc-elevated-card-radio\n  name=\"choices\"\n  value=\"option2\"\n  label=\"Option 2\"\n></obc-elevated-card-radio>\n```\nIn this example, two card radios form a group; only one can be selected at a time.",
+          "description": "`<obc-elevated-card-radio>` – A single radio button presented within an elevated card container for visually distinct selection in a group.\n\nThis component combines a radio input with an elevated card layout, making each option in a set more prominent and easier to scan. It is ideal for scenarios where radio choices need to be visually separated or require additional emphasis compared to standard radio groups.\n\n---\n\n### Features\n- **Elevated Card Presentation:** Each radio option is wrapped in an elevated card, improving clarity and touch target size.\n- **Integrated Radio Button:** Uses an underlying `<obc-radio>` for native group behavior and accessibility.\n- **Customizable Appearance:** Supports `position` (layout), `size`, `graphicBorder`, and `border` for visual adjustments.\n- **Label Support:** Displays a label next to the radio for clear identification.\n- **Disabled and Required States:** Can be disabled or marked as required for form validation.\n- **Light DOM Rendering:** Renders in the light DOM to allow native radio grouping via the `name` property.\n\n---\n\n### Usage Guidelines\nUse `obc-elevated-card-radio` when you want to present a set of mutually exclusive options with greater visual separation than standard radio buttons. This is especially useful in forms or settings panels where choices should stand out or be easily tappable.\n\n- Group multiple `obc-elevated-card-radio` components with the same `name` property to create a radio group.\n- Prefer this component over plain radios when you need a more prominent or card-like selection UI.\n- For simple, inline choices, use a standard `<obc-radio>` instead.\n- **TODO(designer):** Confirm if there are recommended use cases or design constraints for when to use the card radio versus other selection controls.\n\n---\n\n### Slots\nThis component exposes no slots. The radio input and its label are rendered\ninternally from the `label`, `value`, `checked`, and related properties.\n\n---\n\n### Properties and Attributes\n- `position`: Controls the card's layout position (default: Regular).\n- `size`: Sets the card size (default: SingleLine).\n- `graphicBorder`/`border`: Toggles visual borders on the card.\n- `name`: Groups radios for mutual exclusivity (must match across group).\n- `value`: The value submitted when this radio is selected.\n- `label`: Text label shown next to the radio.\n- `checked`: Whether this radio is selected.\n- `disabled`: Disables the radio and card interaction.\n- `required`: Marks the radio as required for form validation.\n\n---\n\n### Best Practices\n- Ensure all radios in a group share the same `name` for correct selection behavior.\n- Only one radio in a group should be `checked` at a time.\n- Use concise, descriptive labels for each option.\n- For accessibility, labels are linked to their radio via the `for` and `inputId` attributes.\n\n---\n\n### Example:\n```html\n<obc-elevated-card-radio\n  name=\"choices\"\n  value=\"option1\"\n  label=\"Option 1\"\n  ?checked=${true}\n></obc-elevated-card-radio>\n<obc-elevated-card-radio\n  name=\"choices\"\n  value=\"option2\"\n  label=\"Option 2\"\n></obc-elevated-card-radio>\n```\nIn this example, two card radios form a group; only one can be selected at a time.",
           "name": "ObcElevatedCardRadio",
-          "slots": [
-            {
-              "description": "Contains the radio button input.",
-              "name": "leading-icon"
-            },
-            {
-              "description": "Displays the label text for the radio option.",
-              "name": "label"
-            }
-          ],
           "members": [
             {
               "kind": "field",
@@ -51117,8 +51206,14 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "",
+          "description": "`<obc-keyboard-numeric>` – An on-screen numeric keyboard with optional calculation and symbol modes.",
           "name": "ObcKeyboardNumeric",
+          "slots": [
+            {
+              "description": "Custom leading icon shown inside the input field (rendered when `hasLeadingIcon` is true).",
+              "name": "leading-icon"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -51371,19 +51466,22 @@
               "name": "close-click",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent} Fired when the close button (or Escape) dismisses the keyboard."
             },
             {
               "name": "done-click",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent<{value: string}>} Fired when the DONE button (or Enter) is pressed."
             },
             {
               "name": "value-change",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "{CustomEvent<{value: string}>} Fired whenever the current value changes."
             }
           ],
           "attributes": [
@@ -53978,17 +54076,13 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-notification-floating-item>` – A floating notification message component for transient feedback, alerts, or status updates.\n\nDisplays a notification as an overlay above the main UI, typically used to inform users of events, actions, or system statuses without interrupting their workflow. This component is a specialized variant of a floating message (toast/snackbar) with notification-specific styling and iconography.\n\n### Features\n- **Variants (type):**\n  - `regular` (default): Standard notification appearance for general messages.\n  - `application`: Enhanced notification with an additional secondary icon, suitable for application-level or high-visibility messages.\n- **Layout Direction (direction):**\n  - `horizontal` (default): Content and actions are arranged side-by-side.\n  - `vertical`: Content and actions are stacked for narrow spaces or longer messages.\n- **Line Type (lineType):**\n  - `singleLine` (default): Compact, single-line layout for brief messages.\n  - `multiLine`: Supports longer, multi-line descriptions.\n- **Timestamp and Day Labels:**\n  - `hasTimestamp`: Displays a time label (e.g., \"09:12:46\") when enabled.\n  - `hasDay`: Displays a day label (e.g., \"Yesterday\") when enabled (requires `hasTimestamp`).\n- **Actions:**\n  - `action`: Shows a primary action button (e.g., \"Close\").\n  - `action2`: Shows a secondary action button (e.g., \"Undo\"). Only available if `action` is enabled.\n- **Icon Slots:**\n  - Customizable icons via slots, with a default notification icon provided.\n- **Event Handling:**\n  - Emits custom events for action and dismiss interactions.\n\n### Usage Guidelines\nUse `<obc-notification-floating-item>` for brief, transient notifications that inform users about non-critical events, confirmations, or status changes. Ideal for scenarios where feedback should be visible but not persistent, such as after completing an action or receiving a system update. Avoid using for critical or blocking alerts—use a dialog or alert banner for those cases.\n\n- Prefer the `application` type for notifications that require extra emphasis or represent application-wide events.\n- Use the `multiLine` layout for longer messages to maintain readability.\n- Only enable both actions if the secondary action is truly necessary (e.g., \"Undo\" alongside \"Close\").\n- For accessibility and clarity, keep notification messages concise.\n- By default, the notification does not auto-dismiss; manual dismissal or action is required.\n  **TODO(designer):** Confirm if auto-dismissal is recommended or supported for this component.\n\n**Related keywords:** notification, toast, snackbar, floating message, alert, status update, transient feedback.\n\n### Slots\n\n| Slot Name       | Renders When...               | Purpose                                                      |\n|-----------------|------------------------------|--------------------------------------------------------------|\n| primary-icon    | Always (all types)           | Main icon representing the notification category.            |\n| secondary-icon  | type=\"application\" only      | Additional icon for application-type notifications.          |\n| title           | Always                       | Title or heading of the notification.                        |\n| description     | Always                       | Detailed message text.                                       |\n| time            | hasTimestamp is true         | Timestamp label (e.g., \"09:12:46\").                          |\n| day             | hasTimestamp && hasDay       | Day label (e.g., \"Yesterday\").                               |\n| action          | action is true               | Label/content for the primary action button.                 |\n| action2         | action2 is true              | Label/content for the secondary action button.               |\n\n### Events\n- `action-click` – Fired when the primary action button is clicked.\n- `action2-click` – Fired when the secondary action button is clicked.\n- `dismiss-click` – Fired when the notification is dismissed (e.g., close icon or programmatically).\n\n### Example\n```html\n<obc-notification-floating-item\n  type=\"regular\"\n  direction=\"horizontal\"\n  hasTimestamp\n  action\n>\n  <obi-placeholder slot=\"primary-icon\"></obi-placeholder>\n  <span slot=\"title\">Notification title</span>\n  <span slot=\"description\">A notification message with meaningful content for the user.</span>\n  <span slot=\"time\">09:12:46</span>\n  <span slot=\"action\">Close</span>\n</obc-notification-floating-item>\n```",
+          "description": "`<obc-notification-floating-item>` – A floating notification message component for transient feedback, alerts, or status updates.\n\nDisplays a notification as an overlay above the main UI, typically used to inform users of events, actions, or system statuses without interrupting their workflow. This component is a specialized variant of a floating message (toast/snackbar) with notification-specific styling and iconography.\n\n### Features\n- **Variants (type):**\n  - `regular` (default): Standard notification appearance for general messages.\n  - `application`: Enhanced notification with an additional secondary icon, suitable for application-level or high-visibility messages.\n- **Layout Direction (direction):**\n  - `horizontal` (default): Content and actions are arranged side-by-side.\n  - `vertical`: Content and actions are stacked for narrow spaces or longer messages.\n- **Line Type (lineType):**\n  - `singleLine` (default): Compact, single-line layout for brief messages.\n  - `multiLine`: Supports longer, multi-line descriptions.\n- **Timestamp and Day Labels:**\n  - `hasTimestamp`: Displays a time label (e.g., \"09:12:46\") when enabled.\n  - `hasDay`: Displays a day label (e.g., \"Yesterday\") when enabled (requires `hasTimestamp`).\n- **Actions:**\n  - `action`: Shows a primary action button (e.g., \"Close\").\n  - `action2`: Shows a secondary action button (e.g., \"Undo\"). Only available if `action` is enabled.\n- **Icon Slots:**\n  - Customizable icons via slots, with a default notification icon provided.\n- **Event Handling:**\n  - Emits custom events for action and dismiss interactions.\n\n### Usage Guidelines\nUse `<obc-notification-floating-item>` for brief, transient notifications that inform users about non-critical events, confirmations, or status changes. Ideal for scenarios where feedback should be visible but not persistent, such as after completing an action or receiving a system update. Avoid using for critical or blocking alerts—use a dialog or alert banner for those cases.\n\n- Prefer the `application` type for notifications that require extra emphasis or represent application-wide events.\n- Use the `multiLine` layout for longer messages to maintain readability.\n- Only enable both actions if the secondary action is truly necessary (e.g., \"Undo\" alongside \"Close\").\n- For accessibility and clarity, keep notification messages concise.\n- By default, the notification does not auto-dismiss; manual dismissal or action is required.\n  **TODO(designer):** Confirm if auto-dismissal is recommended or supported for this component.\n\n**Related keywords:** notification, toast, snackbar, floating message, alert, status update, transient feedback.\n\n### Slots\n\n| Slot Name       | Renders When...               | Purpose                                                      |\n|-----------------|------------------------------|--------------------------------------------------------------|\n| primary-icon    | type=\"application\" only      | Custom main icon (the built-in notification icon is used otherwise). |\n| title           | Always                       | Title or heading of the notification.                        |\n| description     | Always                       | Detailed message text.                                       |\n| time            | hasTimestamp is true         | Timestamp label (e.g., \"09:12:46\").                          |\n| day             | hasTimestamp && hasDay       | Day label (e.g., \"Yesterday\").                               |\n| action          | action is true               | Label/content for the primary action button.                 |\n| action2         | action2 is true              | Label/content for the secondary action button.               |\n\n### Events\n- `action-click` – Fired when the primary action button is clicked.\n- `action2-click` – Fired when the secondary action button is clicked.\n- `dismiss-click` – Fired when the notification is dismissed (e.g., close icon or programmatically).\n\n### Example\n```html\n<obc-notification-floating-item\n  type=\"regular\"\n  direction=\"horizontal\"\n  hasTimestamp\n  action\n>\n  <obi-placeholder slot=\"primary-icon\"></obi-placeholder>\n  <span slot=\"title\">Notification title</span>\n  <span slot=\"description\">A notification message with meaningful content for the user.</span>\n  <span slot=\"time\">09:12:46</span>\n  <span slot=\"action\">Close</span>\n</obc-notification-floating-item>\n```",
           "name": "ObcNotificationFloatingItem",
           "slots": [
             {
-              "description": "Main icon representing the notification category.",
+              "description": "Custom main icon, projected into the child only when `type=\"application\"` (the built-in notification icon is used otherwise).",
               "name": "primary-icon"
             },
-            {
-              "description": "Additional icon for application-type notifications.",
-              "name": "secondary-icon"
-            },
             {
               "description": "Title or heading of the notification.",
               "name": "title"
@@ -57455,6 +57549,40 @@
           "kind": "class",
           "description": "`<obc-sequence-card>` - Timeline-style card with header, content, and progress indicator.\n\nOverview:\n- Combines a step indicator, header metadata, and optional content/actions.\n- Supports vertical and horizontal layouts with centered or left-side progress.\n- Use for timelines, process steps, and time-stamped events.\n\nFeatures and Variants:\n- Sizes: `regular`, `small`.\n- Progress layouts: `centered`, `left-side`.\n- Optional progress connector (`showConnector=false` to hide).\n- States: `active`, `flat`, `enhanced`.\n- Layouts: vertical, horizontal, or both.\n- Optional leading icon, timestamps, content, and actions.\n- Full width/height layout toggles.\n- Horizontal and vertical (default) layouts are supported.\n\nUsage Guidelines:\n- Keep titles short; use `subtitle` for secondary text.\n- Provide custom content via the default slot when `hasContent` is true.\n- Provide actions via the `actions` slot when `hasActions` is true.\n- Disable connectors for modal-style layouts that should not show continuation.\n\nSlots:\n- `leading-icon`: Icon before the title (shown when `hasLeadingIcon` is true).\n- `title`: Title text (fallbacks to `cardTitle`).\n- `subtitle`: Subtitle/description (fallbacks to `subtitle`).\n- `time-stamp`: Header timestamp (fallbacks to `timeLabel` + `time`).\n- `header-actions`: Optional header actions (e.g., close button).\n- `left-time-stamp`: Left rail timestamp (fallbacks to `leftTime`).\n- `actions`: Actions row content (shown when `hasActions` is true).\n- Default slot: Main content area (shown when `hasContent` is true).\n\nNotes:\n- `fullWidth` and `fullHeight` stretch the card to fill its container.\n- `indicatorTypeOverride`/`indicatorStyleOverride` force the step indicator\n  size/style when special layouts are needed.\n\nEvents:\n- None. Consumers define actions in slots and handle events on slotted elements.\n\nBest Practices:\n- Pair `left-side` progress with vertical layout for rail-based timelines.\n- Avoid mixing long text with dense action rows; use content slot instead.\n\nExample:\n```html\n<obc-sequence-card\n  size=\"regular\"\n  progressType=\"left-side\"\n  state=\"active\"\n  hasActions\n>\n  <span slot=\"title\">Title</span>\n  <span slot=\"subtitle\">Subtitle</span>\n  <div slot=\"actions\">...</div>\n  <!-- default slot: your content -->\n</obc-sequence-card>\n```\n\nKeywords: timeline, step, progress, sequence, card, event, status.",
           "name": "ObcSequenceCard",
+          "slots": [
+            {
+              "description": "Icon before the title (shown when `hasLeadingIcon` is true).",
+              "name": "leading-icon"
+            },
+            {
+              "description": "Title text (falls back to `cardTitle`).",
+              "name": "title"
+            },
+            {
+              "description": "Subtitle/description (falls back to `subtitle`).",
+              "name": "subtitle"
+            },
+            {
+              "description": "Header timestamp (falls back to `timeLabel` + `time`).",
+              "name": "time-stamp"
+            },
+            {
+              "description": "Optional header actions (e.g., close button).",
+              "name": "header-actions"
+            },
+            {
+              "description": "Left rail timestamp (falls back to `leftTime`).",
+              "name": "left-time-stamp"
+            },
+            {
+              "description": "Actions row content (shown when `hasActions` is true).",
+              "name": "actions"
+            },
+            {
+              "description": "Main content area (shown when `hasContent` is true).",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -58019,6 +58147,24 @@
           "kind": "class",
           "description": "`<obc-sequence-item>` renders the textual part of a sequence flow while\ncomposing `<obc-sequence-step>` for the visual indicator. Consumers can either\nconfigure the built-in step via `step*` props or supply a custom step through\nthe `step` slot.",
           "name": "ObcSequenceItem",
+          "slots": [
+            {
+              "description": "Title/subtitle block (falls back to the built-in `title`/`subtitle`/inline description).",
+              "name": "title"
+            },
+            {
+              "description": "Description text (rendered when `hasDescription` is true and not inlined).",
+              "name": "description"
+            },
+            {
+              "description": "Meta row with timestamp/distance stamps (rendered when `hasMeta` is true — i.e. `hasStamp` with a timestamp or distance stamp enabled).",
+              "name": "meta"
+            },
+            {
+              "description": "Custom step indicator (falls back to the built-in `<obc-sequence-step>`).",
+              "name": "step"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -58675,6 +58821,16 @@
           "kind": "class",
           "description": "`<obc-sequence-modal>` - Modal card with step indicator, title, content, and actions.\n\nOverview:\n- Presents a sequence step in a modal-style card with header metadata.\n- Supports regular and two-line title layouts.\n- Use for focused step/task dialogs with optional actions.\n\nFeatures and Variants:\n- Types: `regular`, `two-line`.\n- Optional timestamp and actions area.\n\nUsage Guidelines:\n- Use the `actions` slot for custom buttons.\n- Provide content via the default slot (no built-in placeholders).\n\nSlots:\n- `actions`: Actions row content (shown when `hasActions` is true).\n- Default slot: Main content area.\n\nEvents:\n- `close-click`: Fired when the close icon is clicked.\n\nBest Practices:\n- Keep titles short; use `subtitle` for additional context.\n- Prefer a single row of actions for compact layouts.\n\nExample:\n```html\n<obc-sequence-modal type=\"regular\" hasActions>\n  <div slot=\"actions\">...</div>\n  <!-- default slot: your content -->\n</obc-sequence-modal>\n```\n\nKeywords: modal, sequence, step, dialog, progress, actions.",
           "name": "ObcSequenceModal",
+          "slots": [
+            {
+              "description": "Actions row content (shown when `hasActions` is true).",
+              "name": "actions"
+            },
+            {
+              "description": "Main content area.",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -58776,6 +58932,12 @@
               "privacy": "private"
             }
           ],
+          "events": [
+            {
+              "description": "Fired when the close icon is clicked.",
+              "name": "close-click"
+            }
+          ],
           "attributes": [
             {
               "name": "type",
@@ -59621,17 +59783,9 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-slider-double>` – A dual-thumb range slider for selecting a value interval within a defined range.\n\nThis component allows users to select a minimum and maximum value by dragging two thumbs along a horizontal track. It is commonly used for filtering or specifying ranges (such as price, speed, or time intervals) in forms and dashboards. The slider supports both interactive and read-only display modes, as well as visual variants for different UI needs.\n\nAppears with two draggable handles (thumbs) and labels showing the current low and high values. Optionally, icons can be placed at each end of the slider via slots.\n\n## Features\n- **Dual-thumb range selection:** Users can adjust both the lower and upper bounds of a numeric interval.\n- **Variants:**\n  - **Normal:** Standard slider with compact styling.\n  - **Enhanced:** Larger track and thumb for increased prominence or touch accessibility.\n  - **NoInput:** Read-only mode; disables all user interaction and presents the current range as static.\n- **Configurable range:** Set minimum (`min`), maximum (`max`), and step size (`step`) for precise control.\n- **Step click adjustment:** Use `stepClick` to define increment/decrement amount for keyboard or button-based changes.\n- **Seeking mode:** Enable `allowSeeking` to let users jump to a value by clicking on the track, with smooth animated transitions controlled by `seekingSpeed`.\n- **Custom labels:** Display formatted value labels with unit (`labelUnit`), decimal precision (`labelDecimals`), and adjustable label width (`labelWidth`).\n- **Hug container option:** Remove spacing between slider and container edges with the `hugcontainer` attribute for seamless layout integration.\n- **Icon slots:** Add icons to the left and right ends of the slider using `icon-left` and `icon-right` slots.\n\n## Usage Guidelines\nUse `obc-slider-double` when you need users to specify a numeric range, such as filtering results by minimum and maximum values. Ideal for scenarios like:\n- Filtering items by price, speed, or other continuous values.\n- Selecting a time interval or threshold range.\n- Any UI where a bounded numeric interval is required.\n\nFor single-value selection, use a standard slider component instead. In read-only or summary views, use the `no-input` variant to display the selected range without allowing changes.\n\n**TODO(designer):** Confirm if there are recommended minimum thumb separation or constraints for usability, and if there are best practices for using the enhanced variant.\n\n## Slots\n\n| Slot Name     | Renders When...               | Purpose                                                                                                          |\n|---------------|-------------------------------|------------------------------------------------------------------------------------------------------------------|\n| icon-left     | Always                        | Icon or content at the left end of the slider. Example: `<obi-placeholder slot=\"icon-left\"></obi-placeholder>`   |\n| icon-right    | Always                        | Icon or content at the right end of the slider. Example: `<obi-placeholder slot=\"icon-right\"></obi-placeholder>` |\n| left-readout  | `showLeftReadout` is true     | Custom content for the left (low) readout label. Falls back to the formatted `low` value.                        |\n| right-readout | `showRightReadout` is true    | Custom content for the right (high) readout label. Falls back to the formatted `high` value.                     |\n\n## Properties and Attributes\n- `low` (number): The current lower bound of the selected range.\n- `high` (number): The current upper bound of the selected range.\n- `min` (number): The minimum allowed value (default: 0).\n- `max` (number): The maximum allowed value (default: 100).\n- `step` (number): The increment for value changes (default: 1).\n- `stepClick` (number): Step size for keyboard or button-based changes (default: 10).\n- `variant` (`normal` | `enhanced` | `no-input`): Visual and interaction style (default: `normal`).\n- `allowSeeking` (boolean): If true, clicking the track animates the thumb to the clicked position.\n- `seekingSpeed` (number): Animation speed for seeking (default: 1/3, i.e., full range in 3 seconds).\n- `labelUnit` (string): Unit label appended to value labels (e.g., `\"%\"`, `\"kn\"`).\n- `labelDecimals` (number): Number of decimal places for value labels.\n- `labelWidth` (string): CSS width for value labels (e.g., `\"5ch\"`, `\"60px\"`).\n- `showLeftReadout` (boolean, property only): Show the left (low) readout label. Default `true`.\n- `showRightReadout` (boolean, property only): Show the right (high) readout label. Default `true`.\n- `hugcontainer` (attribute): If present, removes spacing between slider and container edges.\n\n## Events\n- `value` – Fired continuously whenever the low or high value changes during user interaction. Event detail contains `{low, high}`.\n- `change` – Fired only after user interaction completes (mouse release). Event detail contains `{low, high}`.\n\n## Best Practices and Constraints\n- Ensure `low` is always less than or equal to `high`; the component enforces this automatically.\n- For accessibility, provide clear labels and units so users understand the meaning of the range.\n- Use the `no-input` variant for summary or review screens where editing is not allowed.\n- When using `allowSeeking`, set an appropriate `seekingSpeed` for smooth but responsive thumb movement.\n- Avoid setting `step` too small for large ranges, as this may make precise selection difficult.\n\n## Example\n\n```html\n<obc-slider-double\n  min=\"0\"\n  max=\"100\"\n  low=\"20\"\n  high=\"80\"\n  step=\"5\"\n  label-unit=\"%\"\n  label-decimals=\"0\"\n  variant=\"enhanced\"\n  allowSeeking\n>\n  <obi-placeholder slot=\"icon-left\"></obi-placeholder>\n  <obi-placeholder slot=\"icon-right\"></obi-placeholder>\n</obc-slider-double>\n```\n\nIn this example, the slider allows selection of a percentage range from 0 to 100, with 5% increments, enhanced styling, and seeking enabled.",
+          "description": "`<obc-slider-double>` – A dual-thumb range slider for selecting a value interval within a defined range.\n\nThis component allows users to select a minimum and maximum value by dragging two thumbs along a horizontal track. It is commonly used for filtering or specifying ranges (such as price, speed, or time intervals) in forms and dashboards. The slider supports both interactive and read-only display modes, as well as visual variants for different UI needs.\n\nAppears with two draggable handles (thumbs) and labels showing the current low and high values. The low and high readout labels can be customized via slots.\n\n## Features\n- **Dual-thumb range selection:** Users can adjust both the lower and upper bounds of a numeric interval.\n- **Variants:**\n  - **Normal:** Standard slider with compact styling.\n  - **Enhanced:** Larger track and thumb for increased prominence or touch accessibility.\n  - **NoInput:** Read-only mode; disables all user interaction and presents the current range as static.\n- **Configurable range:** Set minimum (`min`), maximum (`max`), and step size (`step`) for precise control.\n- **Step click adjustment:** Use `stepClick` to define increment/decrement amount for keyboard or button-based changes.\n- **Seeking mode:** Enable `allowSeeking` to let users jump to a value by clicking on the track, with smooth animated transitions controlled by `seekingSpeed`.\n- **Custom labels:** Display formatted value labels with unit (`labelUnit`), decimal precision (`labelDecimals`), and adjustable label width (`labelWidth`).\n- **Hug container option:** Remove spacing between slider and container edges with the `hugcontainer` attribute for seamless layout integration.\n- **Custom readouts:** Replace the low/high value labels with custom content using the `left-readout` and `right-readout` slots.\n\n## Usage Guidelines\nUse `obc-slider-double` when you need users to specify a numeric range, such as filtering results by minimum and maximum values. Ideal for scenarios like:\n- Filtering items by price, speed, or other continuous values.\n- Selecting a time interval or threshold range.\n- Any UI where a bounded numeric interval is required.\n\nFor single-value selection, use a standard slider component instead. In read-only or summary views, use the `no-input` variant to display the selected range without allowing changes.\n\n**TODO(designer):** Confirm if there are recommended minimum thumb separation or constraints for usability, and if there are best practices for using the enhanced variant.\n\n## Slots\n\n| Slot Name     | Renders When...               | Purpose                                                                                                          |\n|---------------|-------------------------------|------------------------------------------------------------------------------------------------------------------|\n| left-readout  | `showLeftReadout` is true     | Custom content for the left (low) readout label. Falls back to the formatted `low` value.                        |\n| right-readout | `showRightReadout` is true    | Custom content for the right (high) readout label. Falls back to the formatted `high` value.                     |\n\n## Properties and Attributes\n- `low` (number): The current lower bound of the selected range.\n- `high` (number): The current upper bound of the selected range.\n- `min` (number): The minimum allowed value (default: 0).\n- `max` (number): The maximum allowed value (default: 100).\n- `step` (number): The increment for value changes (default: 1).\n- `stepClick` (number): Step size for keyboard or button-based changes (default: 10).\n- `variant` (`normal` | `enhanced` | `no-input`): Visual and interaction style (default: `normal`).\n- `allowSeeking` (boolean): If true, clicking the track animates the thumb to the clicked position.\n- `seekingSpeed` (number): Animation speed for seeking (default: 1/3, i.e., full range in 3 seconds).\n- `labelUnit` (string): Unit label appended to value labels (e.g., `\"%\"`, `\"kn\"`).\n- `labelDecimals` (number): Number of decimal places for value labels.\n- `labelWidth` (string): CSS width for value labels (e.g., `\"5ch\"`, `\"60px\"`).\n- `showLeftReadout` (boolean, property only): Show the left (low) readout label. Default `true`.\n- `showRightReadout` (boolean, property only): Show the right (high) readout label. Default `true`.\n- `hugcontainer` (attribute): If present, removes spacing between slider and container edges.\n\n## Events\n- `value` – Fired continuously whenever the low or high value changes during user interaction. Event detail contains `{low, high}`.\n- `change` – Fired only after user interaction completes (mouse release). Event detail contains `{low, high}`.\n\n## Best Practices and Constraints\n- Ensure `low` is always less than or equal to `high`; the component enforces this automatically.\n- For accessibility, provide clear labels and units so users understand the meaning of the range.\n- Use the `no-input` variant for summary or review screens where editing is not allowed.\n- When using `allowSeeking`, set an appropriate `seekingSpeed` for smooth but responsive thumb movement.\n- Avoid setting `step` too small for large ranges, as this may make precise selection difficult.\n\n## Example\n\n```html\n<obc-slider-double\n  min=\"0\"\n  max=\"100\"\n  low=\"20\"\n  high=\"80\"\n  step=\"5\"\n  label-unit=\"%\"\n  label-decimals=\"0\"\n  variant=\"enhanced\"\n  allowSeeking\n>\n  <span slot=\"left-readout\">Min</span>\n  <span slot=\"right-readout\">Max</span>\n</obc-slider-double>\n```\n\nIn this example, the slider allows selection of a percentage range from 0 to 100, with 5% increments, enhanced styling, and seeking enabled.",
           "name": "ObcSliderDouble",
           "slots": [
-            {
-              "description": "Slot for the left icon",
-              "name": "icon-left"
-            },
-            {
-              "description": "Slot for the right icon",
-              "name": "icon-right"
-            },
             {
               "description": "Custom content for the left (low) readout label (rendered when `showLeftReadout` is true)",
               "name": "left-readout"
@@ -61546,6 +61700,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcStatusIndicator",
+          "slots": [
+            {
+              "description": "Label content shown next to the status indicator.",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -62205,6 +62365,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcSystemMenu",
+          "slots": [
+            {
+              "description": "Custom battery status text (falls back to the built-in charging/battery label).",
+              "name": "battery-status"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -62716,7 +62882,8 @@
               "name": "push-to-talk-change",
               "type": {
                 "text": "CustomEvent"
-              }
+              },
+              "description": "When the push-to-talk toggle is changed"
             },
             {
               "name": "battery-saving-mode-change",
@@ -63820,6 +63987,16 @@
           "kind": "class",
           "description": "",
           "name": "ObcTableHeaderItem",
+          "slots": [
+            {
+              "description": "Leading icon (shown when `hasLeadingIcon` is true).",
+              "name": "leading-icon"
+            },
+            {
+              "description": "Header label content (hidden when `type` is `IconOnly`).",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -64534,6 +64711,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcTag",
+          "slots": [
+            {
+              "description": "Leading icon content (shown when `hasIcon` is true).",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -67924,7 +68107,7 @@
       "declarations": [
         {
           "kind": "class",
-          "description": "`<obc-toggletip>` – A contextual message component for displaying inline notes, feedback, or alerts anchored to a UI element.\n\nThe toggletip provides brief, focused information or actions related to a specific UI context, often appearing as a floating panel with an arrow pointing to its trigger. It supports a range of visual variants for different semantic meanings, from neutral information to critical alerts.\n\nAppears above the interface to deliver context-sensitive guidance, warnings, or actions without disrupting the main workflow. Commonly used for tooltips with rich content, inline help, or actionable notifications.\n\n## Features\n\n- **Variants for semantic meaning:**\n  - `normal` (default): Standard informational note.\n  - `raised`: Elevated importance with a dark header for emphasis.\n  - `enhanced`: For primary or enhanced information requiring user attention.\n  - `eco-feedback`: Positive or environmental feedback.\n  - `caution`: Indicates caution or minor issues.\n  - `warning`: Highlights warnings or potential problems.\n  - `alarm`: Signals critical or urgent conditions.\n- **Customizable layout:**\n  - Optional header (title container) and description.\n  - Optional content area for custom elements or rich content.\n  - Optional action buttons (primary and secondary).\n  - Leading and trailing icon slots for visual context.\n  - Adjustable width via `customWidth` property.\n- **Icon logic:**\n  - Leading icon is shown by default and adapts to the variant (e.g., warning, alarm, eco-feedback).\n  - Trailing icon slot for additional context or actions.\n- **Responsive and accessible:**\n  - Content adapts to available space.\n  - All sections (header, description, content, actions) can be toggled independently.\n- **Events:**\n  - `primary-action`: Fired when the primary action button is clicked.\n  - `secondary-action`: Fired when the secondary action button is clicked.\n\n## Usage Guidelines\n\nUse `obc-toggletip` to provide contextual information, warnings, or actions related to a specific UI element or state. Ideal for:\n- Explaining the purpose or status of a control.\n- Delivering inline feedback or guidance.\n- Presenting warnings, cautions, or critical alerts in context.\n- Offering quick actions related to the message.\n\nAvoid using for persistent or global alerts—use a banner or dialog for those cases. For simple tooltips with only text, a lightweight tooltip component may be more appropriate.\n\n**TODO(designer):** Confirm if there are recommended maximum lengths for title/description, and if both action buttons should always be shown together or if one is preferred as primary.\n\n## Slots\n\n| Slot Name      | Renders When...              | Purpose                                               |\n| -------------- | --------------------------- | ----------------------------------------------------- |\n| leading-icon   | `hasLeadingIcon` is true    | Main icon representing the message type or context.   |\n| trailing-icon  | `hasTrailingIcon` is true   | Additional icon for secondary context or actions.     |\n| content        | `hasContent` is true        | Custom content area for rich or interactive elements. |\n\n## Properties and Configuration\n\n- `variant`: Controls the visual style and semantic meaning (see Features above for all options).\n- `title`: Sets the header text (shown if `hasTitleContainer` is true).\n- `description`: Sets the main message text (shown if `hasDescription` is true).\n- `hasTitleContainer`, `hasDescription`, `hasContent`, `hasActions`: Toggle visibility of each section.\n- `hasLeadingIcon`, `hasTrailingIcon`: Toggle visibility of icon slots.\n- `primaryButtonLabel`, `secondaryButtonLabel`: Set labels for action buttons (shown if `hasActions` is true).\n- `customWidth`: Sets a custom width for the toggletip (in pixels).\n\n## Events\n\n- `primary-action`: Fired when the primary action button is clicked. Event detail contains `{ label: string }`.\n- `secondary-action`: Fired when the secondary action button is clicked. Event detail contains `{ label: string }`.\n\n## Best Practices and Constraints\n\n- Use the variant that best matches the message's intent (e.g., `alarm` for critical, `eco-feedback` for positive).\n- Keep messages concise and focused on the immediate context.\n- Only show both action buttons if both are necessary; otherwise, prefer a single primary action.\n- The toggletip should point to its related UI element and not obscure important content.\n- For accessibility, ensure the toggletip is reachable via keyboard and screen reader.\n\n## Example\n\n```html\n<obc-toggletip\n  variant=\"warning\"\n  title=\"Unsaved Changes\"\n  description=\"You have unsaved edits. Save before leaving.\"\n  hasActions\n  primaryButtonLabel=\"Save\"\n  secondaryButtonLabel=\"Discard\"",
+          "description": "`<obc-toggletip>` – A contextual message component for displaying inline notes, feedback, or alerts anchored to a UI element.\n\nThe toggletip provides brief, focused information or actions related to a specific UI context, often appearing as a floating panel with an arrow pointing to its trigger. It supports a range of visual variants for different semantic meanings, from neutral information to critical alerts.\n\nAppears above the interface to deliver context-sensitive guidance, warnings, or actions without disrupting the main workflow. Commonly used for tooltips with rich content, inline help, or actionable notifications.\n\n## Features\n\n- **Variants for semantic meaning:**\n  - `normal` (default): Standard informational note.\n  - `raised`: Elevated importance with a dark header for emphasis.\n  - `enhanced`: For primary or enhanced information requiring user attention.\n  - `eco-feedback`: Positive or environmental feedback.\n  - `caution`: Indicates caution or minor issues.\n  - `warning`: Highlights warnings or potential problems.\n  - `alarm`: Signals critical or urgent conditions.\n- **Customizable layout:**\n  - Optional header (title container) and description.\n  - Optional content area for custom elements or rich content.\n  - Optional action buttons (primary and secondary).\n  - Leading and trailing icon slots for visual context.\n  - Adjustable width via `customWidth` property.\n- **Icon logic:**\n  - Leading icon is shown by default and adapts to the variant (e.g., warning, alarm, eco-feedback).\n  - Trailing icon slot for additional context or actions.\n- **Responsive and accessible:**\n  - Content adapts to available space.\n  - All sections (header, description, content, actions) can be toggled independently.\n- **Events:**\n  - `primary-action`: Fired when the primary action button is clicked.\n  - `secondary-action`: Fired when the secondary action button is clicked.\n\n## Usage Guidelines\n\nUse `obc-toggletip` to provide contextual information, warnings, or actions related to a specific UI element or state. Ideal for:\n- Explaining the purpose or status of a control.\n- Delivering inline feedback or guidance.\n- Presenting warnings, cautions, or critical alerts in context.\n- Offering quick actions related to the message.\n\nAvoid using for persistent or global alerts—use a banner or dialog for those cases. For simple tooltips with only text, a lightweight tooltip component may be more appropriate.\n\n**TODO(designer):** Confirm if there are recommended maximum lengths for title/description, and if both action buttons should always be shown together or if one is preferred as primary.\n\n## Slots\n\n| Slot Name      | Renders When...              | Purpose                                               |\n| -------------- | --------------------------- | ----------------------------------------------------- |\n| leading-icon   | `hasLeadingIcon` is true    | Main icon representing the message type or context.   |\n| trailing-icon  | `hasTrailingIcon` is true   | Additional icon for secondary context or actions.     |\n| content        | `hasContent` is true        | Custom content area for rich or interactive elements. |\n\n## Properties and Configuration\n\n- `variant`: Controls the visual style and semantic meaning (see Features above for all options).\n- `title`: Sets the header text. The header is shown only when `title` is a non-empty string.\n- `description`: Sets the main message text. Shown whenever `description` is defined.\n- `hasContent`, `hasActions`: Toggle visibility of the custom content area and the action buttons.\n- `hasLeadingIcon`, `hasTrailingIcon`: Toggle visibility of icon slots (only effective when a `title` is set).\n- `primaryButtonLabel`, `secondaryButtonLabel`: Set labels for action buttons (shown if `hasActions` is true).\n- `customWidth`: Sets a custom width for the toggletip (in pixels).\n\n## Events\n\n- `primary-action`: Fired when the primary action button is clicked. Event detail contains `{ label: string }`.\n- `secondary-action`: Fired when the secondary action button is clicked. Event detail contains `{ label: string }`.\n\n## Best Practices and Constraints\n\n- Use the variant that best matches the message's intent (e.g., `alarm` for critical, `eco-feedback` for positive).\n- Keep messages concise and focused on the immediate context.\n- Only show both action buttons if both are necessary; otherwise, prefer a single primary action.\n- The toggletip should point to its related UI element and not obscure important content.\n- For accessibility, ensure the toggletip is reachable via keyboard and screen reader.\n\n## Example\n\n```html\n<obc-toggletip\n  variant=\"warning\"\n  title=\"Unsaved Changes\"\n  description=\"You have unsaved edits. Save before leaving.\"\n  hasActions\n  primaryButtonLabel=\"Save\"\n  secondaryButtonLabel=\"Discard\"",
           "name": "ObcToggletip",
           "slots": [
             {
@@ -70107,6 +70290,12 @@
           "kind": "class",
           "description": "`<obc-user-menu>` – A user menu component with sign-in and signed-in layouts.\n\nProvides multiple layouts for authentication and account access states, including\nsign-in forms, user-specific sign-in, loading states, and signed-in navigation.\n\n### Features\n- **Multiple States:** Supports sign-in, user sign-in, loading, and signed-in layouts.\n- **Size Options:** Regular and small sizes for compact layouts.\n- **Recent Users:** Optional \"Recently signed in\" section for quick access.\n- **Navigation Actions:** Signed-in state includes navigation items and actions.\n\n### Variants\n- `type`: `sign-in`, `user-sign-in`, `loading-sign-in`, `signed-in`\n- `size`: `regular`, `small`\n\n### Usage Guidelines\nUse `obc-user-menu` in authentication or account panels where quick access to\nsign-in, profile, or account actions is needed. The `user-sign-in` type is\nbest for fast re-auth flows; `loading-sign-in` is for pending auth states.\n\n### Properties and Configuration\n- `type` (`ObcUserMenuType`): Controls the layout state. Defaults to `sign-in`.\n- `size` (`ObcUserMenuSize`): Controls the overall size. Defaults to `regular`.\n- `hasRecentlySignedIn` (`boolean`): Toggles the recent users section.\n  Defaults to `true`.\n- `username` (`string`): Current username value for sign-in layouts.\n- `password` (`string`): Current password value for sign-in layouts.\n- `usernameError` (`string`): Error message for the username field.\n- `passwordError` (`string`): Error message for the password field.\n- `userInitials` (`string`): Initials for the primary user profile.\n- `userLabel` (`string`): Label for the primary user profile.\n- `recentUsers` (`ObcUserMenuUser[]`): List of recent users shown in the\n  \"Recently signed in\" section.\n- `signedInActions` (`ObcUserMenuSignedInAction[]`): Actions shown in the\n  signed-in navigation list.\n\n### Events\n- `sign-in-click` – Fired when a sign-in button is clicked.\n- `sign-out-click` – Fired when the sign-out button is clicked.\n- `signed-in-action-click` – Fired when a signed-in action is clicked.\n- `recent-user-click` – Fired when a recent user button is clicked.\n\n### Slots\n- `signed-in-action-icon-{id}`: Optional icon for a signed-in action. The\n  `{id}` is the normalized action id.\n\n### Example\n```html\n<obc-user-menu\n  type=\"user-sign-in\"\n  size=\"small\"\n  hasRecentlySignedIn=\"false\"\n  userInitials=\"JD\"\n  userLabel=\"John Doe\"\n></obc-user-menu>\n```",
           "name": "ObcUserMenu",
+          "slots": [
+            {
+              "description": "Optional icon for a signed-in action, one per action; `<id>` is the normalized action id (shown in the `signed-in` type).",
+              "name": "signed-in-action-icon-<id>"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -70671,6 +70860,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcIntegrationAppBar",
+          "slots": [
+            {
+              "description": "Application buttons; slotted elements are normalized to a uniform width",
+              "name": "apps"
+            }
+          ],
           "members": [
             {
               "kind": "method",
@@ -70723,27 +70918,35 @@
           "name": "ObcIntegrationBarDropdown",
           "slots": [
             {
+              "description": "Vessel selector content",
               "name": "vessel-selector"
             },
             {
+              "description": "Label for the first status field",
               "name": "status-label-1"
             },
             {
+              "description": "Icon for the first status field",
               "name": "status-icon-1"
             },
             {
+              "description": "Label for the second status field",
               "name": "status-label-2"
             },
             {
+              "description": "Icon for the second status field",
               "name": "status-icon-2"
             },
             {
+              "description": "Label for the third status field",
               "name": "status-label-3"
             },
             {
+              "description": "Icon for the third status field",
               "name": "status-icon-3"
             },
             {
+              "description": "Custom clock content, rendered when `showClock` is true",
               "name": "clock"
             }
           ],
@@ -70893,7 +71096,7 @@
               "type": {
                 "text": "CustomEvent"
               },
-              "description": "Firaed when the notification button is clicked"
+              "description": "Fired when the notification button is clicked"
             },
             {
               "name": "system-button-clicked",
@@ -71078,10 +71281,6 @@
             {
               "description": "Compact vessel integration buttons; slotted integration buttons are forced to hug type",
               "name": "hug-buttons"
-            },
-            {
-              "description": "Modal that will appear achored below the fleet/vessel button. Typically an obc-integration-vessel-menu",
-              "name": "vessel-integration-menu"
             }
           ],
           "members": [
@@ -72208,6 +72407,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcIntegrationFleetButton",
+          "slots": [
+            {
+              "description": "Icon shown alongside the alert topic",
+              "name": "alert-topic-icon"
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -72352,6 +72557,12 @@
           "kind": "class",
           "description": "",
           "name": "ObcIntegrationTabs",
+          "slots": [
+            {
+              "description": "Tab label content",
+              "name": ""
+            }
+          ],
           "members": [
             {
               "kind": "field",
@@ -74971,11 +75182,6 @@
               "readonly": true
             }
           ],
-          "events": [
-            {
-              "name": "None"
-            }
-          ],
           "attributes": [
             {
               "name": "heading",
@@ -95001,11 +95207,6 @@
               "privacy": "private"
             }
           ],
-          "events": [
-            {
-              "name": "None"
-            }
-          ],
           "attributes": [
             {
               "name": "forceAngle",