@openwop/openwop-conformance 2.1.6 → 2.2.0

package/CHANGELOG.md

@@ -1,5 +1,103 @@
 # `@openwop/openwop-conformance` Changelog
 
+## [2.2.0] — 2026-09-16 — the suite wipes the host's mock program store between scenario files, and a bound id travels as one segment
+
+**Why a minor and not the 2.1.8 that was pinned for two days.** `PUBLISHING.md`
+§"Versioning alignment": a conformance scenario addition is a minor bump, and
+#1359 added `v2-bound-id-path-projection` (its header says so). No 2.1.x patch
+ever added a scenario file; this release does, so it is 2.2.0. Nothing was
+published as 2.1.8.
+
+This entry was first written on 2026-09-14 and said *"No scenario behaviour
+changes."* That was true when written and false by the time the tag was cut, so
+the entry is rewritten rather than appended to: two behaviour changes rode this
+version after the pin was bumped, and a package whose changelog denies them is a
+package lying about itself.
+
+### Fixed
+
+- **The suite now wipes the host's conformance-mock program store between
+  scenario FILES** (openwop #1357; half two of two, paired with openwop-app
+  #3870, which adds the seam). `src/setup.ts` posts
+  `POST /v1/host/openwop-app/test/mock-ai/reset` in a per-file `afterAll`.
+  Why: a host that keeps mock programs in a module-level map keyed by `nodeId`
+  retains any program a scenario does not fully drain, and the four
+  envelope-truncation scenarios seed `finishReason: 'length'` programs on
+  purpose — so a later file dispatching on a colliding node consumed the
+  leftovers and failed `envelope_truncation_unrecoverable` with nothing in that
+  file to explain it. Measured on `replay-observable-sequence-determinism`: red
+  in-suite, green alone, five runs on unchanged bases, one red at load 3.4 on an
+  idle box — not contention, and a wrong value rather than a missing result.
+  2.1.7's per-fixture node ids narrowed the collision; this removes the
+  leftover. **Best-effort by design:** a host without the seam answers 404 and
+  the call is swallowed, because a suite must never fail a compliant host for
+  lacking a TEST seam — so on such a host the leak, if it has one, persists
+  silently. Per file rather than per test because programs are seeded for a
+  whole scenario's attempt sequence.
+
+### Changed
+
+- **A tenant-bound id travels as one `~`-escaped path segment** (RFC 0184 §A.1,
+  openwop #1359; §A.5 exactly-once projection, #1360). A bound id is two
+  segments joined by `/`; a path parameter is one. The corpus said `%2F`
+  carried the separator, and a tier-1 host's front door decoded it back to `/`
+  before forwarding, so every bound id was unreachable through its own front
+  door. The escape marker is now `~` (RFC 3986 unreserved — an intermediary has
+  no license to rewrite it): every byte outside `[A-Za-z0-9._-]` becomes
+  `~XX`, total over bytes so a later grammar widening cannot invalidate a
+  projection already on the wire. New `src/lib/bound-id.ts` codec;
+  `v2-id-grammar` asserts the new form; new scenario
+  `v2-bound-id-path-projection` creates one run and asserts the projection is
+  applied exactly once (the codec is deliberately not idempotent — `a~3Ab` →
+  `a~7E3Ab` — so a double projection corrupts silently, and both reporting hosts
+  found a read path that already composed one). **Hosts: a v2 path parameter
+  carrying a bound id is now expected in the `~` form. `%2F` is no longer the
+  contract.**
+- **RFC 0183 requirement rows** (openwop #1358): `requirements.json` gains the
+  ids for the resume actions `interruptResolved` cannot record, and
+  `fixtures.md` documents `conformance-approval-refine`. The RFC is `Draft`; no
+  scenario asserts these rows yet.
+
+### Packaging
+
+- `spec/v2/declaration.json` gains an optional `normativeText` on family
+  entries (RFC 0169, openwop #1351): the path(s) where a family's behaviour is
+  actually written, as distinct from `section`, which names the declaration
+  site. The declaration and the schemas generated from it ship in the tarball,
+  which is what first required the identity bump.
+
+## [2.1.7] — 2026-09-13 — nine fixtures shared one programmable node id
+
+The mock-AI program seam is keyed by `nodeId` alone — no run, no workflow, no
+tenant. `host-sample-test-seams.md` §5 stated the isolation that relies on:
+*"each conformance scenario uses a unique fixture (and therefore unique
+`nodeId`)"*. The corpus did not honour it. Nine fixtures declared a node called
+`structured-call`, and vitest runs scenario files in parallel, so any two of
+them could overwrite each other's program mid-run.
+
+That is the long-standing `replay-observable-sequence-determinism` flake.
+That scenario never programs the mock: it runs `conformance-phase4-nondet-tool`
+and inherits whatever the last writer left. When an envelope scenario had just
+staged `{ stopReason: 'safety' }`, the replay fixture's own node refused, the
+source run reached `failed`, and the scenario reported
+
+    expected 'failed' to be 'completed'
+
+— an assertion about replay determinism failing for a reason that has nothing
+to do with replay. It was green in isolation, red under the full gate, and did
+not track load, because contention was never the variable; overlap was.
+
+Each of the nine nodes is now named for its fixture
+(`refusal-structured-call`, `nondet-structured-call`, and so on), which is what
+§5 always claimed. `conformance/scripts/check-mock-ai-node-ids-unique.mjs`
+holds the line: every fixture node dispatching to the mock provider must be
+owned by exactly one fixture.
+
+**Hosts: re-register the conformance fixtures when you pin 2.1.7.** The node
+ids inside those nine workflow definitions changed. A host still serving the
+old definitions will program a node its fixture no longer has, and the envelope
+scenarios will fail loudly rather than silently — but they will fail.
+
 ## [2.1.6] — 2026-09-13 — the unknown-run probe is tenant-bound
 
 `v2-compensation-read-projection` asserted `404 not_found` for an unknown run

package/README.md

@@ -117,7 +117,7 @@ Exit code is non-zero on any failed assertion. `--certify` distinguishes: `0`
 
 ## What's Covered
 
-The current suite has 517 scenario files under `src/scenarios/`.
+The current suite has 518 scenario files under `src/scenarios/`.
 - 2026-09-03 (suite `1.157.0 -> 1.158.0`, gap G17): NEW `idempotency-concurrent-claim.test.ts` — drives the new `host-sample-test-seams.md` §25 concurrent duplicate-delivery seam for the RFC 0150 §B / `idempotency.md` §"Concurrent duplicates (Layer 2)" atomic-claim MUST, which is unconditional and had no witness of any kind. Asserts every executor mints the SAME `logicalInvocationId` **before** asserting `delivered === 1` — without the identity check a host passes by minting different ids and never colliding, one effect because nothing raced. Not profile-gated and so not opt-out-able (the obligation is unconditional); an unmounted seam records `blocked`, which is not certifiable. Graduates `layer2-invocation-claim-atomic` reference-impl -> protocol.
 - 2026-08-19 (suite `1.137.0 → 1.138.0`): NEW `durability-poison-exhaustion.test.ts` — RFC 0158 §C.8, the FIRST row of that RFC's conformance table to land. Asserts what `failure-path.test.ts` cannot: not just that deterministically failing work reaches terminal, but that attempts STOP — counted on the log, re-counted after a scaled quiet window, asserted unchanged. A host still redelivering records more. Seam-gated on the existing event-log seam (`blocked` = unobservable, not unmet) and outside every profile floor.
 - 2026-08-19 (suite `1.136.15 → 1.137.0`): NEW `replay-fanout-suppression.test.ts` — capability-gated on `webhooks.supported`, **outside every profile floor**; witnesses `replay.md` §"Host-initiated fan-out is an external effect", which was the largest normative MUST NOT on the replay surface with no scenario and no SECURITY invariant. Three legs in ONE `it` against ONE receiver and ONE subscription — a positive control, the MUST NOT, and a `branch` boundary leg — because "no delivery arrived" passes identically when delivery never worked, so absence is asserted only after presence is proven on that exact wiring. A host with an SSRF guard correctly refuses the loopback receiver and records `blocked`: **unobservable, not unmet.**
@@ -462,7 +462,7 @@ Server-required (added in 1.7.0):
 | ------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Redaction** | [`capabilities.md`](../spec/v1/capabilities.md) §"Secrets" + NFR-7 + §"aiProviders" | Vendor-neutral assertions that the server doesn't leak secret material. Three scenario groups: (a) discovery shape contract — `secrets` + `aiProviders` advertisements are well-formed regardless of `secrets.supported`; when `supported === true`, scopes MUST be non-empty + `resolution === 'host-managed'`; `byok ⊆ supported`. (b) bearer-token redaction — invalid Bearer canary in `Authorization` header is not echoed in the 401 response body. (c) credentialRef echo control — gated on `secrets.supported === true`; canary planted in `configurable.ai.credentialRef` MUST NOT appear in any RunEvent payload (poll-based capture; transport-agnostic). Uses runtime-built canary fixtures (`lib/canaries.ts`) that defeat static secret scanners. 6 scenarios. |
 
-Current source tree: 517 scenario files. Use [`coverage.md`](./coverage.md) for current grade/gap tracking.
+Current source tree: 518 scenario files. Use [`coverage.md`](./coverage.md) for current grade/gap tracking.
 
 ## Remaining Gaps
 

package/dist/spec-artifacts.lock.json

@@ -1,5 +1,5 @@
 {
   "package": "@openwop/spec-artifacts",
-  "version": "2.1.6",
-  "stampSha256": "366973a92d7c7b3a59f4c872e35c720a6e8075d3f8e2da6920eebca507609b42"
+  "version": "2.2.0",
+  "stampSha256": "b5398e169f00362c4f6821354b1746c79fff01a341488ebfb2cf2cbd20f19b4a"
 }

package/fixtures/conformance-approval-refine.json

@@ -0,0 +1,45 @@
+{
+  "id": "conformance-approval-refine",
+  "name": "Conformance: Approval (refine)",
+  "version": "1.0",
+  "description": "Suspends on an approval gate offering accept|reject|refine. Resume with {action:'refine', refineFeedback:{...}} exercises RFC 0183 \u00a7A.1/\u00a7A.2 \u2014 the resolved payload must carry the action and its structured feedback.",
+  "nodes": [
+    {
+      "id": "gate",
+      "typeId": "core.approvalGate",
+      "name": "Approval Gate",
+      "position": {
+        "x": 0,
+        "y": 0
+      },
+      "config": {
+        "title": "Conformance approval (refine-capable)",
+        "description": "Conformance suite \u2014 please accept to complete the run.",
+        "actions": [
+          "accept",
+          "reject",
+          "refine"
+        ]
+      },
+      "inputs": {}
+    }
+  ],
+  "edges": [],
+  "triggers": [
+    {
+      "id": "manual",
+      "type": "manual",
+      "enabled": true
+    }
+  ],
+  "variables": [],
+  "metadata": {
+    "tags": [
+      "conformance",
+      "hitl"
+    ]
+  },
+  "settings": {
+    "timeout": 0
+  }
+}

package/fixtures/conformance-envelope-nl-to-format-engaged.json

@@ -5,7 +5,7 @@
   "description": "Drives `core.ai.structuredOutput` against the conformance-only `mock` provider. The conformance scenario POSTs a 3-entry program: all three attempts return natural-language prose (no JSON sigil at the start). The host's `dispatchStructured` retry loop exhausts on parse-error, detects the NL shape, and fires ONE additional dispatch with a corrective coercion fragment — emitting `envelope.nlToFormat.engaged { originalEnvelopeType, fallbackCalls: 1 }` BEFORE the secondary call. The pre-seeded 4th program entry returns valid JSON, the schema validates, and the run terminates `completed`.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "nl-to-format-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (NL responses)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-recovery-applied.json

@@ -2,10 +2,10 @@
   "id": "conformance-envelope-recovery-applied",
   "name": "Conformance: envelope.recovery.applied (RFC 0032 §B.6)",
   "version": "1.0",
-  "description": "Drives `core.ai.structuredOutput` against the conformance-only `mock` provider. The conformance scenario POSTs a 1-entry program to `/v1/host/sample/test/mock-ai/program` (keyed by `nodeId: 'structured-call'`) BEFORE starting the run: the mock returns a markdown-fenced JSON envelope (e.g., ```json\\n{\"result\":\"ok\"}\\n```). The host's `dispatchStructured` lenient-parse fallback strips the fence via `tryLenientParse(text)`, emits exactly one `envelope.recovery.applied` with `path: 'markdown-fence'`, and accepts the parsed value WITHOUT counting against the retry budget per RFC 0033 §D. Run terminates `completed`.",
+  "description": "Drives `core.ai.structuredOutput` against the conformance-only `mock` provider. The conformance scenario POSTs a 1-entry program to `/v1/host/sample/test/mock-ai/program` (keyed by `nodeId: 'recovery-applied-structured-call'`) BEFORE starting the run: the mock returns a markdown-fenced JSON envelope (e.g., ```json\\n{\"result\":\"ok\"}\\n```). The host's `dispatchStructured` lenient-parse fallback strips the fence via `tryLenientParse(text)`, emits exactly one `envelope.recovery.applied` with `path: 'markdown-fence'`, and accepts the parsed value WITHOUT counting against the retry budget per RFC 0033 §D. Run terminates `completed`.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "recovery-applied-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (markdown-fenced)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-refusal.json

@@ -5,7 +5,7 @@
   "description": "Single `core.ai.structuredOutput` node against the conformance `mock` provider with a pre-seeded program returning `stopReason: 'safety'` + `refusalText: '...'` on attempt 1. Host's `dispatchStructured()` MUST: (a) emit exactly one `envelope.refusal` event with the canonical payload shape; (b) NOT retry (RFC 0032 §B.3 + RFC 0033 §D — refusal is terminal); (c) fail the node with `error.code: 'envelope_refused_by_provider'` per RFC 0033 §F; (d) NOT echo the refusal text in `RunSnapshot.error.message` (SECURITY invariant `envelope-refusal-no-prompt-leak` — refusal text lives only on the event-log entry, scrubbed via the existing SR-1 redaction harness).",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "refusal-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (refusal)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-retry-attempted.json

@@ -2,10 +2,10 @@
   "id": "conformance-envelope-retry-attempted",
   "name": "Conformance: envelope.retry.attempted (RFC 0032 §B.1)",
   "version": "1.0",
-  "description": "Drives `core.ai.structuredOutput` against the conformance-only `mock` provider. The conformance scenario POSTs a 2-entry program to `/v1/host/sample/test/mock-ai/program` (keyed by `nodeId: 'structured-call'`) BEFORE starting the run: attempt 1 returns invalid JSON, attempt 2 returns a valid envelope. The host's `dispatchStructured` retry loop MUST emit exactly one `envelope.retry.attempted` event with `attempt: 2` between the two provider calls (RFC 0032 §B.1). The run terminates `completed` after the second attempt succeeds.",
+  "description": "Drives `core.ai.structuredOutput` against the conformance-only `mock` provider. The conformance scenario POSTs a 2-entry program to `/v1/host/sample/test/mock-ai/program` (keyed by `nodeId: 'retry-attempted-structured-call'`) BEFORE starting the run: attempt 1 returns invalid JSON, attempt 2 returns a valid envelope. The host's `dispatchStructured` retry loop MUST emit exactly one `envelope.retry.attempted` event with `attempt: 2` between the two provider calls (RFC 0032 §B.1). The run terminates `completed` after the second attempt succeeds.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "retry-attempted-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-retry-exhausted.json

@@ -5,7 +5,7 @@
   "description": "Drives `core.ai.structuredOutput` against the conformance `mock` provider with a program that returns invalid JSON on EVERY attempt. The host's `dispatchStructured` retry loop MUST exhaust its budget and emit exactly one `envelope.retry.exhausted` event with `finalReason: 'schema-violation'` (or `'parse-error'` per RFC 0032 §B.1 reason enum). The node MUST fail with `error.code: 'envelope_payload_invalid'` (existing RFC 0021 code per RFC 0033 §C). Pairs with `envelope-retry-exhausted.test.ts`.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "retry-exhausted-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (always invalid)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-truncated.json

@@ -5,7 +5,7 @@
   "description": "Drives `core.ai.structuredOutput` against the conformance `mock` provider with a program: attempt 1 returns `stopReason: 'max_tokens'` (truncation); attempt 2 returns a valid envelope. The host's `dispatchStructured` retry loop MUST: (a) emit exactly one `envelope.truncated` event with `stopReason: 'max_tokens'`; (b) retry with an INCREASED output budget per RFC 0033 §B (the host's `truncationBudgetMultiplier` — default 2×); (c) NOT inject the corrective schema fragment on the truncation retry (truncation is an output-size problem, not a schema problem). Eventually completes after attempt 2 succeeds. Pairs with `envelope-truncated.test.ts`.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "truncated-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output (truncation then success)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-envelope-truncation-cap-exhaustion.json

@@ -5,7 +5,7 @@
   "description": "Drives `core.ai.structuredOutput` against the conformance `mock` provider with a program that returns `stopReason: 'max_tokens'` on EVERY attempt. The host's `dispatchStructured` retry loop MUST: (a) emit `envelope.truncated` on each attempt (or at least the first one — RFC 0032 §B.4 is per-attempt); (b) double the budget each retry (RFC 0033 §B); (c) exhaust retries after `maxRetryAttempts` (default 3); (d) emit exactly one `envelope.retry.exhausted` with `finalReason: 'truncation'`; (e) emit `cap.breached` with `kind: 'schema'`; (f) fail the node with `error.code: 'envelope_truncation_unrecoverable'` per RFC 0033 §F. The run does NOT exceed `maxRetryAttempts` total LLM calls — DoS-bound assertion. Pairs with `envelope-truncation-cap-exhaustion.test.ts`.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "truncation-cap-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output (perpetual truncation → cap exhaustion)",
       "position": { "x": 0, "y": 0 },

package/fixtures/conformance-phase4-nondet-tool.json

@@ -16,7 +16,7 @@
       "inputs": {}
     },
     {
-      "id": "structured-call",
+      "id": "nondet-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (consumes nondet-tool result)",
       "position": { "x": 200, "y": 0 },
@@ -40,7 +40,7 @@
     }
   ],
   "edges": [
-    { "id": "e1", "sourceNodeId": "nondet-tool", "targetNodeId": "structured-call" }
+    { "id": "e1", "sourceNodeId": "nondet-tool", "targetNodeId": "nondet-structured-call" }
   ],
   "triggers": [
     { "id": "manual", "type": "manual", "enabled": true }

package/fixtures/conformance-phase4-replay-divergence.json

@@ -2,10 +2,10 @@
   "id": "conformance-phase4-replay-divergence",
   "name": "Conformance: RFC 0041 §B replay-divergence-at-refusal (Phase 4)",
   "version": "1.0",
-  "description": "Single `core.ai.structuredOutput` node against the conformance `mock` provider. Conformance scenario `replay-divergence-at-refusal.test.ts` pre-seeds the mock with a two-entry program via `POST /v1/host/sample/test/mock-ai/program` keyed on the structured-call nodeId: entry [0] returns a valid envelope (consumed by the original run); entry [1] returns `stopReason: 'safety'` + `refusalText` (consumed by the `:fork mode: replay`). Phase 4 hosts advertising `multiAgent.executionModel.replayDeterminism.refusalDivergenceEmission: true` MUST detect the divergence at replay time, emit a `replay.divergedAtRefusal` event with `originalEnvelopeKind: 'valid'` + `replayEnvelopeKind: 'refusal'`, and fail the replay with HTTP `422` + `error.code: 'replay_diverged_at_refusal'` per `spec/v1/rest-endpoints.md §\"Common error codes\"`. Silent substitution of the refusal for the original envelope is non-conformant.",
+  "description": "Single `core.ai.structuredOutput` node against the conformance `mock` provider. Conformance scenario `replay-divergence-at-refusal.test.ts` pre-seeds the mock with a two-entry program via `POST /v1/host/sample/test/mock-ai/program` keyed on the divergence-structured-call nodeId: entry [0] returns a valid envelope (consumed by the original run); entry [1] returns `stopReason: 'safety'` + `refusalText` (consumed by the `:fork mode: replay`). Phase 4 hosts advertising `multiAgent.executionModel.replayDeterminism.refusalDivergenceEmission: true` MUST detect the divergence at replay time, emit a `replay.divergedAtRefusal` event with `originalEnvelopeKind: 'valid'` + `replayEnvelopeKind: 'refusal'`, and fail the replay with HTTP `422` + `error.code: 'replay_diverged_at_refusal'` per `spec/v1/rest-endpoints.md §\"Common error codes\"`. Silent substitution of the refusal for the original envelope is non-conformant.",
   "nodes": [
     {
-      "id": "structured-call",
+      "id": "divergence-structured-call",
       "typeId": "core.ai.structuredOutput",
       "name": "Structured output via mock provider (Phase 4 replay-divergence probe)",
       "position": { "x": 0, "y": 0 },

package/fixtures.md

@@ -47,6 +47,7 @@ All fixtures MUST advertise:
 | Delay                                     | `conformance-delay`                                                                             | Verifies poll/SSE behavior over time                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | `completed`                                                                         | ≤ 30s (input-controlled)     |
 | Failure                                   | `conformance-failure`                                                                           | Verifies error-event surface                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | `failed`                                                                            | ≤ 5s                         |
 | Approval                                  | `conformance-approval`                                                                          | Verifies HITL approval interrupt + resume                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | `completed` after resolve                                                           | unbounded (suspends)         |
+| Approval (refine)                         | `conformance-approval-refine`                                                                   | RFC 0183 — refine resolution carries action + refineFeedback                                                        |
 | Clarification                             | `conformance-clarification`                                                                     | Verifies HITL clarification interrupt + resume                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | `completed` after resolve                                                           | unbounded (suspends)         |
 | Multi-node                                | `conformance-multi-node`                                                                        | Verifies edge ordering + per-node events                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | `completed`                                                                         | ≤ 10s                        |
 | Idempotent                                | `conformance-idempotent`                                                                        | Verifies `Idempotency-Key` cache                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | `completed`                                                                         | ≤ 5s                         |
@@ -177,6 +178,20 @@ The `messages`-mode stream fixture (AI token streaming) is covered by the determ
 - **Terminal status (after accept)**: `completed`.
 - **Resolve schema**: `{action: "accept" | "reject"}`. Server MUST reject any other shape with 400.
 
+### `conformance-approval-refine`
+
+- **Purpose**: verify a `refine` resolution round-trips its action and structured feedback (RFC 0183 §A.1/§A.2).
+- **Inputs**: none.
+- **Behavior**:
+  1. Run starts and reaches an `approvalGate` offering `accept | reject | refine`.
+  2. Run status MUST be `waiting-approval`.
+  3. Client POSTs `{action: 'refine', refineFeedback: {scope: 'whole', ...}}` to the interrupt.
+  4. The resolved event payload MUST carry `action: 'refine'` and the `refineFeedback` supplied.
+  5. A `refine` resolution supplying no `refineFeedback` MUST be refused.
+- **Why it is separate from `conformance-approval`**: adding `refine` to that fixture's `actions` would change a
+  registered workflow definition every host already serves, forcing a re-registration for a test-only widening.
+  A new id costs one catalog row and no host churn.
+
 ### `conformance-clarification`
 
 - **Purpose**: verify HITL clarification interrupt + resume.
@@ -487,6 +502,7 @@ conformance/
     conformance-delay.json
     conformance-failure.json
     conformance-approval.json
+    conformance-approval-refine.json
     conformance-clarification.json
     conformance-multi-node.json
     conformance-idempotent.json

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "2.1.6",
+  "version": "2.2.0",
   "description": "Production-ready black-box conformance suite for OpenWOP v1.0 compliant servers.",
   "repository": {
     "type": "git",
@@ -56,6 +56,6 @@
     "@openwop/spec-artifacts": "file:../spec-artifacts"
   },
   "peerDependencies": {
-    "@openwop/spec-artifacts": "2.1.6"
+    "@openwop/spec-artifacts": "2.2.0"
   }
 }

package/requirements.json

@@ -2,11 +2,11 @@
   "$comment": "GENERATED by conformance/scripts/generate-requirement-registry.mjs — do not edit. One record per it()/test() in src/scenarios. Ids: openwop.it.<file-stem>.<title-slug>[~n] (src/lib/requirement-ids.ts). A record with id null has an interpolated title; its run-time row is keyed by the rendered title and maps here by file+line only. Renamed ids need a row in requirement-aliases.json.",
   "generatedFrom": "src/scenarios/*.test.ts",
   "counts": {
-    "files": 566,
-    "tests": 2156,
-    "withStableId": 2156,
+    "files": 567,
+    "tests": 2159,
+    "withStableId": 2159,
     "interpolatedTitles": 0,
-    "explicitIds": 2111
+    "explicitIds": 2114
   },
   "records": [
     {
@@ -11218,7 +11218,7 @@
     {
       "id": "openwop.it.envelope-completion-distinguishes-truncation.capabilities-envelopes-reliability-completion-when-present-conforms-to-rfc-0033",
       "file": "envelope-completion-distinguishes-truncation.test.ts",
-      "line": 94,
+      "line": 103,
       "title": "capabilities.envelopes.reliability.completion (when present) conforms to RFC 0033 §E",
       "explicitId": "openwop.it.envelope-completion-distinguishes-truncation.capabilities-envelopes-reliability-completion-when-present-conforms-to-rfc-0033",
       "citations": [
@@ -11235,7 +11235,7 @@
     {
       "id": "openwop.it.envelope-completion-distinguishes-truncation.truncation-emits-envelope-truncated-envelope-retry-attempted-with-reason-truncat",
       "file": "envelope-completion-distinguishes-truncation.test.ts",
-      "line": 117,
+      "line": 126,
       "title": "truncation: emits envelope.truncated + envelope.retry.attempted with reason: \"truncation\"",
       "explicitId": "openwop.it.envelope-completion-distinguishes-truncation.truncation-emits-envelope-truncated-envelope-retry-attempted-with-reason-truncat",
       "citations": [
@@ -11256,7 +11256,7 @@
     {
       "id": "openwop.it.envelope-completion-distinguishes-truncation.truncation-retry-budget-strictly-greater-than-initial-rfc-0033-b-truncationbudge",
       "file": "envelope-completion-distinguishes-truncation.test.ts",
-      "line": 142,
+      "line": 151,
       "title": "truncation: retry budget strictly greater than initial (RFC 0033 §B truncationBudgetMultiplier)",
       "explicitId": "openwop.it.envelope-completion-distinguishes-truncation.truncation-retry-budget-strictly-greater-than-initial-rfc-0033-b-truncationbudge",
       "citations": [
@@ -11269,7 +11269,7 @@
     {
       "id": "openwop.it.envelope-completion-distinguishes-truncation.schema-violation-no-envelope-truncated-envelope-retry-attempted-reason-schema-vi",
       "file": "envelope-completion-distinguishes-truncation.test.ts",
-      "line": 166,
+      "line": 175,
       "title": "schema-violation: NO envelope.truncated; envelope.retry.attempted reason ∈ {schema-violation, parse-error}",
       "explicitId": "openwop.it.envelope-completion-distinguishes-truncation.schema-violation-no-envelope-truncated-envelope-retry-attempted-reason-schema-vi",
       "citations": [
@@ -11286,7 +11286,7 @@
     {
       "id": "openwop.it.envelope-completion-distinguishes-truncation.schema-violation-retry-budget-unchanged-from-initial-no-budget-multiplication-on",
       "file": "envelope-completion-distinguishes-truncation.test.ts",
-      "line": 196,
+      "line": 205,
       "title": "schema-violation: retry budget UNCHANGED from initial (no budget multiplication on this path)",
       "explicitId": "openwop.it.envelope-completion-distinguishes-truncation.schema-violation-retry-budget-unchanged-from-initial-no-budget-multiplication-on",
       "citations": [
@@ -14544,7 +14544,7 @@
     {
       "id": "openwop.it.interrupt-approval.run-suspends-at-gate-accept-resolution-drives-terminal-completed",
       "file": "interrupt-approval.test.ts",
-      "line": 21,
+      "line": 24,
       "title": "run suspends at gate, accept resolution drives terminal completed",
       "explicitId": "openwop.it.interrupt-approval.run-suspends-at-gate-accept-resolution-drives-terminal-completed",
       "citations": [
@@ -14565,7 +14565,7 @@
     {
       "id": "openwop.it.interrupt-approval.400-or-422-when-action-is-not-in-accept-reject",
       "file": "interrupt-approval.test.ts",
-      "line": 50,
+      "line": 53,
       "title": "400 (or 422) when action is not in {accept, reject}",
       "explicitId": "openwop.it.interrupt-approval.400-or-422-when-action-is-not-in-accept-reject",
       "citations": [
@@ -14578,7 +14578,7 @@
     {
       "id": "openwop.it.interrupt-approval.400-404-when-nodeid-does-not-match-an-active-interrupt",
       "file": "interrupt-approval.test.ts",
-      "line": 78,
+      "line": 81,
       "title": "400/404 when nodeId does not match an active interrupt",
       "explicitId": "openwop.it.interrupt-approval.400-404-when-nodeid-does-not-match-an-active-interrupt",
       "citations": [
@@ -14588,6 +14588,44 @@
         }
       ]
     },
+    {
+      "id": "openwop.it.interrupt-approval.a-refine-resolve-round-trips-action-and-the-structured-feedback-it-requires",
+      "file": "interrupt-approval.test.ts",
+      "line": 117,
+      "title": "a refine resolve round-trips `action` and the structured feedback it requires",
+      "explicitId": "openwop.it.interrupt-approval.a-refine-resolve-round-trips-action-and-the-structured-feedback-it-requires",
+      "citations": [
+        {
+          "section": "RFCS/0183-interrupt-resolved-action-fidelity.md §A.1",
+          "requirement": "a gate offering `refine` MUST accept a refine resolution carrying refineFeedback"
+        },
+        {
+          "section": "RFCS/0183-interrupt-resolved-action-fidelity.md §A.1",
+          "requirement": "the resolution MUST be recorded as an event"
+        },
+        {
+          "section": "RFCS/0183-interrupt-resolved-action-fidelity.md §A.1",
+          "requirement": "the resolved payload MUST carry `action: \"refine\"` — the seat RFC 0183 adds"
+        },
+        {
+          "section": "RFCS/0183-interrupt-resolved-action-fidelity.md §A.2",
+          "requirement": "a refine resolution MUST carry the refineFeedback it was given — an action whose meaning is incomplete without it"
+        }
+      ]
+    },
+    {
+      "id": "openwop.it.interrupt-approval.refuses-a-refine-resolution-that-supplies-no-refinefeedback",
+      "file": "interrupt-approval.test.ts",
+      "line": 167,
+      "title": "refuses a refine resolution that supplies no refineFeedback",
+      "explicitId": "openwop.it.interrupt-approval.refuses-a-refine-resolution-that-supplies-no-refinefeedback",
+      "citations": [
+        {
+          "section": "RFCS/0183-interrupt-resolved-action-fidelity.md §A.2",
+          "requirement": "refine without refineFeedback MUST be refused — the feedback is what the action means"
+        }
+      ]
+    },
     {
       "id": "openwop.it.interrupt-approver-routing.capabilities-schema-declares-interrupt-approverrouting",
       "file": "interrupt-approver-routing.test.ts",
@@ -25930,6 +25968,49 @@
         }
       ]
     },
+    {
+      "id": "openwop.it.v2-bound-id-path-projection.a-tenant-bound-id-is-readable-at-its-escaped-path-segment-links-carry-that-form",
+      "file": "v2-bound-id-path-projection.test.ts",
+      "line": 51,
+      "title": "a tenant-bound id is readable at its ~-escaped path segment, links carry that form, and a malformed escape is refused",
+      "explicitId": "openwop.requirement.0184.bound-id-path-projection",
+      "citations": [
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": "the run read at the projected segment MUST be the run that was created — a host that decodes the escape to a DIFFERENT id has a non-injective decoder"
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        },
+        {
+          "section": "spec/v2/core/identity.md §5",
+          "requirement": null,
+          "interpolated": true
+        }
+      ]
+    },
     {
       "id": "openwop.it.v2-bundle-v3-signed.a-signed-v3-bundle-validates-against-the-closed-root-schema-an-extra-root-key-is",
       "file": "v2-bundle-v3-signed.test.ts",

package/scenario-majors.json

@@ -1,9 +1,9 @@
 {
   "$comment": "GENERATED by conformance/scripts/generate-scenario-majors.mjs (RFC 0168 §D.3). Do not edit; add a file to BOTH_MAJORS in the generator to target both majors.",
   "counts": {
-    "files": 517,
+    "files": 518,
     "v1": 445,
-    "v2": 74
+    "v2": 75
   },
   "majors": {
     "a2a-1-0-agent-card.test.ts": [
@@ -1244,6 +1244,9 @@
     "v2-assurance-downgrade-audited.test.ts": [
       2
     ],
+    "v2-bound-id-path-projection.test.ts": [
+      2
+    ],
     "v2-bundle-v3-signed.test.ts": [
       2
     ],