@catalyst-cloud/schema 0.1.25 → 0.1.26

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/schema",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "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

@@ -1728,6 +1728,20 @@ export const durableEventTypes = {
     ingestVerb: "coordination.publish",
     wakes: false,
   },
+  "environment.check.override.granted": {
+    rationale:
+      "CTC-1171 Phase 4 — an operator granted a short-lived, exact-hash, audited bypass of the declaration gate (readEnvironmentGate, consulted for implement/pr). MirrorDO-native, same category as runner.start.failed: the audit ledger's own atomic record of the mutation, written in the SAME transaction as the override grant. NOT wake-eligible — granting an override does not itself create new eligible work; the next scan simply reads a different classifier verdict.",
+    ingestVerb: "coordination.publish",
+    wakes: false,
+    entity: "team",
+  },
+  "environment.check.override.revoked": {
+    rationale:
+      "CTC-1171 Phase 4 — the paired revocation fact to environment.check.override.granted, written atomically with the override row's revoked_at_ms. NOT wake-eligible for the same reason as the grant: a revoke only narrows a future classifier read, it never itself creates new eligible work.",
+    ingestVerb: "coordination.publish",
+    wakes: false,
+    entity: "team",
+  },
 } as const satisfies Record<string, DurableEventSpec>;
 
 /** Why a heartbeat-shaped signal updates mutable NOW instead of the immutable history, and which