@dereekb/dbx-firebase 13.38.0 → 13.40.0

package/package.json

@@ -1,20 +1,20 @@
 {
   "name": "@dereekb/dbx-firebase",
-  "version": "13.38.0",
+  "version": "13.40.0",
   "peerDependencies": {
     "@angular/common": "21.2.11",
     "@angular/core": "21.2.11",
     "@angular/material": "^21.2.9",
-    "@dereekb/date": "13.38.0",
-    "@dereekb/dbx-analytics": "13.38.0",
-    "@dereekb/dbx-core": "13.38.0",
-    "@dereekb/dbx-form": "13.38.0",
-    "@dereekb/dbx-web": "13.38.0",
-    "@dereekb/firebase": "13.38.0",
-    "@dereekb/model": "13.38.0",
-    "@dereekb/rxjs": "13.38.0",
-    "@dereekb/util": "13.38.0",
-    "@dereekb/vitest": "13.38.0",
+    "@dereekb/date": "13.40.0",
+    "@dereekb/dbx-analytics": "13.40.0",
+    "@dereekb/dbx-core": "13.40.0",
+    "@dereekb/dbx-form": "13.40.0",
+    "@dereekb/dbx-web": "13.40.0",
+    "@dereekb/firebase": "13.40.0",
+    "@dereekb/model": "13.40.0",
+    "@dereekb/rxjs": "13.40.0",
+    "@dereekb/util": "13.40.0",
+    "@dereekb/vitest": "13.40.0",
     "@ng-forge/dynamic-forms": "0.10.0-next.4",
     "@ngrx/component-store": "^21.1.0",
     "firebase": "^12.12.1",

package/types/dereekb-dbx-firebase.d.ts

@@ -5228,10 +5228,12 @@ type DbxFirebaseNotificationHealthCheckProbeActionMap = NotificationDeliveryMeth
  * dialog, an admin view). The per-method test message actions are an input for the same reason: the
  * report renders them, whoever owns the store supplies them.
  *
- * The view is client-facing, so it shows only what the user can act on. The check's account-wide
- * findings (`is`), any method the system has no send service for, and the methods in
- * {@link HIDDEN_NOTIFICATION_DELIVERY_METHODS} are left out here — all of them remain on the check
- * itself for an API/callModel consumer.
+ * The view is client-facing, so it shows only what the user can act on. The account-wide findings
+ * (`is`) lead, because they are frequently the whole answer and no method section repeats them — a
+ * global opt-out or a disabled account leaves every method looking correctly configured. Any method
+ * the system has no send service for, and the methods in
+ * {@link HIDDEN_NOTIFICATION_DELIVERY_METHODS}, are left out — both remain on the check itself for an
+ * API/callModel consumer.
  */
 declare class DbxFirebaseNotificationHealthCheckComponent {
     private readonly _presentationService;
@@ -5242,6 +5244,14 @@ declare class DbxFirebaseNotificationHealthCheckComponent {
      * Left unset the report is read-only, which is what an admin or historical view wants.
      */
     readonly probeActions: i0.InputSignal<Maybe<Partial<Record<NotificationDeliveryMethod, Maybe<DbxFirebaseNotificationHealthCheckMethodProbeActionConfig>>>>>;
+    /**
+     * The account-wide findings, which apply however each individual method is configured.
+     *
+     * Shown in full rather than filtered: unlike a method section there is no "this channel is off"
+     * noise here, and an account-level finding is often the only explanation the report has — a global
+     * opt-out, a disabled account, or an unreadable auth record leaves every method looking fine.
+     */
+    readonly accountIssuesSignal: i0.Signal<_dereekb_firebase.NotificationHealthCheckIssue[]>;
     readonly statusColorSignal: i0.Signal<i1.DbxThemeColor>;
     readonly statusIconSignal: i0.Signal<string>;
     readonly statusLabelSignal: i0.Signal<string>;