@ai-matrx/messaging 0.4.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,84 @@
 # Changelog — `@ai-matrx/messaging`
 
+## 0.7.0 — 2026-09-07
+
+🚨 **Every RPC in this package was calling the wrong schema, so every read failed against the
+live database.** Found the first time the package ran a real query — the honest verification the
+work order named, which is also why no source gate could have caught it.
+
+### Fixed
+
+- **RPCs are called on `public`; only the TABLES are in `communication`.** Matrx Main's messaging
+  tables moved into `communication` during the schema reorg, and the five auth-checked SECURITY
+  DEFINER functions stayed in `public` where PostgREST exposes them by default and where every
+  existing caller and GRANT already pointed. This package sent both to `communication`, so the
+  inbox read, the direct-conversation get-or-create, the unread count, the profile read and the
+  participant check all failed with PGRST202 — *"Could not find the function
+  communication.get_dm_conversations_with_details … in the schema cache"*. The whole product was
+  dead against the real database while 129 tests and a packed-tarball canary stayed green,
+  because a fake PostgREST answers whatever schema it is asked for.
+- New constant `MESSAGING_RPC_SCHEMA` (`"public"`), exported and asserted by the tarball canary
+  beside `MESSAGING_SCHEMA`, with the verification query in a comment above it. A regression test
+  proves the RPC lands on `public` and the table write on `communication`; it fails when the two
+  are collapsed.
+
+**The lesson, recorded where the next agent will read it:** "verified against the live schema by
+inspection" is not verification. One query would have found this on day one.
+
+### Consumer action (C28)
+
+None. Nothing in the API changed — the package simply works against the real database now.
+
+## 0.6.0 — 2026-09-07
+
+**The two entries did not agree on their own branded ids.** A consumer that minted a
+`ConversationId` with `asConversationId` from `@ai-matrx/messaging` could not pass it to a hook
+from `@ai-matrx/messaging/react` — the two were different types, with an error message that
+blames the consumer. Found by the first real adoption, which does exactly that on its
+conversation route.
+
+### Fixed
+
+- **The nominal brand is a named marker, not a `unique symbol`.** The package ships two entries
+  built as two bundles, so every shared type is DECLARED TWICE in the shipped `.d.ts` — and two
+  `declare const brand: unique symbol` declarations are two different symbols, hence two
+  incompatible `ConversationId`s. A structural marker (`__mxBrand`) is identical in both
+  declarations, so the brands unify while still being impossible to produce by accident. No
+  runtime change: the marker is types-only.
+- **`verify-tarball` now typechecks a real consumer against BOTH entries** — core-minted ids
+  assigned to `/react` types and back. It fails against the `unique symbol` build, which is the
+  only way this class can be caught: in `src/` there is only ever one declaration, so every
+  source gate stays green while the shipped types are broken.
+- The canary still imported `getInitials` / `avatarPaletteIndex`, which moved to
+  `@ai-matrx/kit/format` in 0.5.0 — it would have failed that release's publish.
+
+### Consumer action (C28)
+
+None. `asConversationId(...)` and friends behave exactly as before; ids from the two entries now
+actually interoperate, which is what the types always claimed.
+
+## 0.5.0 — 2026-09-07
+
+**Consumer action (C28).** Two exports MOVED OUT of this package to
+`@ai-matrx/kit/format`. Update the import; the behaviour is identical.
+
+| was | now |
+|---|---|
+| `import { getInitials } from "@ai-matrx/messaging"` | `import { getInitials } from "@ai-matrx/kit/format"` |
+| `import { avatarPaletteIndex } from "@ai-matrx/messaging"` | `import { avatarPaletteIndex } from "@ai-matrx/kit/format"` |
+
+**Why.** Duplication census finding H1 (2026-09-07): both bodies were
+duplicated in `@ai-matrx/meet`, and while two packages claimed them no host
+twin had a correct owner to point at. They now live in `@ai-matrx/kit`, which
+has zero sibling dependencies.
+
+The conversation-shaped formatters — `formatConversationTime`,
+`formatMessageTime`, `formatDateSeparator`, `formatLastSeen`, `formatTypists`,
+`groupMessages`, `isSameDay`, `participantNames` — all stay here. Nothing is
+re-exported: this package imports kit directly.
+
+New dependency: `@ai-matrx/kit` (`latest`).
+
 ## 0.4.0 — 2026-09-07
 
 **A ```matrx fence written in the PLATFORM's dialect was being deleted on render.** Found the

package/README.md

@@ -314,7 +314,8 @@ One canonical schema, in Matrx Main, under the platform's DB conventions:
 
 | | |
 |---|---|
-| Schema | `communication` (never `public`) |
+| Table schema | `communication` (never `public`) |
+| RPC schema | `public` — the SECURITY DEFINER functions stayed there through the schema reorg. The two DIFFER, deliberately; collapsing them fails every read with PGRST202 |
 | Tables | `dm_conversations`, `dm_conversation_participants`, `dm_messages` |
 | RPCs | `dm_get_or_create_direct_conversation`, `get_dm_conversations_with_details`, `get_dm_user_info`, `get_dm_unread_count`, `is_dm_participant` |
 

package/dist/index.cjs

@@ -21,6 +21,7 @@ var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: tru
 var src_exports = {};
 __export(src_exports, {
   MESSAGING_EVENTS: () => MESSAGING_EVENTS,
+  MESSAGING_RPC_SCHEMA: () => MESSAGING_RPC_SCHEMA,
   MESSAGING_SCHEMA: () => MESSAGING_SCHEMA,
   MessagingError: () => MessagingError,
   RPCS: () => RPCS,
@@ -30,7 +31,6 @@ __export(src_exports, {
   asMessageId: () => asMessageId,
   asOrganizationId: () => asOrganizationId,
   asUserId: () => asUserId,
-  avatarPaletteIndex: () => avatarPaletteIndex,
   composeFence: () => composeFence,
   conversationTopic: () => conversationTopic,
   createActionRegistry: () => createActionRegistry,
@@ -48,7 +48,6 @@ __export(src_exports, {
   formatLastSeen: () => formatLastSeen,
   formatMessageTime: () => formatMessageTime,
   formatTypists: () => formatTypists,
-  getInitials: () => getInitials,
   groupMessages: () => groupMessages,
   inboxTopic: () => inboxTopic,
   invalidResponse: () => invalidResponse,
@@ -1496,20 +1495,6 @@ function formatDateSeparator(isoString, now = Date.now(), locale) {
     day: "numeric"
   });
 }
-function getInitials(name) {
-  const parts = name.trim().split(/\s+/).filter(Boolean);
-  if (parts.length === 0) return "?";
-  const first = parts[0]?.[0] ?? "";
-  const last = parts.length > 1 ? parts.at(-1)?.[0] ?? "" : "";
-  return `${first}${last}`.toUpperCase() || "?";
-}
-function avatarPaletteIndex(seed, buckets = 8) {
-  let hash = 0;
-  for (let index = 0; index < seed.length; index += 1) {
-    hash = hash * 31 + seed.charCodeAt(index) | 0;
-  }
-  return Math.abs(hash) % buckets;
-}
 function groupMessages(messages, args = {}) {
   const windowMs = args.windowMs ?? 5 * MINUTE;
   const now = args.now ?? Date.now();
@@ -1556,6 +1541,7 @@ function formatLastSeen(lastSeenMs, now = Date.now()) {
 
 // src/core/repository.ts
 var MESSAGING_SCHEMA = "communication";
+var MESSAGING_RPC_SCHEMA = "public";
 var TABLES = {
   conversations: "dm_conversations",
   participants: "dm_conversation_participants",
@@ -1590,6 +1576,7 @@ function createMessagingRepository(options) {
     ...options.now !== void 0 ? { now: options.now } : {}
   });
   const db = () => client.schema(MESSAGING_SCHEMA);
+  const rpcDb = () => client.schema(MESSAGING_RPC_SCHEMA);
   async function withSessionRetry(operation, run) {
     try {
       return await run();
@@ -1607,7 +1594,7 @@ function createMessagingRepository(options) {
     }
   }
   async function rpc(fn, args, operation) {
-    const { data, error } = await db().rpc(fn, args);
+    const { data, error } = await rpcDb().rpc(fn, args);
     if (error !== null) throw normalizeMessagingError(error, operation);
     return data;
   }