@catalyst-cloud/schema 0.1.49 → 0.1.51

package/package.json

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

@@ -791,68 +791,86 @@ export const durableEventTypes = {
     wakes: false,
     entity: "ticket",
   },
-  // ── CTC-1597 — `intake` is the renamed `triage` phase, ADDITIVE beside it (D4). Same shape as the
-  // `phase.triage.*` block below; nothing in this repo emits these yet (the phase is dormant, outside
-  // RELAY_PHASES), declared now so CTC-1530 can be re-cut under the right name.
+  // CTC-1530 — `intake` joins `RELAY_PHASES` at its HEAD, gated dark behind `CATALYST_INTAKE_PHASE`.
+  // This block mirrors `phase.remediate.*`'s own set exactly (no git/rebase-specific suffixes —
+  // intake never touches a branch), so the generic phase-lifecycle/park machinery every relay phase
+  // already shares works for it with no special-casing. Supersedes CTC-1597's placeholder
+  // declaration of the same family (a smaller, `phase.triage.*`-shaped set, since at that point
+  // `intake` was still dormant outside `RELAY_PHASES`) now that this ticket makes it a real,
+  // lease-backed, preemptable phase.
   "phase.intake.abandoned": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase's worker abandoned it — a lifecycle terminal fact. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase's worker abandoned it — a lifecycle terminal fact.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
   "phase.intake.boot-resume": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the daemon restarted and resumed this phase — a real coordination fact about continuity across a restart. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the daemon restarted and resumed this phase — a real coordination fact about continuity across a restart.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
-  "phase.intake.complete": {
+  "phase.intake.boot-resume-gated": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase reported success. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the daemon restarted but gated (did not immediately resume) this phase.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
-  "phase.intake.escalated": {
+  "phase.intake.complete": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase escalated to a human. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase reported success.",
     ingestVerb: "coordination.publish",
-    wakes: { consumerClass: "host-channel" },
+    wakes: false,
     entity: "ticket",
   },
   "phase.intake.failed": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase reported failure. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase reported failure.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
-  "phase.intake.failure-retracted": {
+  "phase.intake.orphan-detected": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): a previously-reported failure was retracted (corrected) — a real correction fact. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): an orphaned phase-agent worker was detected — a coordination fact (state discovered), not a sample.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
-  "phase.intake.linear-transition": {
+  "phase.intake.park": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase performed a real Linear ticket-state transition as part of its own execution. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the intake phase was PARKED after N consecutive failures (CTC-1270) — a terminal-until-released outcome, distinct from `phase.intake.failed`, which a reader must be able to tell apart. Paired with `phase.intake.revive`.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
-  "phase.intake.orphan-detected": {
+  "phase.intake.preempted": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): an orphaned phase-agent worker was detected — a coordination fact (state discovered), not a sample. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): a higher-priority worker preempted this phase.",
+    ingestVerb: "coordination.publish",
+    wakes: false,
+    entity: "ticket",
+  },
+  "phase.intake.reclaim": {
+    rationale:
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): ownership of orphaned work was reclaimed by a new worker — an ownership transition akin to a lease reassignment.",
+    ingestVerb: "coordination.publish",
+    wakes: false,
+    entity: "ticket",
+  },
+  "phase.intake.resumed-after-preemption": {
+    rationale:
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): the phase resumed after being preempted earlier — the paired fact to *.preempted.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",
   },
   "phase.intake.revive": {
     rationale:
-      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): a parked phase was revived. CTC-1597 — the renamed `triage` phase.",
+      "ADR-0039 durable-fact example ('a phase started, completed, failed, or was preempted'): a repeated-failure park of the intake phase was revived (CTC-1270) — the paired fact to `phase.intake.park`.",
     ingestVerb: "coordination.publish",
     wakes: false,
     entity: "ticket",

package/src/telemetry/phase-lifecycle-point.ts

@@ -62,6 +62,88 @@ export function teamFromTicket(ticket: string): string | null {
   return m === null ? null : m[1]!;
 }
 
+/**
+ * CTC-1776 — THE ONE DOCUMENTED ORDER of `detail`'s `key=` tokens, and the reason there is one.
+ *
+ * `detail` is an APPEND-ONLY, fixed-order sequence so an operator's `blob5 LIKE '%status=…%phase=…%'`
+ * predicate keeps matching as fields are added (docs/devops.md's own recipe is written against it).
+ * A new optional field goes at the END of `buildPhaseLifecyclePoint`'s array AND at the end of this
+ * list — never inserted in the middle.
+ *
+ * `failure_class` and `round` are RESERVED here, ahead of CTC-1771 building them, so that ticket's
+ * fields land after `reason=` by construction rather than by anyone remembering to. The subsequence
+ * test in this module's spec is what enforces it.
+ *
+ * ⛔ `reason` is the ONE token whose value may contain spaces and its own `key=value` pairs — a
+ * validate row's `reason=ladder:plan-conformance=PASS type-safety=FAIL …` digest (CTC-1541/CTC-1776).
+ * A naive space-split therefore sees the digest's `step=verdict` pairs as fields of their own, which
+ * is exactly what the round-1 subsequence test missed (CTC-1776 validate round 2, CR-C). Two rules
+ * follow. (1) `reason` renders LAST of the free-text-capable tokens, so everything after it up to
+ * the next key REGISTERED HERE belongs to its value — a reader (the spec's `parseDetail`, an
+ * operator's `LIKE`) can only tell a digest pair from a field by consulting this list. (2) A field
+ * appended after `reason` MUST be registered here first: an unregistered one is indistinguishable
+ * from a digest token and is swallowed into `reason`'s value, which the spec's round-trip assertion
+ * turns into a red test rather than a silent census skew.
+ */
+export const PHASE_LIFECYCLE_DETAIL_ORDER = [
+  "status",
+  "ticket",
+  "phase",
+  "nonce",
+  "executor",
+  "substrate",
+  "provider",
+  "branch",
+  "base_sha",
+  "pr_number",
+  "artifact_key",
+  "reason",
+  // Reserved — CTC-1771 Phase 5.
+  "failure_class",
+  "round",
+] as const;
+
+/** CTC-1541/CTC-1776 — the `reason=` value a validate row carries for its per-step ladder digest.
+ *  Used by BOTH the succeeded-receipt site and the failed-release site in MirrorDO.ts, so "exactly
+ *  as a succeeded row does" is a shared function rather than two string literals. */
+export const LADDER_REASON_PREFIX = "ladder:";
+export function ladderReason(digest: string): string {
+  return `${LADDER_REASON_PREFIX}${digest}`;
+}
+
+/** CTC-1776 — the `reason=` value for a validate row whose ladder block could not be parsed at all.
+ *  Deliberately NOT a `ladder:` digest: five UNREPORTED verdicts read as a verdict set, and the
+ *  census must count "I could not look" apart from a real FAIL. Bare, with no cause suffix — the
+ *  five causes are named in the runner's own log line (loop.ts), keyed by ticket and phase. */
+export const VALIDATION_LADDER_UNPARSED_REASON = "validation-ladder-unparsed";
+
+/** CTC-1776 — the one verdict that means "I could not look", mirrored from `LADDER_VERDICTS`
+ *  (`apps/runner/src/validation-ladder.ts`); this package stays runner-free, same posture
+ *  `apps/mirror/src/artifacts/relay-receipt.ts` already takes for the ladder's other bounds. */
+export const UNREPORTED_LADDER_VERDICT = "UNREPORTED";
+
+/**
+ * CTC-1776 remediate (validate round 1, CR-3) — is every `step=verdict` token in an already-rendered
+ * digest `UNREPORTED`?
+ *
+ * The succeeded-receipt site answers the same question from the parsed `RelayReceiptLadder` it holds;
+ * the FAILED-release site only ever holds the rendered digest string the runner wrote, so it needs
+ * this form. Both then map to {@link VALIDATION_LADDER_UNPARSED_REASON} rather than publishing five
+ * UNREPORTED verdicts as if they were a verdict set — the census has to count "I could not look"
+ * apart from a real FAIL on BOTH row statuses, not just on `succeeded`.
+ *
+ * An empty digest is `false`, never a vacuous `true`: `[].every(…)` is the exact shape AGENTS.md's
+ * false-clean-result rule names, and a summary with no tokens at all is not evidence of anything.
+ */
+export function isAllUnreportedLadderDigest(digest: string): boolean {
+  const tokens = digest.split(/\s+/).filter((token) => token.length > 0);
+  if (tokens.length === 0) return false;
+  return tokens.every((token) => {
+    const eq = token.lastIndexOf("=");
+    return eq !== -1 && token.slice(eq + 1) === UNREPORTED_LADDER_VERDICT;
+  });
+}
+
 /**
  * Build one `phase.lifecycle` TelemetryPoint. Throws (never a falsy sentinel) on an unrecognized
  * `status` — the same posture as `assertEmittable` for the event name.