@feelflow/ffid-sdk 5.7.0 → 5.9.0

package/dist/{types-s3y11uT6.d.ts → types-BYdtyO_2.d.ts}

@@ -33,22 +33,18 @@
  *   This is the FFID-internal runtime-expired case (see
  *   `getEffectiveSubscriptionStatus` on the server). Deny access.
  *
- * **SDK / server asymmetry — `active_canceling` is session-only (#3460).**
- * The backend `EffectiveSubscriptionStatus` in
- * `src/lib/common/subscription-helpers.ts` does NOT currently include
- * `active_canceling`; cancellation-scheduled subscriptions surface as plain
- * `'active'` on `/api/v1/subscriptions/ext/check` and `/oauth/userinfo`, and
- * consumers that branch on the server verdict will not see the new literal.
- * The SDK enriches `computeEffectiveStatusFromSession` with
- * `cancelAtPeriodEnd` (carried on `FFIDSubscription` for FFID backends from
- * #3460 onward — older backends omit the field and the helper defaults to
- * `false`, preserving the pre-#3460 `'active'` verdict) so `useSubscription`
- * can surface a "cancellation scheduled" badge without waiting for an
- * `/ext/check` round-trip. The asymmetry is safe because the new literal is
- * access-granting (no security regression on the userinfo path); when the
- * server's `EffectiveSubscriptionStatus` is later extended to emit
- * `active_canceling`, this docstring MUST be updated to drop the
- * session-only note.
+ * **`active_canceling` is mirrored on the server (#3464, SDK 5.8.0).**
+ * Earlier (#3460, SDK 5.7.0) the literal was a session-only enrichment;
+ * since FFID #3464 the backend `EffectiveSubscriptionStatus` and both
+ * `/api/v1/subscriptions/ext/check` + `/oauth/userinfo` emit
+ * `active_canceling` directly when `cancel_at_period_end=true` and the
+ * period is still live. SDK consumers receive the same literal whether
+ * they read it from the session-derived `computeEffectiveStatusFromSession`
+ * or the server-derived `effectiveStatus` on the userinfo / ext-check
+ * paths. Pre-#3464 FFID backends omit `cancelAtPeriodEnd` on the wire; the
+ * SDK `normalizeUserinfo` boundary defaults it to `false`, so downstream
+ * consumers see a plain boolean and `computeEffectiveStatus` returns the
+ * original `'active'` verdict for legacy deployments.
  *
  * @see /api/v1/subscriptions/ext/check
  * @see docs/03-implementation/EXPIRED_CONTRACT_HANDLING.md

package/dist/webhooks/index.d.cts

@@ -1,4 +1,4 @@
-import { E as EffectiveSubscriptionStatus } from '../types-s3y11uT6.cjs';
+import { E as EffectiveSubscriptionStatus } from '../types-BYdtyO_2.cjs';
 
 /**
  * FFID Webhook SDK Constants

package/dist/webhooks/index.d.ts

@@ -1,4 +1,4 @@
-import { E as EffectiveSubscriptionStatus } from '../types-s3y11uT6.js';
+import { E as EffectiveSubscriptionStatus } from '../types-BYdtyO_2.js';
 
 /**
  * FFID Webhook SDK Constants

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feelflow/ffid-sdk",
-  "version": "5.7.0",
+  "version": "5.9.0",
   "description": "FeelFlow ID Platform SDK for React/Next.js applications",
   "keywords": [
     "feelflow",