@openwop/openwop-conformance 2.46.43 → 2.46.44

package/CHANGELOG.md

@@ -1,3 +1,8 @@
+## [2.46.44] — 2026-11-08 — Bounded loopback and resolvedVia go Active
+
+- **RFC 0258.** `v2-bounded-loopback`: a server-free shape leg and six host legs (re-arm, history from the log, `ApprovalData.loopback`, withdraw, fail on exhaustion, replay re-arm), gated on the `loopback` family and the `conformance-loopback-refine` / `-fail` fixtures. Judges in `lib/bounded-loopback-witness.ts`.
+- **RFC 0259.** `v2-interrupt-resolved-via`: a server-free shape leg and six host legs on the `readInterruptToken` seam, gated on `interrupt.resolvedVia`.
+
 ## [2.46.43] — 2026-11-04 — Two RFCs filed as Draft: bounded loopback and resolvedVia
 
 - **No suite change.** RFCs 0258 and 0259 add gap rows, which change the packed `spec/v1/gaps.json` and `CORPUS-STAMP.json`; no scenario, fixture or schema moves.

package/README.md

@@ -137,7 +137,7 @@ Each scenario file records its disposition and assertion count in `<report-dir>/
 
 ## What's Covered
 
-The current suite has 666 scenario files under `src/scenarios/`. By target major ([`scenario-majors.json`](./scenario-majors.json)): 226 files run against a v2 host and 455 against a v1 host; 15 of them run at both.
+The current suite has 668 scenario files under `src/scenarios/`. By target major ([`scenario-majors.json`](./scenario-majors.json)): 228 files run against a v2 host and 455 against a v1 host; 15 of them run at both.
 
 The v2 scenarios (`src/scenarios/v2-*.test.ts`) cover, by area:
 
@@ -166,7 +166,7 @@ Three kinds of scenario share the tree:
 - **Host** checks drive a live host over HTTP.
 - **Gated** checks run only when the host advertises the family, profile or fixture they need, and otherwise record `inapplicable` or `blocked` with a reason. `--require-behavior` turns an advertised-but-unwitnessable behaviour into a failure.
 
-Current source tree: 666 scenario files. [`coverage.md`](./coverage.md) maps each spec document and every OpenAPI operation to its scenarios. [`CHANGELOG.md`](./CHANGELOG.md) records when each scenario landed.
+Current source tree: 668 scenario files. [`coverage.md`](./coverage.md) maps each spec document and every OpenAPI operation to its scenarios. [`CHANGELOG.md`](./CHANGELOG.md) records when each scenario landed.
 
 ## How the 2.x suite is built
 

package/dist/spec-artifacts.lock.json

@@ -1,5 +1,5 @@
 {
   "package": "@openwop/spec-artifacts",
-  "version": "2.46.43",
-  "stampSha256": "35bbc415dd07e23421b1ce986ea81f727c03bcfa9259c80fc96373180a7d712d"
+  "version": "2.46.44",
+  "stampSha256": "e300a0ad34ed84f4615a9c50caeb9d25598c83c66924ad027cd8cfb9ee8b2651"
 }

package/fixtures/conformance-loopback-refine-fail.json

@@ -0,0 +1,92 @@
+{
+  "id": "conformance-loopback-refine-fail",
+  "name": "Conformance: Bounded loopback (refine, fail on exhaustion)",
+  "version": "1.0",
+  "description": "RFC 0258 §D. The same graph with maxIterations 1 and onExhausted: fail. The first refine loops; a refine on the exhausted second visit emits workflow.loopback-limit, then cap.breached {kind: loopback-iterations}, and fails the run with loop_limit_exceeded naming gate. Conformance scenario: v2-bounded-loopback.test.ts.",
+  "nodes": [
+    {
+      "id": "draft",
+      "typeId": "core.identity",
+      "name": "Draft",
+      "position": {
+        "x": 0,
+        "y": 0
+      },
+      "config": {},
+      "inputs": {}
+    },
+    {
+      "id": "gate",
+      "typeId": "core.approvalGate",
+      "name": "Review",
+      "position": {
+        "x": 200,
+        "y": 0
+      },
+      "config": {
+        "title": "Conformance loopback review (conformance-loopback-refine-fail)",
+        "description": "Conformance suite — refine to loop back to draft.",
+        "actions": [
+          "accept",
+          "reject",
+          "refine"
+        ]
+      },
+      "inputs": {}
+    },
+    {
+      "id": "apply",
+      "typeId": "core.noop",
+      "name": "Apply",
+      "position": {
+        "x": 400,
+        "y": 0
+      },
+      "config": {},
+      "inputs": {}
+    }
+  ],
+  "edges": [
+    {
+      "id": "draft-gate",
+      "sourceNodeId": "draft",
+      "targetNodeId": "gate"
+    },
+    {
+      "id": "again",
+      "sourceNodeId": "gate",
+      "targetNodeId": "draft",
+      "loopback": {
+        "on": "refine",
+        "maxIterations": 1,
+        "historyInput": "rounds",
+        "onExhausted": "fail"
+      }
+    },
+    {
+      "id": "gate-apply",
+      "sourceNodeId": "gate",
+      "targetNodeId": "apply",
+      "triggerRule": "all_success"
+    }
+  ],
+  "triggers": [
+    {
+      "id": "manual",
+      "type": "manual",
+      "enabled": true
+    }
+  ],
+  "variables": [],
+  "metadata": {
+    "tags": [
+      "conformance",
+      "hitl",
+      "loopback",
+      "v2-only"
+    ]
+  },
+  "settings": {
+    "timeout": 0
+  }
+}

package/fixtures/conformance-loopback-refine.json

@@ -0,0 +1,91 @@
+{
+  "id": "conformance-loopback-refine",
+  "name": "Conformance: Bounded loopback (refine, withdraw)",
+  "version": "1.0",
+  "description": "RFC 0258. draft (core.identity, echoes its inputs) → gate (core.approvalGate, accept/reject/refine) → apply (core.noop), plus a loopback edge gate → draft {on: refine, maxIterations: 2, historyInput: rounds}. Each refine re-runs draft and asks gate again; draft echoes the round history it received. After two refines the third visit omits refine (onExhausted defaults to withdraw), and accept runs apply once. Conformance scenario: v2-bounded-loopback.test.ts.",
+  "nodes": [
+    {
+      "id": "draft",
+      "typeId": "core.identity",
+      "name": "Draft",
+      "position": {
+        "x": 0,
+        "y": 0
+      },
+      "config": {},
+      "inputs": {}
+    },
+    {
+      "id": "gate",
+      "typeId": "core.approvalGate",
+      "name": "Review",
+      "position": {
+        "x": 200,
+        "y": 0
+      },
+      "config": {
+        "title": "Conformance loopback review (conformance-loopback-refine)",
+        "description": "Conformance suite — refine to loop back to draft.",
+        "actions": [
+          "accept",
+          "reject",
+          "refine"
+        ]
+      },
+      "inputs": {}
+    },
+    {
+      "id": "apply",
+      "typeId": "core.noop",
+      "name": "Apply",
+      "position": {
+        "x": 400,
+        "y": 0
+      },
+      "config": {},
+      "inputs": {}
+    }
+  ],
+  "edges": [
+    {
+      "id": "draft-gate",
+      "sourceNodeId": "draft",
+      "targetNodeId": "gate"
+    },
+    {
+      "id": "again",
+      "sourceNodeId": "gate",
+      "targetNodeId": "draft",
+      "loopback": {
+        "on": "refine",
+        "maxIterations": 2,
+        "historyInput": "rounds"
+      }
+    },
+    {
+      "id": "gate-apply",
+      "sourceNodeId": "gate",
+      "targetNodeId": "apply",
+      "triggerRule": "all_success"
+    }
+  ],
+  "triggers": [
+    {
+      "id": "manual",
+      "type": "manual",
+      "enabled": true
+    }
+  ],
+  "variables": [],
+  "metadata": {
+    "tags": [
+      "conformance",
+      "hitl",
+      "loopback",
+      "v2-only"
+    ]
+  },
+  "settings": {
+    "timeout": 0
+  }
+}

package/fixtures.md

@@ -55,6 +55,8 @@ All fixtures MUST advertise:
 | Error route only | `conformance-error-route-only` | RFC 0257 — the only terminal sits behind `any_failed`; it is skipped with no condition anywhere | `completed` with `skippedTerminals` | < 1s |
 | All terminals skipped | `conformance-all-terminals-skipped` | RFC 0257 — a `truthy` edge on `payload.ok` declines (`{ok:false}`) or fires (`{ok:true}`) | `completed`, with or without `skippedTerminals` | < 1s |
 | Sub-workflow (child reaches no terminal) | `conformance-subworkflow-skip-parent` | RFC 0257 §B — a `core.subWorkflow` child completes with `skippedTerminals`; the parent continues | `completed` | < 2s |
+| Bounded loopback (withdraw) | `conformance-loopback-refine` | RFC 0258 — a refine loops `gate` back to `draft` with the round history; after two refines `refine` is withdrawn | `completed` after accept | unbounded (suspends) |
+| Bounded loopback (fail) | `conformance-loopback-refine-fail` | RFC 0258 §D — `maxIterations: 1`, `onExhausted: fail`; a refine on the exhausted visit fails the run | `failed` (`loop_limit_exceeded`) | unbounded (suspends) |
 | Approval (timeout) | `conformance-approval-timeout` | RFC 0223 G2 — a 1500 ms `timeoutMs`, no `onTimeout`: the host's timer resolves the gate rejected | `failed` (`approval_rejected`) after the timeout | ~1.5 s + the host's sweep |
 | Approval (timeout, onTimeout approve) | `conformance-approval-timeout-approve` | openwop#1696 — a 1500 ms `timeoutMs` with `onTimeout: approve`: a timeout never grants, so the gate still resolves rejected | `failed` (`approval_rejected`) after the timeout | ~1.5 s + the host's sweep |
 | Approval (reject loops back) | `conformance-approval-reject-loopback` | openwop#1697 — a rejected gate routed back to itself through `revise` is asked again under a new `key` | `waiting-approval` again after one reject (the suite cancels) | unbounded (suspends) |
@@ -308,6 +310,29 @@ The `messages`-mode stream fixture (AI token streaming) is covered by the determ
   4. With `{ok: true}`, `act` MUST run and the run MUST end `run.completed` with no `skippedTerminals`.
 - **Terminal status**: `completed` on both inputs.
 
+### `conformance-loopback-refine`
+
+- **Tagged** `v2-only`: `fixtures-valid` validates it against `schemas/v2/workflow-definition.schema.json`, because the frozen v1 wire cannot carry `loopback`.
+- **Purpose**: witness RFC 0258 §§C–D: the re-arm, the round history and withdrawal on exhaustion.
+- **Inputs**: none.
+- **Behavior**:
+  1. `draft` (`core.identity`) echoes its inputs. Its only input is the loopback's `historyInput` port `rounds`, so its `node.completed` `outputs` is `{rounds: [...]}`: `[]` on the first visit, then one `{round, outputs, refineFeedback}` entry per round, oldest first.
+  2. `gate` (`core.approvalGate`, actions accept/reject/refine) suspends. Each request's `ApprovalData.loopback` reads `{round, maxIterations: 2, exhausted}`.
+  3. A `refine` with `refineFeedback` completes `gate` with the marker `loopback {edgeId: "again", targetNodeId: "draft", round, rearmed: ["draft", "gate"]}`; `draft` runs again and `gate` is asked again under a new key. `apply` MUST NOT start.
+  4. After two refines, the third request omits `refine`, and a `refine` resume answers `400 validation_error` with the run still `waiting-approval`.
+  5. `accept` completes `gate`; `apply` runs once.
+- **Terminal status**: `completed`.
+- **Requires**: the `loopback` family with `maxIterations >= 2`.
+
+### `conformance-loopback-refine-fail`
+
+- **Tagged** `v2-only`: `fixtures-valid` validates it against `schemas/v2/workflow-definition.schema.json`, because the frozen v1 wire cannot carry `loopback`.
+- **Purpose**: witness RFC 0258 §D `onExhausted: fail`.
+- **Inputs**: none.
+- **Behavior**: the same graph with `maxIterations: 1` and `onExhausted: "fail"`. The first refine loops. A refine on the exhausted second visit emits `workflow.loopback-limit {nodeId: "gate", iterations: 1, limit: 1}`, then `cap.breached {kind: "loopback-iterations", limit: 1, observed: 2}`, then `run.failed` with `loop_limit_exceeded` and `failedNodeId: "gate"`.
+- **Terminal status**: `failed`.
+- **Requires**: the `loopback` family.
+
 ### `conformance-subworkflow-skip-parent`
 
 - **Purpose**: witness RFC 0257 §B (`spec/v2/core/execution.md` §`subWorkflow`, Output).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "2.46.43",
+  "version": "2.46.44",
   "description": "Black-box conformance suite for OpenWOP hosts (v2 current; v1 scenarios retained for the frozen v1 tree).",
   "repository": {
     "type": "git",
@@ -56,6 +56,6 @@
     "@openwop/spec-artifacts": "file:../spec-artifacts"
   },
   "peerDependencies": {
-    "@openwop/spec-artifacts": "2.46.43"
+    "@openwop/spec-artifacts": "2.46.44"
   }
 }