@catalyst-cloud/schema 0.1.32 → 0.1.34

package/package.json

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

@@ -1670,6 +1670,13 @@ export const durableEventTypes = {
     wakes: { consumerClass: "dispatcher" },
     entity: "ticket",
   },
+  "relay.phase.wip.recorded": {
+    rationale:
+      "CTC-1096 — a shutting-down runner published a partial artifact and recorded a resume point for (ticket, phase) in the tenant DO's own relay_phase_wip. A durable fact about work that was preserved, not work that completed: it never advances relay_phase_state. NOT wake-eligible — the lease release that follows it in the same shutdown sequence already makes the unit immediately reclaimable, so waking the dispatcher on this too would double-drive the same successor.",
+    ingestVerb: "artifacts.event",
+    wakes: false,
+    entity: "ticket",
+  },
   "runner.container.stopped": {
     rationale:
       "CTC-1118 D4 — RunnerDispatchDO observed its own Container stop (activity expiry, a platform rollout SIGTERM, or an orderly exit) and reported it to the tenant DO. A positive observation ('a container stopped'), never an inferred absence — the entitlement plane's epistemic rule (entitlement.ts's RevokeRequest.observation). NOT wake-eligible: the report only collapses a held lease's deadline (existence-plane, never ownership — ADR-0037 Amendment 7), it does not itself create new eligible work for the dispatcher.",

package/src/migrations.generated.ts

@@ -242,6 +242,13 @@ export const MIRROR_MIGRATIONS = {
         tag: "0032_elite_donald_blake",
         breakpoints: true,
       },
+      {
+        idx: 33,
+        version: "6",
+        when: 1788282183348,
+        tag: "0033_lethal_electro",
+        breakpoints: true,
+      },
     ],
   },
   migrations: {
@@ -308,5 +315,7 @@ export const MIRROR_MIGRATIONS = {
       "-- CTC-851 — backfill comment parents + quarantine the pre-fix empty-issue_id orphans.\n--\n-- 0030 adds the parent_type/parent_entity_id columns and fixes both WRITE legs (webhook normalizer +\n-- reconcile) so new/re-swept comments carry a real parent, but that alone converges only rows the\n-- reconcile re-sweeps — and it walks OPEN issues, so a non-issue comment (or a comment on a closed\n-- issue) keeps its corrupt shape forever. This backfill is what makes the CORPUS canonical rather\n-- than just the new writes.\n--\n-- ⭐ Deliberately a DATA migration in the SHARED bundle (the 0014 pattern): the DO and every host /\n-- OPFS replica apply the same MIRROR_MIGRATIONS through the same runner, so each side repairs its OWN\n-- rows locally. That converges every replica WITHOUT emitting a change_log delta per row (migrations\n-- bypass appendChange), so no ring-buffer flood (the CTC-279 concern).\n--\n-- (a) Healthy rows (a real issue_id) → parent_type='issue', parent_entity_id=issue_id.\n-- (b) Orphans (issue_id empty-string — the measured shape — or NULL, defensively) cannot be repaired\n--     from row data: the replica comments table has no `raw` column and no parent signal beyond the\n--     comment-reply parent_id. A pure in-bundle DML migration cannot call Linear, so it QUARANTINES\n--     them: parent_type='unresolved', issue_id nulled — MARKED with a stated reason, never deleted\n--     (the AC explicitly permits quarantine-with-reason). CTC-851 measured 54 such rows live.\n--\n-- Idempotent by the `parent_type IS NULL` guard: once a row is stamped it is skipped on replay, so a\n-- crash between a statement succeeding and its tag being recorded (execReplaySafe) is safe.\nUPDATE `comments`\n  SET `parent_type` = 'issue', `parent_entity_id` = `issue_id`\n  WHERE `parent_type` IS NULL AND `issue_id` IS NOT NULL AND `issue_id` <> '';\n--> statement-breakpoint\nUPDATE `comments`\n  SET `parent_type` = 'unresolved', `issue_id` = NULL\n  WHERE `parent_type` IS NULL AND (`issue_id` = '' OR `issue_id` IS NULL);\n",
     "0032_elite_donald_blake":
       "ALTER TABLE `issues` ADD `creator_id` text;--> statement-breakpoint\nALTER TABLE `issues` ADD `creator_name` text;--> statement-breakpoint\nALTER TABLE `issues` ADD `creator_avatar_url` text;",
+    "0033_lethal_electro":
+      "ALTER TABLE `labels` ADD `team_id` text;--> statement-breakpoint\nCREATE INDEX `idx_labels_team` ON `labels` (`team_id`);",
   },
 } as const;

package/src/mirror.ts

@@ -101,13 +101,24 @@ export const issues = sqliteTable(
   ],
 );
 
-export const labels = sqliteTable("labels", {
-  id: text("id").primaryKey(),
-  name: text("name"),
-  color: text("color"),
-  updated_at: integer("updated_at"),
-  removed_at: integer("removed_at"),
-});
+// CTC-1088: `team_id` is nullable and ADVISORY, never a gate — NULL means "workspace-scoped, or not
+// yet stamped by the authoritative sweep" (an ambiguity the org-wide reconcile leg bounds to one pass,
+// since it fetches `team { id }` and re-stamps every label every sweep — ADR-0022). Written UNCONDITIONALLY
+// only by that reconcile leg; a webhook or issue-nested label upsert OMITS the column entirely rather
+// than writing null over a real value — the SAME `users.email` precedent this file already documents
+// (see users, above), made safe by `upsertRow`'s `Object.keys(row)` column derivation (do/upsert.ts).
+export const labels = sqliteTable(
+  "labels",
+  {
+    id: text("id").primaryKey(),
+    team_id: text("team_id"),
+    name: text("name"),
+    color: text("color"),
+    updated_at: integer("updated_at"),
+    removed_at: integer("removed_at"),
+  },
+  (t) => [index("idx_labels_team").on(t.team_id)],
+);
 
 // Teammate identities (CTC-USERS): resolves issue assignees + delegate AGENTS (and comment/PR
 // authors/reviewers) to a name + avatar so the UI never renders a gray "Unknown" chip. AGENT