@semantic-components/ui-lab 0.63.0 → 0.65.0

package/src/lib/components/alert-dialog/ARCHITECTURE.md

@@ -1,808 +0,0 @@
-# Alert Dialog Architecture
-
-## Overview
-
-The alert-dialog component uses a multi-signal architecture pattern to ensure smooth, complete animations before DOM cleanup. This document focuses on how animations are coordinated across the dialog content and backdrop using a signal counter to track completion of both animations.
-
-## Component Structure
-
-```
-ScAlertDialogProvider (Root State Manager + CDK Overlay Manager)
-├── ScAlertDialogTrigger (Opens dialog)
-└── ng-template[scAlertDialogPortal] (Lazy content, portaled to CDK overlay)
-    │
-    Inside CDK Overlay (managed by Provider):
-    ├── CDK Backdrop (Transparent - click blocking only)
-    ├── ScBackdrop (Visual backdrop with animations)
-    └── ScAlertDialog (Dialog Content)
-        ├── ScAlertDialogHeader
-        │   ├── ScAlertDialogMedia (Optional)
-        │   └── ScAlertDialogTitle
-        │   └── ScAlertDialogDescription
-        └── ScAlertDialogFooter
-            ├── ScAlertDialogCancel
-            └── ScAlertDialogAction
-```
-
-### ScAlertDialogPortal Directive
-
-`ScAlertDialogPortal` is a structural directive on `ng-template` that marks the lazy content to be portaled into the CDK overlay. It holds a reference to the `TemplateRef` which the provider reads via `contentChild`.
-
-```typescript
-@Directive({
-  selector: 'ng-template[scAlertDialogPortal]',
-})
-export class ScAlertDialogPortal {
-  readonly templateRef = inject(TemplateRef);
-}
-```
-
-The provider queries it and projects the template into the overlay:
-
-```typescript
-// In ScAlertDialogProvider
-protected readonly alertDialogPortal = contentChild.required(ScAlertDialogPortal);
-
-// In provider's overlay template
-<ng-container [ngTemplateOutlet]="alertDialogPortal().templateRef" />
-```
-
-### Why a Directive?
-
-- **Explicit**: A bare `<ng-template>` is ambiguous; `scAlertDialogPortal` communicates intent
-- **Lazy**: Content inside `ng-template` is not instantiated until the provider stamps it
-- **Provider owns lifecycle**: The provider decides _when_ to stamp the template (on open)
-- **DI preserved**: Using `TemplatePortal(overlayTemplate, viewContainerRef)` with the provider's own `ViewContainerRef` keeps the injector chain intact — `ScAlertDialog` can inject `ScAlertDialogProvider`
-
-## The Multi-Signal Pattern
-
-The core of the animation architecture is the separation of **logical state** from **physical state**, with a **coordination signal** to track animation completions.
-
-### Signal 1: `open` (Logical State)
-
-**Purpose:** Controls what the dialog _should_ be doing
-
-```typescript
-// In ScAlertDialogProvider
-readonly open = model<boolean>(false);
-```
-
-**Responsibilities:**
-
-- Represents user intent ("should the dialog be visible?")
-- Triggers animation state changes
-- When `true`: Triggers entry animations
-- When `false`: Triggers exit animations
-
-### Signal 2: `overlayOpen` (Physical State)
-
-**Purpose:** Controls whether DOM exists
-
-```typescript
-// In ScAlertDialogProvider
-readonly overlayOpen = signal<boolean>(false);
-```
-
-**Responsibilities:**
-
-- Controls CDK overlay attachment/detachment
-- Stays `true` during close animations (critical!)
-- Only becomes `false` after animations complete
-- Ensures animations can play before DOM removal
-
-### Signal 3: `animationsCompleted` (Animation Coordination)
-
-**Purpose:** Tracks completion of multiple animations
-
-```typescript
-// In ScAlertDialogProvider (private)
-private readonly animationsCompleted = signal<number>(0);
-```
-
-**Responsibilities:**
-
-- Counts completed animations during close sequence
-- Target count: 2 (dialog + backdrop)
-- Resets to 0 when opening (for next cycle)
-- Triggers overlay closure when target reached
-
-### Why Both Are Needed
-
-**The Problem:**
-
-CDK overlay's lifecycle is tied to DOM presence:
-
-```typescript
-// ❌ This doesn't work:
-if (open()) {
-  overlayRef.attach(portal); // DOM mounted
-} else {
-  overlayRef.detach(); // DOM removed IMMEDIATELY
-  // Animation never plays - element is gone!
-}
-```
-
-**The Solution:**
-
-Separate signals allow animation completion:
-
-```typescript
-// ✅ This works:
-if (overlayOpen()) {
-  // Physical state
-  overlayRef.attach(portal); // DOM mounted
-} else {
-  overlayRef.detach(); // DOM removed AFTER animations
-}
-
-// Meanwhile, open() controls animations:
-if (open()) {
-  // Logical state
-  state = 'open'; // Entry animation
-} else {
-  state = 'closed'; // Exit animation (DOM still mounted!)
-}
-```
-
-## Animation Architecture
-
-### Three Layers (Separated by Concern)
-
-1. **CDK Backdrop** (Transparent - No Animation)
-   - Class: `cdk-overlay-transparent-backdrop`
-   - Purpose: Click blocking and scroll prevention
-   - Functional layer only, no visual styling
-   - Note: No `backdropClick` handler — alert dialog requires explicit dismissal
-
-2. **ScBackdrop Component** (100ms fade animation)
-   - Reusable component from `components/backdrop`
-   - Three-state model (`idle` / `open` / `closed`) with `data-idle`, `data-open`, `data-closed` attributes
-   - Fade effect via Tailwind animate classes
-   - Positioned with `fixed inset-0 -z-50` (behind dialog, behind CDK overlay)
-   - Emits `animationComplete` output when close animation finishes
-
-3. **Dialog Content Animation** (100ms)
-   - Zoom + Fade effects
-   - Three-state model (`idle` / `open` / `closed`) with `data-idle`, `data-open`, `data-closed` attributes
-   - Managed by Tailwind animate classes
-   - Completion detected via `animationend` event (triggers cleanup)
-
-### Synchronization
-
-Both ScBackdrop and Dialog animations:
-
-- Start simultaneously when `open` changes
-- Use same duration (100ms)
-- Use same three-state model (`idle` → `open` → `closed` → `idle`)
-- Inside same overlay (removed together)
-
-### Dialog Three-State Model
-
-The dialog uses three states to prevent a flash of content on first render:
-
-```typescript
-type ScAlertDialogState = 'idle' | 'open' | 'closed';
-```
-
-| State    | Data Attribute | Purpose                                                  |
-| -------- | -------------- | -------------------------------------------------------- |
-| `idle`   | `data-idle`    | Hidden (`opacity-0`), resting state                      |
-| `open`   | `data-open`    | Entry animation (`fade-in`, `zoom-in`)                   |
-| `closed` | `data-closed`  | Exit animation (`fade-out`, `zoom-out`) → back to `idle` |
-
-Flow: `idle` → `open` → `closed` → `idle`
-
-### Dialog Content Animations
-
-Applied via Tailwind classes in `alert-dialog.ts`:
-
-```typescript
-protected readonly class = computed(() =>
-  cn(
-    // Idle state: hidden
-    'data-idle:opacity-0',
-
-    // Entry animation (triggered by data-open)
-    'data-open:animate-in data-open:fade-in-0 data-open:zoom-in-95',
-
-    // Exit animation (triggered by data-closed)
-    'data-closed:animate-out data-closed:fade-out-0 data-closed:zoom-out-95',
-
-    // Base styles
-    'bg-background ring-foreground/10 grid max-w-sm gap-4 rounded-xl p-4 text-sm ring-1 duration-100 ...',
-  ),
-);
-```
-
-**Animation Flow:**
-
-1. `state` signal changes from `'idle'` to `'open'`
-2. `data-open` attribute set → entry animation starts
-3. User clicks cancel/action → `state` changes to `'closed'`
-4. `data-closed` attribute set → exit animation starts
-5. `animationend` event fires → `state` resets to `'idle'` (`opacity-0`)
-
-### ScBackdrop Component Animations
-
-Managed via ScBackdrop component from `components/backdrop`. Uses the same three-state model as the dialog:
-
-```typescript
-// In backdrop.ts
-type ScBackdropState = 'idle' | 'open' | 'closed';
-
-protected readonly class = computed(() =>
-  cn(
-    'pointer-events-none fixed inset-0 -z-50 bg-black/10 duration-100 supports-backdrop-filter:backdrop-blur-xs',
-    'data-idle:opacity-0',
-    'data-open:animate-in data-open:fade-in-0',
-    'data-closed:animate-out data-closed:fade-out-0',
-    this.classInput(),
-  ),
-);
-```
-
-**Animation Flow:**
-
-1. Provider renders: `<div sc-backdrop [open]="open()" (animationComplete)="onBackdropAnimationComplete()"></div>`
-2. ScBackdrop receives `open` input
-3. Effect sets `state` to `'open'` or `'closed'` based on `open` value
-4. Data attribute (`data-open` / `data-closed`) triggers Tailwind animation classes
-5. Animation plays for 100ms
-6. On `animationend`, if closing: state resets to `'idle'` (hidden), emits `animationComplete` output
-7. Provider handles the event directly for coordination
-
-**Why Separate Component?**
-
-- Reusable across dialog, drawer, sheet, alert-dialog, etc.
-- Consistent animation pattern
-- Single responsibility (visual layer only)
-- CDK backdrop handles functionality separately
-
-## Complete Animation Timeline
-
-### Opening Sequence
-
-```
-User clicks trigger:
-│
-├─ t=0ms: Trigger calls open.set(true)
-│  │
-│  ├─ Provider effect 1:
-│  │  ├─ overlayOpen.set(true)  ← Mount DOM immediately
-│  │  └─ animationsCompleted.set(0)  ← Reset for next cycle
-│  │
-│  └─ Provider effect 3 (triggered by overlayOpen):
-│     └─ attachDialog()  ← CDK overlay attached
-│        └─ TemplatePortal(overlayTemplate, viewContainerRef)
-│           ├─ ScBackdrop rendered with [open]="open()"
-│           └─ ng-template outlet stamps scAlertDialogPortal content
-│
-├─ t=0ms: CDK adds .cdk-overlay-backdrop-showing
-│  └─ Backdrop: state → 'open' (data-open set, 100ms fade-in)
-│
-├─ t=0ms: Dialog effect (triggered by open):
-│  └─ state.set('open')
-│     └─ data-open set → Entry animation starts
-│        ├─ fade-in-0
-│        ├─ zoom-in-95
-│        └─ duration-100
-│
-├─ t=0-100ms: Both animations play
-│
-└─ t=100ms: Animations complete, dialog visible
-```
-
-### Closing Sequence (Coordinated Completion)
-
-```
-User clicks cancel/action button:
-│
-├─ t=0ms: Button calls open.set(false)
-│  │
-│  ├─ Dialog effect (triggered by open):
-│  │  └─ state.set('closed')  ← Triggers animation
-│  │     └─ data-closed set → Exit animation starts
-│  │        ├─ animate-out
-│  │        ├─ fade-out-0
-│  │        └─ zoom-out-95
-│  │
-│  └─ Backdrop receives [open]="false" input:
-│     └─ state.set('closed')  ← Triggers backdrop animation
-│        └─ data-closed set → Backdrop fade-out
-│
-├─ IMPORTANT: overlayOpen is STILL true!
-│  └─ DOM remains mounted so animations can play
-│  └─ animationsCompleted = 0 (waiting for both)
-│
-├─ t=0-100ms: Both animations play simultaneously
-│
-├─ t=~100ms: Dialog animation completes
-│  └─ onAnimationEnd(event) fires
-│     └─ if (state === 'closed' && target === element):
-│        ├─ state.set('idle')  ← Reset to hidden resting state
-│        └─ provider.onDialogAnimationComplete()
-│           └─ animationsCompleted.update(n => n + 1)  ← Count = 1
-│
-├─ t=~100ms: Backdrop animation completes
-│  └─ backdrop emits (animationComplete)
-│     └─ provider.onBackdropAnimationComplete()
-│        └─ animationsCompleted.update(n => n + 1)  ← Count = 2
-│
-├─ Provider effect 2 detects: animationsCompleted === 2 && !open()
-│  └─ overlayOpen.set(false)  ← Cleanup triggered!
-│  └─ animationsCompleted.set(0)  ← Reset for next cycle
-│
-└─ t=~100ms: Provider effect 3 (triggered by overlayOpen):
-   └─ detachDialog()  ← DOM removed cleanly after BOTH complete
-```
-
-## Why Track Both Animations?
-
-**Question:** Why coordinate two separate animations instead of using a single timer?
-
-**Answer:** Explicit animation tracking is more robust and event-driven:
-
-### The Problem with Single Timers
-
-```typescript
-// ❌ Old approach - assumes both animations finish together
-onDialogAnimationComplete(): void {
-  setTimeout(() => {
-    this.overlayOpen.set(false);
-  }, 100); // Hope backdrop finishes too!
-}
-```
-
-**Issues:**
-
-- Assumes backdrop takes exactly 100ms
-- Browser rendering variations can cause timing differences
-- Backdrop might take 105ms, getting cut off at 100ms
-- No way to know if backdrop actually completed
-- Might wait longer than necessary if backdrop finishes early
-
-### The Solution: Signal Counter Pattern
-
-```typescript
-// ✅ New approach - explicitly track both completions
-private readonly animationsCompleted = signal<number>(0);
-
-onDialogAnimationComplete(): void {
-  this.animationsCompleted.update(n => n + 1); // Count = 1
-}
-
-onBackdropAnimationComplete(): void {
-  this.animationsCompleted.update(n => n + 1); // Count = 2
-}
-
-effect(() => {
-  if (this.animationsCompleted() === 2 && !this.open()) {
-    this.overlayOpen.set(false); // Both confirmed complete!
-  }
-});
-```
-
-**Benefits:**
-
-1. **Event-driven**: Waits for actual completion, not estimated time
-2. **Robust**: Handles browser timing variations (100ms vs 105ms)
-3. **Accurate**: Both animations explicitly signal completion
-4. **Extensible**: Easy to add more animations (just increase target count)
-5. **No race conditions**: Counter resets on open for clean cycles
-
-## State Synchronization
-
-### Provider Constructor Effects
-
-```typescript
-constructor() {
-  // Effect 1: Sync overlayOpen with open for OPENING
-  effect(() => {
-    if (this.open()) {
-      // Opening: Mount DOM immediately
-      this.overlayOpen.set(true);
-      // Reset counter for next close cycle
-      this.animationsCompleted.set(0);
-    }
-    // Note: When closing, overlayOpen stays true!
-    // It will be set to false by the coordination effect below
-  });
-
-  // Effect 2: Close overlay when both animations complete
-  effect(() => {
-    const completed = this.animationsCompleted();
-    if (completed === 2 && !this.open()) {
-      // Both animations confirmed complete
-      this.overlayOpen.set(false);
-      // Reset for next cycle
-      this.animationsCompleted.set(0);
-    }
-  });
-
-  // Effect 3: Attach/detach CDK overlay based on overlayOpen
-  effect(() => {
-    if (this.overlayOpen()) {
-      this.attachDialog();
-    } else {
-      this.detachDialog();
-    }
-  });
-}
-```
-
-### Provider Overlay Template
-
-The provider's template includes the backdrop and focus trap, projecting the consumer's `scAlertDialogPortal` template via `ngTemplateOutlet`:
-
-```html
-<ng-content />
-<ng-template #overlayTemplate>
-  <div sc-backdrop [open]="open()" (animationComplete)="onBackdropAnimationComplete()"></div>
-  <div cdkTrapFocus [cdkTrapFocusAutoCapture]="true">
-    <ng-container [ngTemplateOutlet]="alertDialogPortal().templateRef" />
-  </div>
-</ng-template>
-```
-
-Note: Unlike the Dialog provider, there are no `backdropClick` or `keydownEvents` handlers. An alert dialog requires the user to explicitly choose an action (Cancel or Action) to dismiss it.
-
-### Dialog Constructor Effects
-
-```typescript
-constructor() {
-  // Effect: Sync animation state with logical state
-  effect(() => {
-    const isOpen = this.alertDialogProvider.open();
-    this.state.set(isOpen ? 'open' : 'closed');
-  });
-}
-```
-
-## Animation Completion Handling
-
-### Dialog Component
-
-```typescript
-protected onAnimationEnd(event: AnimationEvent): void {
-  // Only trigger cleanup when close animation completes
-  if (
-    this.state() === 'closed' &&
-    event.target === this.elementRef.nativeElement
-  ) {
-    this.state.set('idle'); // Reset to hidden resting state
-    this.alertDialogProvider.onDialogAnimationComplete();
-  }
-}
-```
-
-**Why check `event.target`?**
-
-- `animationend` bubbles from child elements
-- We only care about the dialog's own animation
-- Prevents false triggers from child element animations
-
-### Provider Component
-
-The provider directly handles backdrop animation completion in its template — no intermediary needed:
-
-```html
-<!-- In provider's overlay template -->
-<div sc-backdrop [open]="open()" (animationComplete)="onBackdropAnimationComplete()"></div>
-```
-
-```typescript
-// In ScAlertDialogProvider
-onDialogAnimationComplete(): void {
-  if (!this.open()) {
-    this.animationsCompleted.update(n => n + 1);
-  }
-}
-
-onBackdropAnimationComplete(): void {
-  if (!this.open()) {
-    this.animationsCompleted.update(n => n + 1);
-  }
-}
-```
-
-**Why check `!this.open()` before incrementing?**
-
-- User might have reopened dialog during close animation
-- Prevents counter from incrementing during new open cycle
-- Guards against race conditions
-- Example: User clicks cancel (close starts), then immediately clicks trigger again (reopens)
-- Without this check, the counter would incorrectly increment for the new cycle
-
-**Why use `update()` instead of `set()`?**
-
-- Increment is relative to current value
-- Safe if multiple updates happen
-- Immutable update pattern
-- Consistent with Angular signals best practices
-
-## Comparison: Evolution of Animation Coordination
-
-### Approach 1: Single Timer (Previous Implementation)
-
-```typescript
-// ❌ Problems:
-private async detachDialogWithAnimation() {
-  if (this.overlayRef.hasAttached()) {
-    const backdrop = this.overlayRef.backdropElement;
-    backdrop?.classList.add('sc-backdrop-hiding');
-
-    // Wait arbitrary time
-    await firstValueFrom(timer(100));
-
-    this.overlayRef.detach();  // Might cut off dialog animation!
-  }
-}
-```
-
-**Issues:**
-
-1. Single hardcoded timer for all animations
-2. No detection of actual animation completion
-3. Dialog animation might take longer or shorter
-4. Not coordinated with dialog state
-5. No way to cancel if reopened
-
-### Approach 2: Signal Counter (Current Implementation)
-
-```typescript
-// ✅ Both animations explicitly tracked:
-private readonly animationsCompleted = signal<number>(0);
-
-constructor() {
-  // Effect 1: Open and reset
-  effect(() => {
-    if (this.open()) {
-      this.overlayOpen.set(true);
-      this.animationsCompleted.set(0);
-    }
-  });
-
-  // Effect 2: Close when both complete
-  effect(() => {
-    if (this.animationsCompleted() === 2 && !this.open()) {
-      this.overlayOpen.set(false);
-      this.animationsCompleted.set(0);
-    }
-  });
-
-  // Effect 3: Attach/detach CDK overlay
-  effect(() => {
-    if (this.overlayOpen()) {
-      this.attachDialog();
-    } else {
-      this.detachDialog();
-    }
-  });
-}
-
-// Both animations signal completion
-onDialogAnimationComplete(): void {
-  if (!this.open()) {
-    this.animationsCompleted.update(n => n + 1);
-  }
-}
-
-onBackdropAnimationComplete(): void {
-  if (!this.open()) {
-    this.animationsCompleted.update(n => n + 1);
-  }
-}
-```
-
-**Improvements:**
-
-1. Both animations event-driven
-2. No timing assumptions
-3. Handles browser rendering variations
-4. Explicit completion signals
-5. Extensible (easy to add more animations)
-6. Signal-based reactivity
-7. Clean cycle management
-
-## Key Design Decisions
-
-### 1. Provider Owns Everything
-
-**Decision:** `ScAlertDialogProvider` manages state, overlay lifecycle, backdrop, and focus trap
-
-**Why:**
-
-- Provider controls _when_ content appears (open state)
-- Provider controls _where_ content appears (CDK overlay)
-- Single component owns the full lifecycle — no coordination between sibling components
-- `ScAlertDialogPortal` directive just marks _what_ content to portal — no logic
-
-### 2. `display: contents` on Provider
-
-**Decision:** Provider uses `display: contents` to be invisible to CSS layout
-
-**Why:**
-
-- Provider is a `<div>` (required for CDK overlay's `ViewContainerRef`)
-- But it shouldn't affect the consumer's layout
-- `display: contents` makes the element's box disappear while keeping children in flow
-- Consumer can place trigger and other content without layout interference
-
-### 3. No Backdrop Click / Escape Handlers
-
-**Decision:** Alert dialog does not close on backdrop click or Escape key
-
-**Why:**
-
-- Alert dialogs require explicit user action (Cancel or Action button)
-- This follows WAI-ARIA alert dialog best practices
-- Prevents accidental dismissal of critical confirmations
-- Unlike `ScDialogProvider`, the provider does not subscribe to `overlayRef.backdropClick()` or `overlayRef.keydownEvents()`
-
-### 4. Separation of Logical and Physical State
-
-**Decision:** Split logical state (`open`) from physical state (`overlayOpen`)
-
-**Why:**
-
-- Logical state drives animations
-- Physical state drives DOM lifecycle
-- Animations need time to complete before DOM removal
-- Clean separation makes flow easier to understand
-
-### 5. Signal Counter Pattern
-
-**Decision:** Use signal counter to track multiple animation completions
-
-**Why:**
-
-- Both animations explicitly signal completion
-- No timing assumptions or hardcoded delays
-- Reactive: effect triggers when counter reaches target
-- Extensible: easy to add more animations (increase target)
-- Debuggable: counter value visible in Angular DevTools
-
-### 6. Event-Driven Completion
-
-**Decision:** Both dialog and backdrop emit completion events
-
-**Why:**
-
-- Precise: no guessing when animations finish
-- Robust: handles browser timing variations
-- Decoupled: backdrop component remains reusable
-- No arbitrary timeouts or magic numbers
-
-### 7. Guard Pattern for Counter Increments
-
-**Decision:** Check `!open()` before incrementing animation counter
-
-**Why:**
-
-- Prevents counter increments during new open cycle
-- User might reopen during close animation
-- Without guard, counter would increment incorrectly for new cycle
-- Example: Close starts → dialog completes → user reopens → backdrop completes would incorrectly increment counter for new open
-- Effect checks both counter AND `!open()` for safety
-
-### 8. Effect-Based Reactivity
-
-**Decision:** Use Angular effects instead of manual subscriptions
-
-**Why:**
-
-- Automatic cleanup on component destruction
-- Declarative: describes "what" not "how"
-- Runs automatically when dependencies change
-- Easier to reason about than imperative code
-
-## Animation Classes Reference
-
-### Dialog Content Classes
-
-```typescript
-// Idle state (hidden)
-'data-idle:opacity-0';
-
-// Entry animation (via data-open)
-'data-open:animate-in data-open:fade-in-0 data-open:zoom-in-95';
-
-// Exit animation (via data-closed)
-'data-closed:animate-out data-closed:fade-out-0 data-closed:zoom-out-95';
-```
-
-### Backdrop Classes
-
-```typescript
-// Idle state (hidden)
-'data-idle:opacity-0';
-
-// Entry animation (via data-open)
-'data-open:animate-in data-open:fade-in-0';
-
-// Exit animation (via data-closed)
-'data-closed:animate-out data-closed:fade-out-0';
-```
-
-## Accessibility Considerations
-
-The animation system preserves accessibility:
-
-1. **Focus Management:** Dialog auto-focuses on mount via `cdkTrapFocus` with `cdkTrapFocusAutoCapture`
-2. **ARIA Attributes:** Set before animations start (`role="alertdialog"`, `aria-modal="true"`)
-3. **Screen Readers:** Announce dialog immediately (not after animation)
-4. **No Escape Dismiss:** Escape key does NOT close the alert dialog — user must choose an action
-5. **No Backdrop Dismiss:** Clicking outside does NOT close the alert dialog — user must choose an action
-6. **Reduced Motion:** Could add `@media (prefers-reduced-motion)` support
-
-## Performance Considerations
-
-### Efficient Rendering
-
-- Uses `ChangeDetectionStrategy.OnPush` everywhere
-- Effects only run when dependencies change
-- No manual subscriptions to manage
-- Single overlay instance reused
-
-### Animation Performance
-
-- CSS animations (GPU accelerated)
-- Opacity and transform (composited properties)
-- No layout thrashing
-- Minimal JavaScript during animation
-
-### Memory Management
-
-- Effects auto-cleanup on destroy
-- No timeout leaks (event-driven approach)
-- Overlay detached after use
-- No memory leaks
-
-## Consumer API
-
-```html
-<div sc-alert-dialog-provider [(open)]="isOpen">
-  <button sc-alert-dialog-trigger sc-button>Delete</button>
-  <ng-template scAlertDialogPortal>
-    <div sc-alert-dialog>
-      <div sc-alert-dialog-header>
-        <h2 sc-alert-dialog-title>Are you sure?</h2>
-        <p sc-alert-dialog-description>This action cannot be undone.</p>
-      </div>
-      <div sc-alert-dialog-footer>
-        <button sc-alert-dialog-cancel sc-button>Cancel</button>
-        <button sc-alert-dialog-action sc-button>Continue</button>
-      </div>
-    </div>
-  </ng-template>
-</div>
-```
-
-**Key points:**
-
-- `scAlertDialogPortal` on `ng-template` marks lazy content
-- Content is only instantiated when dialog opens
-- `ScAlertDialogPortal` must be imported in the consumer's `imports` array
-- `[(open)]` provides two-way binding for programmatic control
-- No close button, escape, or backdrop click — user must choose Cancel or Action
-
-## Summary
-
-The alert-dialog animation architecture achieves smooth, reliable animations through:
-
-1. **Two-signal pattern:** Separates intent (`open`) from DOM lifecycle (`overlayOpen`)
-2. **Signal counter coordination:** Tracks completion of multiple animations (`animationsCompleted`)
-3. **Event-driven completion:** Both dialog and backdrop explicitly signal when done
-4. **Reactive updates:** Effects respond to state changes automatically
-5. **Robust timing:** No assumptions, handles browser variations
-6. **Centralized ownership:** Provider owns all lifecycle logic; portal directive is just a content marker
-
-This architecture provides:
-
-- Reliable animation completion detection
-- Clean separation of concerns
-- Extensibility (easy to add more animations)
-- No race conditions or timing assumptions
-- Debuggable signal-based state
-- Better user experience (smooth, never cut off)
-- Lazy content instantiation via `ng-template`