@franzzemen/brokenstock-shell 0.1.2 → 0.2.0

package/fesm2022/franzzemen-brokenstock-shell.mjs

@@ -116,12 +116,28 @@ class AuthenticationService {
         return this.authenticated() && roleNames.some(r => this.userSession()?.roles.includes(r) === true);
     }
     /**
-     * Check whether the current session holds a plan-feature (truthy grant).
-     * Works for boolean features (`true`) and quantity features (limit > 0).
-     * e.g. `hasFeature('real-time')`.
+     * Is this BOOLEAN feature granted and on? e.g. `hasFeature('real-time')`.
+     *
+     * Strictly `=== true`, matching the back end's `hasFeature`. It used to be
+     * `!!this.features()[slug]`, which is NOT a valid entitlement test now that `0` is
+     * a real state: `Features` has FOUR states and truthiness collapses two of them.
+     *
+     *   - key absent → not granted (an upsell)
+     *   - `0`        → granted, ZERO allowance (a limit — a different product, and
+     *                  FALSY, so `!!` reported it as "not in your plan")
+     *   - `true`     → granted, unlimited
+     *   - `number`>0 → granted with that limit
+     *
+     * It also matters in the other direction: `!!` passed on any positive number, so a
+     * boolean slug misconfigured with a numeric value would show the affordance while
+     * the BE — which requires exactly `true` — refused every call behind it. The user
+     * sees the door and cannot open it.
+     *
+     * For QUANTITY features use {@link featureValue} and compare the limit yourself;
+     * this returns false for every numeric grant, including a valid one.
      */
     hasFeature(slug) {
-        return this.authenticated() && !!this.features()[slug];
+        return this.authenticated() && this.features()[slug] === true;
     }
     /** Raw plan-feature value (`true` for boolean grants, the numeric limit for quantity features, else undefined). */
     featureValue(slug) {