@stapel/chat-react 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1 +1,50 @@
 # @stapel/chat-react
+
+## 0.2.0
+
+### Minor Changes
+
+- ca35e19: New pair: `@stapel/chat-react` — the React half of `stapel-chat`, wiring both
+  of its transports behind one seam.
+
+  The storefront spec ruled polling-only for chat v1, and it was right about the
+  fleet it surveyed: the resumable consumer existed but `stapel_chat.routing`
+  exported nothing, so no host could mount it. stapel-chat 0.2.2 ships that mount
+  (`ws/chat/<uuid:conversation_id>`). So this pair carries **two transports and
+  one seam** — `useChatFreshness(streamKey, mapToQueryKeys, { fallbackRefetchInterval })`,
+  deliberately the signature the realtime substrate reserves for
+  `useSignalInvalidate`:
+
+  - a typed client for the module's own protocol — `hello{last_seq}` → `welcome`
+    → replay → `replay_done` → live frames, seq-deduped on both ends, resume from
+    the cursor the STORE holds (not the one the socket opened with), `error{resync}`
+    forwarded verbatim, close codes 4401/4403 treated as answers rather than
+    faults (no reconnect), everything else reconnected with jittered backoff;
+  - polling by `seq`, visibility-aware, with exponential backoff on consecutive
+    failures — used whenever the socket is not carrying the stream, and for the
+    inbox, which has no socket at all (the module fans out per thread).
+
+  Both ends do the same thing with what they learn: refetch the thread query,
+  whose query function advances the window BY SEQ
+  (`?direction=prev&anchor=<tip>`). The screens are written once and the tests
+  run against both transports. Writes never go over the socket: the `send` frame
+  is typed (a mirror must be complete) and never emitted, because its refusals
+  carry socket-local codes with no i18n key and no remediation, while
+  `POST …/messages` answers with the persisted row and a real error envelope.
+
+  Surface: `<ConversationList>` (server-computed unread counts, as a LoadState so
+  a badge cannot read "0" during an outage), `<ConversationThread>` (a contiguous
+  seq-ordered window — a hole is re-read, never stitched — with backfill and an
+  automatic, monotonic read marker), `<MessageComposer>` (code-point length
+  counting, so an emoji is one character on both sides of the wire), and
+  `<StartDirectChat>` — "message the seller", get-or-create over the module's own
+  participant-pair idempotency. An opt-in antd skin at `@stapel/chat-react/default`
+  and a member-surface nav entry.
+
+  Two contract facts recorded rather than papered over:
+  `CreateConversationRequest.scope_key` is ignored by the server, so a direct
+  thread cannot be scoped to a listing and the pair exposes no argument that
+  pretends otherwise; and stapel-chat ships no `translations/` directory, so the
+  pair authors ru/es for the twelve error keys the module owns (the
+  stapel-forms/stapel_attributes precedent) while the cross-cutting keys come from
+  stapel-core's catalogue.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Stapel contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/flows/freshness.js

@@ -4,11 +4,11 @@
  *
  * ── What changed since the spec ─────────────────────────────────────────────
  *
- * `tasks/darom-storefront-design.md` §3.6 ruled polling-by-seq for chat v1,
+ * The storefront spec §3.6 ruled polling-by-seq for chat v1,
  * and it was right about the fleet it surveyed: stapel-chat had the resumable
  * consumer but `routing.py` exported nothing, so no host could mount it.
  * stapel-chat 0.2.2 ships that mount (`ws/chat/<uuid:conversation_id>`) and
- * the darom fleet runs it. So the pair carries BOTH transports and picks at
+ * the client fleet runs it. So the pair carries BOTH transports and picks at
  * runtime — a deployment without sockets (WSGI, no channel layer, a
  * misconfigured proxy) is not a broken chat, it is a chat that refreshes on a
  * timer.

package/dist/model/runtime.d.ts

@@ -10,7 +10,7 @@ import type { ChatReconnectOptions, ChatWebSocketFactory } from "../realtime/cha
 export interface ChatRealtimeOptions {
     /**
      * Where this deployment mounts `stapel_chat.routing.websocket_urlpatterns`,
-     * e.g. `wss://darom.example/ws/chat/`. Omit to derive it from `baseUrl`
+     * e.g. `wss://shop.example/ws/chat/`. Omit to derive it from `baseUrl`
      * (the canonical `/ws/chat/` at the API's own origin). Pass `null` to turn
      * the socket transport OFF explicitly — a host that knows its backend runs
      * under WSGI says so here instead of letting every tab fail a handshake

package/llms.txt

@@ -1,4 +1,4 @@
-# @stapel/chat-react 0.1.0
+# @stapel/chat-react 0.2.0
 
 Headless React flow pair for stapel-chat (contract >=0.2 <0.3) — business + state, zero visual opinion.
 Built on @stapel/core: typed client + StapelApiError envelope, auth token refresh,

package/manifest.json

@@ -1,7 +1,7 @@
 {
   "$generated": "by scripts/gen-manifest.mjs — do not edit; drift-gated (pnpm gen:manifest:check)",
   "package": "@stapel/chat-react",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "backend": {
     "module": "stapel-chat",
     "contract": ">=0.2 <0.3"

package/nav-manifest.json

@@ -1,6 +1,6 @@
 {
   "package": "@stapel/chat-react",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "entries": [
     {
       "id": "chat.conversations",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stapel/chat-react",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Headless React pair for stapel-chat: typed API client, TanStack Query hooks, a seq-ordered thread store, and ONE transport seam behind which the module's own resumable WebSocket protocol (hello/welcome/replay/replay_done/message/error) and seq-anchored polling are interchangeable — the UI never knows which is live. Conversation list with unread badges, thread replay + live tail, REST send, direct-thread idempotency for \"message the seller\", monotonic read markers. Zero visual opinion in the main entry; an opt-in /default subpath ships the antd skin.",
   "license": "MIT",
   "repository": {
@@ -47,13 +47,6 @@
     "nav-manifest.json",
     "llms.txt"
   ],
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "test": "tsc -p tsconfig.demo.json && vitest run --exclude test/prodBundlePurity.test.ts",
-    "test:pack": "vitest run test/prodBundlePurity.test.ts",
-    "lint": "eslint .",
-    "size": "size-limit"
-  },
   "size-limit": [
     {
       "name": "index — headless pair (client + hooks + thread store + transport seam)",
@@ -89,9 +82,6 @@
   },
   "devDependencies": {
     "@size-limit/preset-small-lib": "^11.2.0",
-    "@stapel/core": "workspace:^",
-    "@stapel/showcase": "workspace:^",
-    "@stapel/tokens": "workspace:^",
     "@tanstack/react-query": "^5.81.0",
     "@testing-library/react": "^16.3.0",
     "@types/react": "^19.1.0",
@@ -103,12 +93,22 @@
     "react-dom": "^19.1.0",
     "size-limit": "^11.2.0",
     "typescript": "^5.8.3",
-    "vitest": "^3.2.4"
+    "vitest": "^3.2.4",
+    "@stapel/core": "^0.15.0",
+    "@stapel/showcase": "^0.2.0",
+    "@stapel/tokens": "^0.5.0"
   },
   "engines": {
     "node": ">=22"
   },
   "publishConfig": {
     "access": "public"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "test": "tsc -p tsconfig.demo.json && vitest run --exclude test/prodBundlePurity.test.ts",
+    "test:pack": "vitest run test/prodBundlePurity.test.ts",
+    "lint": "eslint .",
+    "size": "size-limit"
   }
-}
+}

package/src/analytics/generated/events.json

@@ -1,7 +1,7 @@
 {
   "$generated": "by scripts/gen-events.mjs — do not edit; drift-gated (pnpm gen:events:check)",
   "package": "@stapel/chat-react",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "defined": [],
   "flows": []
 }