kaafil-react-uikit 0.9.0 → 0.10.1

package/CHANGELOG.md

@@ -6,6 +6,129 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 While on `0.x` a minor bump may carry a breaking change; the entry will say so.
 
+## [0.10.1] — 2026-09-15
+
+Two long-standing bugs that only bite together, found when the traveller
+surface of that same partner CRM went blank on a **production** build.
+
+### Fixed
+
+- **`isDevelopment()` answered `true` in every production browser build.**
+  It read `(globalThis as {...}).process?.env?.NODE_ENV`, on the reasoning
+  that a bundler "sees this exact property-access shape and inlines it the
+  same way it would a bare reference". It does not — Vite, webpack, Turbopack
+  and esbuild all match the literal member expression `process.env.NODE_ENV`,
+  and route it through `globalThis` or an optional chain and nothing is
+  replaced. A browser has no `process`, so the expression was `undefined`,
+  `undefined !== 'production'` is `true`, and **every dev-only throw in this
+  package shipped to real users**. It now reads a bare `process.env.NODE_ENV`
+  (declared locally, so still no `@types/node`) and fails CLOSED: a value it
+  cannot read means production, because a false positive here does not
+  produce a stray console line — it turns a guard meant to degrade quietly
+  into a crash.
+
+- **The session's open window no longer claims to be a manager.**
+  `SessionShell` populated `SessionContext` with `persona: 'manager'`
+  unconditionally while opening. On a share surface that is simply false: a
+  bare `shareToken` prop settles the persona synchronously, which is the whole
+  premise of the credential-shape model. It now derives `'share'` from the
+  prop and keeps the guess only for `credentialResolver`, which genuinely
+  cannot be known before it resolves.
+
+  Together these took out the entire traveller surface in production:
+  `BrandShell` rejects `headStrategy: 'own-page'` for any non-`share` persona,
+  that guard is written to warn and fall back outside development, and instead
+  it threw — so `/t/<token>`, the page a traveller opens from a WhatsApp
+  message, rendered nothing but an error boundary.
+
+## [0.10.0] — 2026-09-15
+
+Both changes came out of integrating a real partner CRM against the live
+engine; both are things a host hit before anybody here did.
+
+### Fixed
+
+- **Every directly-exported composite now waits for the session.**
+  `SessionShell` renders its children throughout the async open window with
+  `SessionContext` populated but no client yet, so any client-backed hook
+  called in that window throws:
+
+  ```
+  useKaafilClient() was called outside a <SessionShell>
+  ```
+
+  — which is a misleading message for a timing problem. The shell is right
+  there; it has nothing to hand down yet.
+
+  `KaafilAgencyWorkspace`, `KaafilManagerApp`, `KaafilShareView` and two
+  Manager sections already guarded with a two-component split. Thirty-one
+  other exports did not, and were safe only because a gated Surface happened
+  to sit above them. `TripWorkspace` is the one a host actually mounts
+  directly — it is the right component when a CRM wants to keep its own
+  navigation — and it threw every time.
+
+  What made it expensive to diagnose: the child throws, `ErrorShell` catches
+  it, the subtree unmounts, and the effect that would have opened the session
+  never runs. The network tab shows **no request at all**, which reads like a
+  broken credential rather than a race.
+
+  `TripWorkspace` renders its own skeleton while opening; the rest render
+  `null`, matching the five that were already gated.
+
+### Added
+
+- **`installKaafilOfflineShell` gained `isHostOwned`**, defaulting to
+  same-origin. The handler previously claimed every non-API GET including
+  cross-origin ones, so a third-party font or beacon went through a cache
+  lookup that could never hit — and, because the first `respondWith` wins, a
+  host's own `fetch` listener could never answer for it.
+
+- **`installKaafilOfflineShell` gained `runtimeCache`**, default `false`.
+  When on, a successful same-origin miss is written to the cache so the next
+  offline load can serve it. Only `ok`, `basic` responses are stored: a
+  pinned 404 outlives the mistake, and an opaque response cannot be read back
+  usefully. Off by default so `cacheName` stays the only revalidation knob.
+
+  Turn it on when enumerating your build is impractical — content-hashed
+  chunks you cannot list at worker-build time being the usual case.
+
+### Changed
+
+- **The offline shell's own documentation was wrong in two places**, which is
+  worth a changelog line because the fix is what the options above are for.
+  It claimed to call `respondWith` "only for requests it actually owns" — it
+  declines only non-GET, API and (now) cross-origin. And an inline comment
+  said a non-precached request was "left alone for the host's own handlers",
+  when it was in fact claimed, proxied, and returned without being cached.
+
+  The consequence the docs never stated: without `runtimeCache`, `precache`
+  is not a warm-up optimisation, it is the entire offline surface.
+
+- First tests for `src/offline/serviceWorker.ts`, which had none: eleven
+  covering what the handler claims and what a miss does.
+
+## [0.9.0] — 2026-09-14
+
+Backfilled — this version shipped without a changelog entry.
+
+### Added
+
+- **`kaafil-react-uikit/offline`**, the seventh subpath: `withCachedCredential`,
+  `localStorageCredentialStore` and `installKaafilOfflineShell`. The host's half
+  of offline — a credential that survives a reload, and a service-worker fetch
+  policy — in a module that imports neither React nor the SDK, so it can be
+  pulled into a worker bundle.
+
+### Changed
+
+- **`KaafilManagerApp`'s `onNavigateModule` is now optional.** The Surface
+  satisfies `ManagerNowSection`'s requirement itself; omit it and the
+  quick-link chips still work, you lose only the host-side hook.
+
+- `ShareLinkDialog` no longer labels a bare token "the new share link", and
+  warns in development when `buildShareUrl` is unset — the desk was showing an
+  operator a UUID they could not send anyone.
+
 ## [0.8.0] — 2026-09-14
 
 ### Added