@ai-matrx/messaging 0.1.1 → 0.1.2

package/CHANGELOG.md

@@ -1,5 +1,40 @@
 # Changelog — `@ai-matrx/messaging`
 
+## 0.1.2 — 2026-08-31
+
+**Typing, presence and message broadcast work.** The root defect was in `@ai-matrx/realtime`
+(every channel got a unique instance topic, and for broadcast/presence the topic IS the room);
+this package found it, and it is fixed in realtime 0.2.0. These are the consumer-side changes
+that fix came with — both of them real defects this package was carrying.
+
+### Fixed
+
+- **One presence publisher per conversation.** One channel carries ONE presence entry per key, so
+  `useTypists` and `useOnlineUserIds` now read the roster with `presence: { publish: false }`.
+  The composer — which actually knows whether this user is typing — is the single publisher. Two
+  publishers overwrote each other on every heartbeat.
+- **One composer per conversation, so REPLY works.** `ConversationView` called `useComposer` and
+  also rendered `<Composer>`, which called it again: two independent drafts, two independent
+  reply targets — picking "reply" on a message set it on an instance the composer's reply bar
+  never read — and two typing publishers. The view now owns the state and renders `ComposerView`;
+  the exported `Composer` is unchanged for standalone use.
+- **A broadcast message one field short no longer takes down the thread.** `useMessageAction`
+  reads `message.action ?? null` instead of assuming the field is present; an off-shape wire
+  payload used to throw `undefined.kind` and unmount the conversation.
+
+### Added
+
+- `src/react/realtime-rooms.test.tsx` — renders the real `ConversationView` against a shared,
+  topic-deduping fake Supabase client and proves every holder of the conversation topic lands on
+  ONE live channel named as declared (0.1.1 produced five), a remote typist reaches the
+  indicator, a remote broadcast reaches the thread, and exactly one holder publishes presence.
+  All four fail against `@ai-matrx/realtime` 0.1.1.
+
+### Consumer action (C28)
+
+None. No public API changed. `@ai-matrx/realtime` >= 0.2.0 is required and is picked up
+automatically by the `"latest"` spec.
+
 ## 0.1.1 — 2026-08-31
 
 Caught in review immediately after 0.1.0 published.

package/dist/react.cjs

@@ -2125,7 +2125,12 @@ function useTypists(conversationId, participants) {
   const typing = (0, import_react4.useTyping)(
     {
       topic: conversationId === null ? "" : conversationTopic(conversationId),
-      identity: { userId: host?.identity.userId ?? "" }
+      identity: { userId: host?.identity.userId ?? "" },
+      // READ-ONLY. This label and `useComposer` sit on the SAME topic, which is
+      // one channel carrying ONE presence entry per key — so exactly one of
+      // them publishes, and it is the composer that actually knows whether this
+      // user is typing. Publishing here would overwrite that on every heartbeat.
+      publish: false
     },
     { enabled: conversationId !== null && host !== null }
   );
@@ -2152,7 +2157,10 @@ function useOnlineUserIds(conversationId) {
   const presence = (0, import_react4.usePresence)(
     {
       topic: conversationId === null ? "" : conversationTopic(conversationId),
-      presence: { state: { userId: host?.identity.userId ?? "" } }
+      // READ-ONLY, for the same reason: `useComposer`'s typing presence already
+      // puts this user in the roster under this key with their `userId`, and a
+      // second publisher on one entry just fights it.
+      presence: { publish: false, state: { userId: host?.identity.userId ?? "" } }
     },
     { enabled: conversationId !== null && host !== null }
   );
@@ -2233,7 +2241,7 @@ function useMessagingAi(conversationId) {
 }
 function useMessageAction(message) {
   const host = useRequiredMessagingHost();
-  const action = message.action;
+  const action = message.action ?? null;
   const [receipt, setReceipt] = (0, import_react3.useState)(
     () => action === null ? null : host.actions.receiptFor(action.kind, message.id, host.identity.userId)
   );
@@ -2765,7 +2773,7 @@ function ConversationView(props) {
       /* @__PURE__ */ (0, import_jsx_runtime4.jsx)(TypingDots, {}),
       typists.label
     ] }) : null }),
-    /* @__PURE__ */ (0, import_jsx_runtime4.jsx)(Composer, { conversationId })
+    /* @__PURE__ */ (0, import_jsx_runtime4.jsx)(ComposerView, { composer, disabled: false })
   ] });
 }
 function MessageGroupView(props) {
@@ -2898,6 +2906,10 @@ function MessageActionChips(props) {
 }
 function Composer(props) {
   const composer = useComposer(props.conversationId);
+  return /* @__PURE__ */ (0, import_jsx_runtime4.jsx)(ComposerView, { composer, disabled: props.conversationId === null });
+}
+function ComposerView(props) {
+  const composer = props.composer;
   const textareaRef = (0, import_react5.useRef)(null);
   (0, import_react5.useEffect)(() => {
     const node = textareaRef.current;
@@ -2931,7 +2943,7 @@ function Composer(props) {
           value: composer.value,
           placeholder: "Message",
           "aria-label": "Message",
-          disabled: props.conversationId === null,
+          disabled: props.disabled,
           onChange: (event) => {
             composer.setValue(event.target.value);
             composer.onKeystroke();