The actionable toast appears after reversible operations — "Transfer sent · Undo", "Message failed · Retry", "Photo uploaded · View". The action button sits right-aligned, tappable without dismissing the toast. Auto-dismiss is suppressed while an action is present.

• Separate component for a button slot that should be a prop on the base Toast. Material's Snackbar, SwiftUI's .alert(actions:), and every other mature DS handle this as an optional action parameter — not a sibling record. Maintaining two components doubles the surface area of every future change and invites drift (different widths, different type sets). C1 · Layer Structure & Naming
• Axis names + values drift from the base Toast. Base Toast exposes type = default | pending | error + theme = default | light | dark. This sibling exposes type = default | light — same axis name, narrower value set, collides on meaning. Consumers wiring Code Connect can't treat them as the same prop. C2 · Variant & Property Naming
• description=yes|no is a slot + sizing flag bundled into a string. When description is present, vertical padding grows from 8 to 12 and a 4 px gap is inserted below the label. The trigger should be the presence of supporting-text content (supportingText?: String), not a hard-coded variant. C2 · Variant & Property Naming
• Action surface uses the deprecated Button - Small/XS. The embedded Button instance (node 21:164490) is marked DEPRECATED in Figma, slated for deletion. When that source is removed, every variant of this toast breaks. Must re-link to Button - XSmall. C4 · Native Mappability
• No icon axis at all. Base Toast has With Icon = yes | no. This sibling drops the axis entirely — you can't have an actionable toast with a leading checkmark or error glyph. Merging into Toast recovers the icon automatically. C6 · Asset & Icon Quality
• Whole-container tap overlaps the action button. The default, description=no variant wraps the entire toast in a <button> element, while the inner action is also a button — two conflicting tap targets stacked. Behavior is undefined when the user taps the non-action area. C5 · Interaction State Coverage
• Action has no states. No pressed, disabled, or loading state on the action. "Retry" actions commonly need a spinner after tap; destructive "Undo" often needs to grey out during processing. Not modeled. C5 · Interaction State Coverage
• Width 330 vs. base Toast 312. Inconsistent with the base Toast's fixed width. A single consolidated component picks one width (recommend 312, matching the rest of the family). C1 · Layer Structure & Naming
• Code Connect mappings not registered. Blocked on consolidation — there should be no separate Code Connect entry; the action slot maps to the base Toast's action parameter. C7 · Code Connect Linkability

• Consolidate into the base Toast. Remove Toast - With Button from the family. Base Toast picks up two new optional slots: supportingText?: String (the 10/15 BarkAda second line) and action?: EBToastAction (label + callback, with optional loading and disabled states). One component, covers every use case today and the ones this sibling misses (actionable error, actionable with icon). Family
• Migrate the action surface to Button - XSmall. The embedded Button - Small/XS is marked deprecated in Figma. Rebind the action instance to the canonical Button - XSmall before the deprecated source is deleted — otherwise every variant breaks. Composition
• Replace description=yes|no with a supporting-text slot. Promote the second text line to an optional content slot. The padding and gap changes follow from the slot being populated — no duplicate variants required. Slot
• Normalize width to 312. Match the base Toast. One width across the family. Property
• Define the action's state contract. Spec pressed / disabled / loading states on the action slot so "Retry" and "Undo" flows can reflect processing state. State
• Resolve the whole-container tap conflict. Decide: either the toast is dismiss-on-tap (drop the action as the only interactive surface), or the action owns the only tappable region. Pick one and drop the root <button> wrapper from the other variants. State
• Document auto-dismiss suppression when an action is present. A toast with an action stays visible until the user taps the action or explicitly dismisses. Call this out as a usage note. Docs
• Document the A11y announcement mapping. Action label feeds accessibilityLabel (iOS) / contentDescription (Android). Live region polite for neutral, assertive if consolidated into a destructive Toast. A11y