@ai-matrx/messaging 0.6.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # 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

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,
@@ -1540,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",
@@ -1574,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();
@@ -1591,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;
   }