@catalyst-cloud/schema 0.1.35 → 0.1.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/schema",
-  "version": "0.1.35",
+  "version": "0.1.37",
   "type": "module",
   "description": "Typed Drizzle schema = single source of truth for the per-tenant Mirror DO SQLite store (CTC-13 / ADR-0002). Shared by the mirror Worker, the host-sync replica, and the browser OPFS replica.",
   "license": "MIT",

package/src/events/registry.ts

@@ -82,6 +82,24 @@ export const durableEventTypes = {
     ingestVerb: "coordination.publish",
     wakes: { consumerClass: "host-channel" },
   },
+  "ask.replied": {
+    rationale:
+      "A human answered — or tried to answer — an ask in its own thread, and the mirror's ask-decision trigger reached a named outcome. ADR-0039's own durable-fact example ('a human answer was received'), applied to the customer-facing ask loop (CTC-1326). Wake-eligible because the operator learning about it LATE is the defect CTC-1326 exists to close: before this, the only surface was a 15-minute Linear read poll.",
+    // ⛔ NOT `webhook.ingest`, THOUGH A COMMENT WEBHOOK IS WHAT SETS IT OFF (CTC-1049 review). That verb
+    // carries a hard invariant this fact cannot satisfy: `test/webhook-event-types.test.ts` asserts the
+    // mapping is SURJECTIVE over the webhook.ingest slice — every type in it must be reachable from a
+    // raw (source, eventType, action) tuple — and the CTC-1049 gate enforces the same coverage from the
+    // other side. This type is not a mapping of a delivery; it is MINTED INSIDE the mirror DO after the
+    // ask-decision trigger runs (which itself calls Linear), so no fixture could ever produce it and
+    // declaring it webhook.ingest silently broke both checks the moment it was added.
+    // ⚠️ `coordination.publish` is the closest TRUE verb, not a perfect one: the operator copy really
+    // does arrive over a cross-DO publish, but the origin copy is appended in place. The registry has
+    // no verb for "minted by the mirror itself", which is a real gap worth a follow-up rather than a
+    // reason to mislabel this one.
+    ingestVerb: "coordination.publish",
+    wakes: { consumerClass: "host-channel" },
+    entity: "ticket",
+  },
   "broker.daemon.gc": {
     rationale:
       "The coordination broker daemon's own garbage-collection pass completing — a discrete lifecycle event of the process that OWNS the coordination log, worth recording to explain gaps in the log's own continuity.",