@revturbine/sdk 0.11.11 → 0.11.13

package/CHANGELOG.md

@@ -47,6 +47,92 @@ also require a changelog entry.
 
 ---
 
+## 0.11.13
+
+### Slot lifecycle events carry the slot's `route` (BL-0207, ruling D-30)
+
+**What changed.** Every slot lifecycle event (`slot_evaluated`, `slot_filled`,
+`slot_empty`, `slot_suppressed`, `slot_error`) now carries `route`: the app
+route the slot rendered on. Ingestion-driven surface-slot discovery reads it
+and persists it on the discovered slot. There is no SDK write to any CRUD
+route. The field is additive and optional in the scaffold contract
+(`slotContextBase.route`).
+
+A route is a **path, never a URL**. It has no origin, query string or
+fragment. The React layer computes it at emission time:
+
+- **Default:** `window.location.pathname`, with identifier-like segments
+  templated to `:id`. That covers numbers, UUIDs, long hex, prefixed ids like
+  `cus_…`, long opaque tokens and email-shaped values, raw or
+  percent-encoded. For example, `/accounts/4821/billing?coupon=X` reports
+  `/accounts/:id/billing`.
+- **`<RevTurbineRoute route={…}>`** (new, renderless) declares the framework
+  route pattern for its subtree, and the innermost boundary wins.
+- **Next.js App Router:** build the pattern with the new pure helper
+  `routePatternFromParams(usePathname(), useParams())`, which gives
+  `/projects/[projectId]/settings`. The SDK does not import `next/navigation`.
+
+Also new:
+
+- **Headless exports:** `normalizeSlotRoute`, `routePatternFromParams`,
+  `currentBrowserRoute`, `isIdentifierLikeSegment` and `SLOT_ROUTE_MAX_LENGTH`
+  (512).
+- **React hook:** `useSlotRoute()`.
+- **Headless controller option:** `PlacementControllerOptions.route` accepts a
+  string or a getter. When it is omitted, a headless controller emits
+  `route: null`.
+
+**Landed in:** 0.11.13 (`web-sdk` only; `server-python`/`server-rust` bumped
+in lockstep with no behavior change — no port emits slot events). The
+`@revt-eng/*` pins move to `0.1.366` (the scaffold contract: `slotContextBase.route`,
+`SurfaceSlotSchema.route`, and the `SurfaceSlotStatus` = `live | idle`
+vocabulary), and the vendored port types are re-synced — `SurfaceSlot.status`
+is now `SurfaceSlotStatus` (`live`/`idle`, default `idle`) in both ports.
+**Fail-closed in:** n/a (additive telemetry field).
+**Proving test:**
+- `web-sdk/slot-route.test.ts`: normalization, PII/query stripping, the
+  Next.js params recipe, and controller emission including the
+  throwing-getter case.
+- `web-sdk/react/usePlacement.route.test.tsx`: the plain-DOM pathname case and
+  the `<RevTurbineRoute>` Next.js pattern case.
+
+## 0.11.12
+
+### `builtin_dimensions` now reaches the browser SDK from the client-context fetch (BL-0312, plan 279 TASK-5)
+
+**What changed.** `0.11.11` (BL-0310/BL-0311) taught the shared evaluator to
+stamp `rt_<dimension>` segment traits from a `builtin_dimensions` object on the
+user context, but nothing yet delivered that object into `web-sdk`'s held
+context. `fetchClientContext` (`GET /api/sdk/client-context`) now maps the
+response's `builtin_dimensions` onto `RevTurbineUserContext.builtin_dimensions`,
+overlaying per leaf the same way it overlays `plan_handle`: a leaf the server
+evaluated on this fetch replaces the held value; a leaf it did not evaluate
+leaves whatever the app (or a prior fetch) had set untouched. A leaf absent on
+both sides stays absent — unknown is trait absence (plan 255), never a
+sentinel.
+
+The hash-skip that decides whether a fetch actually changed anything and
+should re-apply (and so re-evaluate segments) now accounts for
+`builtin_dimensions`. This surfaced a real gap: the shared
+`computeUserContextHash` helper re-projects its input to a fixed key set
+(`plan_handle`, `plan`, `usage`, `custom`, `trial`, `instances`) and silently
+drops anything outside it, so simply adding `builtin_dimensions` to the object
+passed to it was a no-op. `builtin_dimensions` is folded into the skip key as
+a literal suffix instead — the same technique already used for the coarse
+`payment_at_risk` signal, which has the identical problem.
+
+**Landed in:** 0.11.12 (`web-sdk` only; `server-python`/`server-rust` bumped
+in lockstep with no behavior change — the ports have no client-context fetch
+of their own and resolve built-ins only from an app-supplied
+`builtin_dimensions`, per plan 279's TASK-17 backlog note).
+**Fail-closed in:** 0.11.12. Before this release, a client-context response
+that changed only `builtin_dimensions` was hash-skipped and segments never
+re-evaluated against the new value.
+**Proving test:** `web-sdk/customer-side-client-context.test.ts`, describe
+block `builtin_dimensions (plan 279 AC-4)` — server-overlays-app, an
+unevaluated leaf survives, a changed value re-applies (new context object),
+an unchanged value does not.
+
 ## 0.11.11
 
 ### Built-in segment dimensions: reserved `rt_*` segment traits (BL-0310/BL-0311, plan 279 TASK-3/TASK-4)

package/dist/growthbook.d.ts

@@ -226,11 +226,11 @@ declare const UserPlanContextSchema: z.ZodObject<{
  */
 declare const UserBuiltinDimensionsSchema: z.ZodObject<{
     activity_level: z.ZodOptional<z.ZodEnum<{
-        inactive: "inactive";
         new: "new";
         high: "high";
         medium: "medium";
         low: "low";
+        inactive: "inactive";
     }>>;
     subscription_state: z.ZodOptional<z.ZodEnum<{
         trial: "trial";