@frame-kit/ui-ng-patterns 0.1.20 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@frame-kit/ui-ng-patterns",
-  "version": "0.1.20",
+  "version": "0.2.1",
   "description": "Opinionated, dashboard-ready Angular component patterns composed from @frame-kit/ui-ng.",
   "license": "MIT",
   "repository": {
@@ -17,7 +17,7 @@
     "@angular/forms": "^21.2.0",
     "@angular/platform-browser": "^21.2.0",
     "@angular/router": "^21.2.0",
-    "@frame-kit/ui-ng": "0.1.20",
+    "@frame-kit/ui-ng": "0.2.1",
     "rxjs": "^7.0.0"
   },
   "sideEffects": false,

package/types/frame-kit-ui-ng-patterns-dashboard.d.ts

@@ -664,6 +664,14 @@ interface Point {
  * and can be dragged around (CDK drag). It renders over the app in a fixed
  * layer — drop it once near the app root.
  *
+ * **Presentational, not clever.** It renders exactly what it is given and
+ * reports what the user did — it derives no step state of its own. Which step
+ * is open (`openStepId`), which are done or pending (`steps`), whether it is
+ * collapsed (`collapsed`): all inputs. When a step should advance, when a
+ * context switch should re-focus the guide, when a choice has gone stale —
+ * all consumer decisions, because the consumer knows *what changed*, while
+ * the widget only ever sees a new array.
+ *
  * **Controlled model, no domain data.** The `steps` model is a required,
  * reactive input: the widget is a pure view of it and emits events when the
  * user acts (`stepAction`, `stepMarkDone`, `stepSecondaryAction`,
@@ -671,9 +679,9 @@ interface Point {
  * it is keyed by, say, the active account or environment, swapping the input
  * re-renders the widget instantly. The widget never persists step state.
  *
- * **Collapsed is a two-way model.** Bind `[(collapsed)]` (or listen to
- * `collapsedChange`) to drive the card ↔ pill swap from outside — e.g. an
- * auto-open policy. Left unbound, the widget manages it internally.
+ * **Collapsed and openStepId are two-way models.** Bind `[(collapsed)]` /
+ * `[(openStepId)]` to drive the card ↔ pill swap and the expanded row from
+ * outside; the widget writes them only in response to a direct user action.
  *
  * **Container-aware.** `boundary` (a selector or element) confines both
  * dragging and the widget's resting position to a region of the app — e.g. a
@@ -800,20 +808,14 @@ declare class OnboardingGuideComponent {
     /** The boundary element currently under observation (if any). */
     private observedBoundary;
     /**
-     * Last seen completion signature (step ids + done states) — the accordion
-     * reset skips the first run and cosmetic-only model updates.
-     */
-    private prevCompletionSignature;
-    /**
-     * The expanded step. Two-way bindable so a consumer can spotlight a
-     * specific step (e.g. a "complete this section" banner). `undefined` means
-     * "follow the default" — the first incomplete step. User toggles (and
-     * consumer writes) override the default until the `steps` model changes,
-     * which resets the choice so the guide re-focuses the next piece of work.
+     * The expanded step, or `null` for none. Fully controlled: the widget
+     * writes it only when the user toggles a row, and never infers a value
+     * of its own — which step should be open, when to advance to the next
+     * one, and whether a context switch should re-focus the guide are all
+     * decisions the consumer owns (it knows what changed; the widget only
+     * sees a new array).
      */
-    readonly openStepId: _angular_core.ModelSignal<string | null | undefined>;
-    /** The step actually expanded: the explicit choice, or the default. */
-    protected readonly resolvedOpenStepId: _angular_core.Signal<string | null>;
+    readonly openStepId: _angular_core.ModelSignal<string | null>;
     protected readonly total: _angular_core.Signal<number>;
     protected readonly doneCount: _angular_core.Signal<number>;
     protected readonly percent: _angular_core.Signal<number>;