@catalyst-cloud/schema 0.1.21 → 0.1.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@catalyst-cloud/schema",
-  "version": "0.1.21",
+  "version": "0.1.22",
   "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/retention.ts

@@ -162,6 +162,28 @@ export function mayPruneHotEvent(check: HotEventPruneCheck): boolean {
   return check.archivedAt !== null && check.ageMs > EVENT_HOT_WINDOW_MS;
 }
 
+// ── Session transcripts — the artifact plane's first lifecycle class (CTC-963 / ADR-0041) ─────────
+//
+// Transcripts are NOT events and get their OWN retention class: short default, longer
+// keep-on-failure, neither inherited from event retention above nor from ADR-0036's original
+// no-lifecycle default. Enforced by two operator-applied R2 lifecycle delete-age rules keyed on the
+// name markers below (docs/event-backbone/retention-and-deletion.md's transcript section;
+// docs/devops.md carries the exact provisioning calls). The name prefixes are imported by
+// apps/mirror's transcript name grammar so route grammar and lifecycle rules share one definition.
+
+/** A transcript whose worker reported a clean outcome is kept 30 days. */
+export const TRANSCRIPT_RETENTION_OK_MS = 30 * 24 * 60 * 60 * 1000; // 30 days
+
+/** A transcript whose worker failed/died mid-phase is kept 180 days — keep-on-failure, so a
+ *  post-mortem is possible long after the ok-class copies have expired. */
+export const TRANSCRIPT_RETENTION_FAIL_MS = 180 * 24 * 60 * 60 * 1000; // 180 days
+
+/** The name marker a clean-outcome transcript carries in its final key segment. */
+export const TRANSCRIPT_OK_NAME_PREFIX = "transcript-ok-";
+
+/** The name marker a failed/crashed-outcome transcript carries in its final key segment. */
+export const TRANSCRIPT_FAIL_NAME_PREFIX = "transcript-fail-";
+
 /** Bump when the projection's slot ASSIGNMENT changes (a field moves position, or the slot count
  *  changes); additive-at-the-end changes to a slot's semantic meaning still bump, because AE has no
  *  schema to enforce it and a silent reinterpretation of an existing blob/double is the failure mode