@wireai/activation 0.9.0 → 0.9.1

package/CHANGELOG.md

@@ -3,6 +3,45 @@
 All notable changes to `@wireai/activation` (formerly `wireai-onboarding`).
 Historical entries below the rename keep the old package name on purpose.
 
+## [0.9.1] — 2026-07-17
+
+### Fixed: the review-decision wire is now documented as it actually is
+
+No API change — `fetchReviewDecision` and `FetchReviewDecisionOptions` are byte-compatible
+with 0.9.0. What changes is that the kit stops asserting things about the server that are not
+true, and pins the wire with tests.
+
+- **The "prod 422s without `session_id`" comment was stale and is corrected.** The server
+  relaxed `session_id` to optional on 2026-07-16 and the relaxation **is deployed**: the live
+  route declares `session_id` as `required: false`, and an unauthenticated call carrying no
+  params at all answers `401`, not `422` — query validation runs before the handler's auth
+  check, so a required param would have 422'd first. A session-less review gate reaches the
+  firing brain today.
+- **`FetchReviewDecisionOptions` stays closed at `sessionId` / `deviceKey` — deliberately.**
+  The deployed `GET /v1/reviews/decision` declares exactly those two query params plus the
+  `Authorization` header. Hosts that hand-rolled this fetch invented `user_id` and
+  `session_count` params on the belief that "the server ignores what it doesn't read, so
+  passing it is always safe". They are no-ops: the route declares neither, and `session_count`
+  appears nowhere in the deployed API. Adding them to the kit would have made the call site
+  read as though identity and a session counter reach the firing brain when neither does.
+  Identity goes in `deviceKey`; a client-side session floor is `ReviewConfig.minSessions`.
+- **`arm` is documented as load-bearing.** `fetchReviewDecision` already returns
+  `ReviewDecisionResponse` (`{fire, reason, arm}`). Narrowing it to `{fire, reason}` on the way
+  to the gate silently kills per-arm attribution across a reweighting; the docs now say so and
+  a regression test pins it.
+- **`timeoutFallbackMs` is surfaced where the race actually happens.** It already exists on
+  `ReviewConfig` and is fully implemented in `useReviewGate` (local rules stay parked until the
+  decision lands or the window expires). The transport docs now point at it, because a host
+  running its own dwell timer in parallel with the fetch builds a race a slow server loses — an
+  in-flight `{fire:false}` arrives after the local timer already showed the prompt.
+
+### Added
+
+- `src/reviews/transport.test.ts` — the transport had **no test file at all**. 11 tests pin the
+  wire contract (only `session_id` + `device_key` are sent; a session-less call is legal), the
+  incident semantics (`{fire:false}` survives, never collapsed to null; `arm` survives), and
+  "no opinion is the only null" (non-2xx / non-boolean `fire` / unreachable → `null`).
+
 ## [0.1.0] — 2026-07-12
 
 ### Renamed: `wireai-onboarding` is now `@wireai/activation`

package/dist/analytics/index.d.mts

@@ -1,4 +1,4 @@
-export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-f5VVB5hH.mjs';
+export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-Bzb-bcB2.mjs';
 import { W as WireUserContext, E as EventQueueOptions } from '../currentSession-Bs2JfTJ8.mjs';
 export { A as AnalyticsEvent, C as ClientEvent, a as ClientEventTarget, b as ClientEventType, c as ContextEnvelope, d as ContextEnvelopeInput, e as EnvelopeSource, f as EventQueue, g as WIRE_ONBOARDING_EVENTS, h as WireOnboardingEventName, i as buildContextEnvelope, j as createEventQueue, k as getCurrentSessionId, m as makeSessionId, r as reportClientEvent, l as reportClientEvents, n as resetCurrentSessionId, s as setCurrentSessionId, t as toAnalyticsEvent } from '../currentSession-Bs2JfTJ8.mjs';
 import '../types-CNUqMK0D.mjs';

package/dist/analytics/index.d.ts

@@ -1,4 +1,4 @@
-export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-DzU-TqZz.js';
+export { R as ReportAppEventOptions, r as reportAppEvent } from '../transport-B31G0Cib.js';
 import { W as WireUserContext, E as EventQueueOptions } from '../currentSession-61dcm3V-.js';
 export { A as AnalyticsEvent, C as ClientEvent, a as ClientEventTarget, b as ClientEventType, c as ContextEnvelope, d as ContextEnvelopeInput, e as EnvelopeSource, f as EventQueue, g as WIRE_ONBOARDING_EVENTS, h as WireOnboardingEventName, i as buildContextEnvelope, j as createEventQueue, k as getCurrentSessionId, m as makeSessionId, r as reportClientEvent, l as reportClientEvents, n as resetCurrentSessionId, s as setCurrentSessionId, t as toAnalyticsEvent } from '../currentSession-61dcm3V-.js';
 import '../types-Buj9Lw9t.js';