@ai-matrx/messaging 0.7.0 → 0.9.0

package/CHANGELOG.md

@@ -1,5 +1,57 @@
 # Changelog — `@ai-matrx/messaging`
 
+## 0.9.0 — 2026-09-07
+
+**`<MessagingProvider client={supabase}>` did not typecheck for a host with generated Supabase
+types** — the one line the README tells every consumer to write.
+
+### Fixed
+
+- **The public `client` prop type is now shallow.** Checking a fully-typed
+  `SupabaseClient<Database>` against the rich internal shape makes tsc chase PostgREST's schema
+  machinery until it bails with `TS2589: Type instantiation is excessively deep and possibly
+  infinite`, followed by a page of "not assignable" — so the only way to pass the client a host
+  already has was the cast this package's own header forbids. The boundary is method names and
+  arity with `unknown` results; the rich contract (`MessagingSupabaseInternal`, formerly the
+  public type's body) is still what everything inside works against, and the provider narrows to
+  it ONCE, in-package. Same lesson as data 0.2.1: type a public boundary over `unknown`, never
+  over a strict recursive type the host's generator also produces.
+- **`createMessagingRepository` takes the same shallow client**, so the framework-free path a
+  service module uses (the README's "Outside React" section) compiles for the same host that the
+  provider does. Both legs are proven at compile time.
+- **`supabase-shape.test.ts` now proves the consumer's leg**: a `SupabaseClient<Database>` is
+  assignable to `MessagingSupabaseClient`. The old proof deliberately checked only the CALLS,
+  noting that whole-interface assignability "makes tsc bail with TS2589, which is a compiler
+  limit, not a contract failure" — true, and precisely why the consumer could not compile. The
+  limit was the contract failure.
+
+### Consumer action (C28)
+
+None, and one less cast: pass your `SupabaseClient` straight in. A host that had written
+`client={supabase as never}` can delete the cast. `MessagingSupabaseInternal` is exported for
+anyone building the repository directly.
+
+## 0.8.0 — 2026-09-07
+
+**Every conversation in the first real inbox was titled with a raw UUID.** The second live defect
+of the adoption session, found by looking at the screen rather than at a test.
+
+### Fixed
+
+- **The participant profile is NESTED under `user`, and the top-level `id` is the participant
+  ROW.** The live `get_dm_conversations_with_details` aggregate is
+  `{ id, user_id, role, is_muted, last_read_at, user: { user_id, email, display_name, avatar_url } }`.
+  This package read `display_name` / `email` / `avatar_url` off the TOP level, found nothing, and
+  fell back to the user id — so a direct conversation's title, its avatar, and every participant
+  name rendered as a UUID. The nested profile is now the source, `user_id` is the identity, and
+  the bare `id` fallback survives only for an aggregate that carries neither — because here `id`
+  belongs to a different entity, and using it as a user id attributes a message to a row key.
+- A regression test built from the verbatim live aggregate; it fails against 0.7.0.
+
+### Consumer action (C28)
+
+None. Names and avatars simply appear now.
+
 ## 0.7.0 — 2026-09-07
 
 🚨 **Every RPC in this package was calling the wrong schema, so every read failed against the

package/dist/index.cjs

@@ -798,11 +798,13 @@ function projectParticipants(value, operation) {
   for (const entry of value) {
     if (typeof entry !== "object" || entry === null) continue;
     const record = entry;
-    const id = str(record, "user_id") ?? str(record, "id");
+    const nested = typeof record["user"] === "object" && record["user"] !== null ? record["user"] : {};
+    const id = str(record, "user_id") ?? str(nested, "user_id") ?? str(record, "id");
     if (id === null) continue;
     summaries.push(
       projectUserSummary({
         ...record,
+        ...nested,
         user_id: id
       })
     );
@@ -1569,12 +1571,13 @@ function requireOrg(organizationId, operation) {
   return organizationId;
 }
 function createMessagingRepository(options) {
-  const { client, identity } = options;
+  const { identity } = options;
   const org = requireOrg(identity.organizationId, "createMessagingRepository");
   const userCache = createReadCache({
     ttlMs: options.userTtlMs ?? 5 * 6e4,
     ...options.now !== void 0 ? { now: options.now } : {}
   });
+  const client = options.client;
   const db = () => client.schema(MESSAGING_SCHEMA);
   const rpcDb = () => client.schema(MESSAGING_RPC_SCHEMA);
   async function withSessionRetry(operation, run) {