import type{LyraEventDetailSnapshot}from'../../../internal/lyra-element.js';import{type PropertyValues,type TemplateResult}from'lit';import{LyraElement}from'../../../internal/lyra-element.js';import'../../utility/copy-button/copy-button.class.js';import'../message-feedback/message-feedback.class.js';import type{LyraClipboardWriteFailure,LyraClipboardWriteSuccess}from'../../../internal/clipboard.js';import type{MessageFeedbackSubmitDetail,MessageFeedbackValue}from'../message-feedback/message-feedback.class.js';export type MessageActionControl='copy'|'regenerate'|'edit'|'feedback';export interface LyraMessageActionsEventMap{'lr-regenerate':CustomEvent<null>;'lr-edit':CustomEvent<null>;'lr-copy':CustomEvent<LyraClipboardWriteSuccess>;'lr-error':CustomEvent<null>;'lr-copy-error':CustomEvent<LyraClipboardWriteFailure>;'lr-feedback-change':CustomEvent<{rating:MessageFeedbackValue;}>;'lr-feedback-submit':CustomEvent<LyraEventDetailSnapshot<MessageFeedbackSubmitDetail>>;}
/**
* `<lr-message-actions>` — the per-message action toolbar for `<lr-chat-message>`'s `actions`
* slot: opt-in built-ins (copy / regenerate / edit / feedback) that emit intent events, plus a
* default slot for custom controls (e.g. a slotted `<lr-branch-picker>`). It performs nothing
* itself except the copy.
*
* `[part="base"]` is `role="toolbar"` with the WAI-ARIA APG roving-tabindex pattern applied to the
* plain `<button>` elements this component renders itself (`regenerate`/`edit`); ArrowLeft/ArrowRight
* (swapped under `effectiveDirection === 'rtl'`) plus Home/End move focus across every logical
* action. Plain light-DOM actions are flattened directly. Composite controls opt into the exported
* `LyraToolbarActionProvider` protocol, which keeps implementation nodes private while exposing
* ordered focus/tab-stop operations and stable action IDs. Both feedback thumbs and both branch
* controls therefore remain independent arrow-key stops without parent shadow-root inspection.
* When a managed action leaves the toolbar, its optional `releaseTabIndex()` restores an untouched
* authored tab stop; a consumer change made after toolbar management always remains authoritative.
* Providers notify availability/order changes with `lr-toolbar-actions-change`; plain authored
* actions are observed in light DOM. A former stop is cleared, and if it held focus, focus moves to
* the nearest survivor or the stable toolbar without overriding a newer external focus move.
*
* Public collection properties take bounded, clone-owned readonly snapshots. Create a new
* collection and reassign it after changes; mutating the assigned array does not update the view.
* Built-in control names normalize first-wins before rendering, focus navigation, or intent
* events, so each built-in can occur at most once. Provider action ids must be nonblank and unique
* within that provider; invalid actions and later duplicates are omitted.
*
* ArrowLeft/ArrowRight/Home/End from a slotted feedback comment editor remain native editing keys. Roving navigation still operates on the actual toolbar and thumb actions.
*
* The toolbar has no `size`/`compact` property of its own: every built-in action composes
* `<lr-icon-button>` (the embedded `lr-copy-button` does the same one level deeper), so each one's
* hit area is that component's shared `--lr-icon-button-size` floor (2.5rem/40px), same as
* everywhere else in the library. For a dense action row where 40px per action is more than the
* layout can afford, lower `--lr-icon-button-size-scope` (the subtree-scoped input) or
* `--lr-theme-icon-button-size` (the application-wide one) -- NOT `--lr-icon-button-size` itself,
* which every `LyraElement` re-declares on its own `:host` and so never reaches a composed child
* (`internal/tokens.test.ts` proves this) -- on this element or any ancestor of it;
* `::part(regenerate-button__control)`/`::part(edit-button__control)` also reach the built-ins'
* composed native controls directly for a one-off override. Either way the shrink is local to the
* elements it targets, not a library-wide floor change. A coarse-pointer/no-hover safety net
* (`internal/tokens.styles.ts`'s `baseTokens`) then floors the rendered hit area back at
* 2.75rem/44px regardless of how far the dense-row override lowered it, so an intentionally
* cramped desktop toolbar is still comfortably tappable the moment the pointer reaching it is a
* finger rather than a mouse.
*
* @customElement lr-message-actions
* @slot - Additional controls (e.g. `lr-copy-button`, `lr-icon-button`, `lr-branch-picker`)
*   appended after the built-ins; they participate in the toolbar's arrow-key navigation.
* @event lr-regenerate - The regenerate built-in was activated. No detail.
* @event lr-edit - The edit built-in was activated: a *request* to edit; the host swaps the message
*   body for its own editor.
* @event lr-copy - Clipboard writing fulfilled. Frozen `detail: { ok: true, text }`, surfaced by
*   the embedded `lr-copy-button` (bubbles + composed already; not re-emitted, so exactly one event
*   reaches a host listener).
* @event lr-error - Clipboard writing failed; generic `detail: null` signal from the embedded
*   copy button.
* @event lr-copy-error - Clipboard writing failed. Frozen
*   `detail: { ok: false, text, reason, error }` from the embedded copy button.
* @event lr-feedback-change - Bubbles unchanged from the embedded, thumbs-only
*   `lr-message-feedback`. `detail: { rating }`. A colliding event from a slotted custom child is
*   contained at the slot boundary and remains observable directly on that child.
* @event lr-feedback-submit - The built-in feedback control's terminal cancelable persistence
*   request, including thumbs-only choices. Its frozen detail includes a nonblank `submissionId`;
*   when prevented, pass that exact ID to `finalizePendingSubmit()` or
*   `revertPendingSubmit()` on this wrapper. Slotted collisions are contained at the slot boundary.
* @csspart base - The toolbar (`role="toolbar"`).
* @csspart copy-button - The embedded `lr-copy-button`.
* @csspart regenerate-button - The built-in regenerate action, a composed `<lr-icon-button>` as of
*   16.0.0. It still owns the accessible name, the activation and the toolbar tab stop; its
*   background, radius, hover/press mixes, focus ring and hit-area floor now come from
*   `--lr-icon-button-*`.
* @csspart regenerate-button__control - The regenerate action's own native `<button>`, forwarded
*   because the painted surface sits one shadow boundary deeper than `regenerate-button`.
* @csspart edit-button - The built-in edit action, likewise a composed `<lr-icon-button>`.
* @csspart edit-button__control - The edit action's own native `<button>`.
* @csspart feedback - The embedded `lr-message-feedback`.
* @status stable
* @since 4.0.0
*/
export declare class LyraMessageActions extends LyraElement<LyraMessageActionsEventMap>{protected static readonly ownedCollectionProperties:readonly string[];static styles:import("lit").CSSResultGroup[];protected static readonly immutableEventDetails:readonly string[];
/** Which built-ins render, in display order. Duplicate names normalize first-wins. */
controls:readonly MessageActionControl[];private get effectiveControls();
/** What the `copy` built-in copies. Required for it to render at all -- this component never
*  interprets the slotted message body itself. */
copyText:string;
/** Forwarded to the embedded thumbs-only `lr-message-feedback` when enabled. */
feedbackRating:MessageFeedbackValue;
/** Whether this component's current built-in feedback child is awaiting a persistence settle.
*  This is a nonreflecting read-through; no `feedback-pending` attribute or change event exists. */
get feedbackPending():boolean;
/** Settles only the currently rendered built-in feedback transaction identified by `submissionId`.
*  A removed, replaced, stale, or mismatched child fails closed. */
finalizePendingSubmit(submissionId:string):boolean;
/** Reverts only the currently rendered built-in feedback transaction identified by `submissionId`.
*  A removed, replaced, stale, or mismatched child fails closed. */
revertPendingSubmit(submissionId:string):boolean;
/** Visually hides the bar until the enclosing message is hovered or any control inside has focus. */
revealOnInteraction:boolean;
/** Accessible name for the toolbar. Defaults to the localized `messageActionsLabel`. */
label:string;
/** Overrides the toolbar's computed accessible name. Wins over `label` and the localized
*  default. Attribute-reflects from a host-level `aria-label` so a plain-markup consumer gets
*  ARIA-name forwarding without setting a JS property. */
accessibleLabel:string|null;private activeStopIndex;
/** Drives the `data-revealed` host attribute (toggled imperatively in `updated()`, not via a Lit
*  template binding -- `lr-graph`'s `data-hovered` attribute is the precedent for this exact
*  technique) while `revealOnInteraction` is active. CSS alone cannot key `:host`'s own opacity off the
*  ancestor `lr-chat-message`'s hover state from inside this component's own shadow DOM, so the
*  reveal state is tracked in JS instead (see `bindHoverTarget()`). */
private revealed;private hoverTarget;private stopSyncGeneration;private stopObserver?;private managedStops;private directActions;private nextDirectActionId;private focusedStop?;private currentBuiltInFeedback;connectedCallback():void;disconnectedCallback():void;adoptedCallback():void;protected willUpdate(changed:PropertyValues):void;protected firstUpdated(changed:PropertyValues):void;protected updated(changed:PropertyValues):void;private bindHoverTarget;private unbindHoverTarget;private onHoverTargetEnter;private onHoverTargetLeave;private onFocusIn;private onFocusOut;
/** Immediate rendered children plus flattened slotted roots that own logical actions. */
private actionRoots;private sameAction;private isAvailable;private directActionFor;private logicalActions;private setActiveStop;private releaseManagedStop;private releaseManagedStops;private observeStopChanges;private onStopMutations;private reconcileStopsAfterChildren;private onSlotChange;private onToolbarActionsChange;private containSlottedFeedbackEvent;private onToolbarKeyDown;private onRegenerateClick;private onEditClick;private renderControl;render():TemplateResult;}declare global{interface HTMLElementTagNameMap{'lr-message-actions':LyraMessageActions;}}