@openwop/spec-artifacts 2.8.0 → 2.8.2

package/CORPUS-STAMP.json

@@ -1,17 +1,17 @@
 {
   "_comment": "Provenance of @openwop/spec-artifacts (RFC 0168 §D.2). files: SHA-256 per file; the conformance suite compares the installed peer against dist/spec-artifacts.lock.json at start.",
   "package": "@openwop/spec-artifacts",
-  "version": "2.8.0",
-  "corpusTag": "v2.8.0",
+  "version": "2.8.2",
+  "corpusTag": "v2.8.2",
   "files": {
     "api/.redocly.lint-ignore.yaml": "bf5a8350b88a72fa43f59605ed8d903ed24b6cfccda5e45509c9f6ed9ee4e712",
     "api/asyncapi.yaml": "d5ecb9ee6114582be3b1f662c84bfac9ae96dae7bacb853e461168f70a8e1c7d",
     "api/grpc/openwop.proto": "c3e72bb17cba514ee98feb6434e6c9b6ea6795bfd086489ec69fd882dd1ad977",
     "api/openapi.yaml": "39081c59fb696159806b0f2f9a42e7e9ff830d622fcf2ad4159b21357580a955",
     "api/redocly.yaml": "b0604c89b2ca6d5076ec25725c539dad44a741a811fe524439ee6daef8baa09f",
-    "api/seams-v2.yaml": "2ab83d4cdc2ae5d86985b91edcb942375018f44a1cb80d71ae0355f0a4083aec",
-    "api/v2/asyncapi.yaml": "4ee4014e07f36ec0f5a5492b604698c59de87fba833d9c5dbf8e4578bfedf2cb",
-    "api/v2/openapi.yaml": "696cce878d1cd2601d8fad207e52b1b03de8b78caac41f4013202d84e18584ab",
+    "api/seams-v2.yaml": "296a5283690fc422d525815abc780eacd3b6ab7c0fe04e3d4ea72f460f9fabb6",
+    "api/v2/asyncapi.yaml": "21407d943fd706afe9e5c4b5703e453fbd86a8594428014d49b71eb35b937d7c",
+    "api/v2/openapi.yaml": "704e81cd815e8aab818e0dd7dba1b744499e3e9d1f2ad4d7d528161d34a671ae",
     "api/v2/redocly.yaml": "1e66b60e6118ad11a823bb620678be464d99dfe50a40e3e6f93ec9429b88b34c",
     "schemas/README.md": "0c0b737ffcf8f30e7d2809cec8a498232de710f41443212922ad8337cdde0b51",
     "schemas/a2a-task-state.schema.json": "c9365918f993f943b4b619d42551eb066a1ed33a08d895d51b395432a5b1f1bc",
@@ -115,7 +115,7 @@
     "schemas/v2/artifact-type-pack-manifest.schema.json": "85630d1b760d0b41cf5a6fad2acfada39abaf7f0befd95cc4334e1e883e9615d",
     "schemas/v2/audit-verify-result.schema.json": "a748dfadb5155adfde8a91045e76b0db6695005fe559035d71670fdd55edb3ba",
     "schemas/v2/budget-policy.schema.json": "c7449daeb6e1d95e7a047b8c2814d3d54748697c27046972834874867d9b5f4c",
-    "schemas/v2/capabilities.schema.json": "5c6c6a70c73cb9cd0d61594e205a9bc2fd7905c41c7d0f43ae7e50523fdd85a9",
+    "schemas/v2/capabilities.schema.json": "4329d6a9a1a857afa327cc3428433a86aabf6c3cf4fde230855b29443992f693",
     "schemas/v2/certification-bundle.schema.json": "0bcf8f297266505ca39d30eea8100e3c0fb048f2651717fd746da8129fcb7920",
     "schemas/v2/channel-presence-payload.schema.json": "1c20ad810cb311d47aa0b95d928490826b2468fd161f884cd29e867053e6782f",
     "schemas/v2/channel-written-payload.schema.json": "ccecff3c71a3275ad8db035ac0e04db25e6f8d23cf091ddbcd5a60d1be1cbb6b",
@@ -201,7 +201,7 @@
     "schemas/workspace-file.schema.json": "464de85c2a068243084ee9c1d969bc7cd5d8f7948574e58450d6493c38a0e1e4",
     "spec/v1/alias-detectors.json": "e90916db12d2297e2e560b2d54d2c4702d6cb3bef7179a575844687a7ec17262",
     "spec/v1/capability-declaration-classes.json": "e7729aed5c4b4e1dd02abab0530f14cc95f5d4070fe51fb139e7f5cccefa00c6",
-    "spec/v1/core-standard-manifest.json": "839e4db486838db3ee64512a15bfcd95921a4d6611f1549909ef06c29fd8c8dd",
+    "spec/v1/core-standard-manifest.json": "c6d57dec530f5b37f0f1db857db923d1cbd88606cf8ae6b6cbebdb54e35aa950",
     "spec/v1/deprecations.json": "c81c8f71460936c8d489d8270477c7661cf4a5d7b7bad86c98899750b5656027",
     "spec/v1/deprecations.schema.json": "18c87e78bedc210431f795ae44c5b5d202f2f3317850d5cf86867d4f1fa1cdfb",
     "spec/v1/event-codemap.json": "3da60d884157793a360da532a9fcbbfb5285636db325a74cec94b34622186d97",
@@ -213,7 +213,7 @@
     "spec/v1/migrations.schema.json": "886779aa6c22e646db097f5df210adb018a4dd14a7b815465a18c8a7056c8f72",
     "spec/v1/operation-path-manifest.json": "5f5f4e3842669371730ebbd1aace3fb794192615f0018dc144f484ba5db82ac3",
     "spec/v1/spec-gaps.json": "eb3bfcb9c7d05c9a6845d4a40ec9493cfaa5a671932daf1af561310136fdabe8",
-    "spec/v2/README.md": "5d49f56f41e06b44312c61ad8144b786c9a90ec42fd0660a40d89520ef206137",
+    "spec/v2/README.md": "8dbfc17b10f373dba95bdd2e8fec0580f35b380a834d304be3e24e7498170185",
     "spec/v2/core/capabilities.md": "9e81d578e177f9875499677d22207df909e59e3d4ddaa3d90f18a7035cfb31f4",
     "spec/v2/core/conformance.md": "a451c0a2ba79d93c55e540ccef480eba7de9602d59bbb03eead05daafde0beac",
     "spec/v2/core/connection-packs.md": "2e53c92476f68304139faf0c370874dc27bbba56a127a07e0906ff06edbb8ff1",
@@ -234,30 +234,30 @@
     "spec/v2/core/versioning.md": "27b88cde88f9060567ef7e46f4897b6be8892ade9f4a46c2ab16e314c515eabd",
     "spec/v2/core/webhooks.md": "e08a736fd0bfdc79f5c2309c66f53caf96fac8d9954e0a184c2229de4ce286e9",
     "spec/v2/core/workflow-chain-packs.md": "26bb65721f826285b7d90c3cb62fa7e9fb2414c1bc6e0fd25b33209168c3102e",
-    "spec/v2/declaration.json": "4cebdd1dd35c7a59dffd38c154b0d9cdc58c2a3ffbfb452fa5743b64fc3c8d4e",
+    "spec/v2/declaration.json": "facd8b8466ea86b61325670450a1205c672e844e0dbcd9d9392ef0eb2021cca3",
     "spec/v2/declaration.schema.json": "c86e3083fb9789c1958ecb4576cc6f71aa90e6f339521139238543ed08211dd4",
     "spec/v2/errors.json": "4ff032033f02d7e3fb4204581456408ba5e7642b438c1f349bbd1c264e63e419",
     "spec/v2/event-codemap.json": "37869a03cdfd8758b57e6f350641a6ebbd383231cebda51f5473ad85f94ab74c",
     "spec/v2/event-codemap.schema.json": "b173f2a9bcc0bf9b62a474ce3b91e1431d597e64fd1560fc58662cd8606eaf9c",
-    "spec/v2/ext/README.md": "68b4203c1ffcb1434af79b5e04ae3d23501977e7d48b2256c18a6c92559f6270",
-    "spec/v2/ext/a2uiSurface/README.md": "7dfdd0db93b8bd2d8cfb0ebcc7c474f21f2cb0d3108cb66becf311288d21a9ef",
-    "spec/v2/ext/brand/README.md": "f5d3c6232e0a63fe445e9707dd6b0e117f8ececcec7194049fafa5562b63aa10",
-    "spec/v2/ext/canvas/README.md": "601537975b78d6f762a4a42c7cae583c54c61dfb73817cef99ac03177e671c11",
-    "spec/v2/ext/chat/README.md": "f4023b16b3749fbe3786439e370ee73c459c02f8d1c439b5df0287e1f24e1e56",
-    "spec/v2/ext/coordination/README.md": "70b00ede75f22c5fbdf4d8e0840d82d2dfeac61bda1459f94d6ebc2adb6d2865",
-    "spec/v2/ext/dataIntegration/README.md": "0a040215adbfc1cc176c2fbe052598701c9c36461367f0cd6b9e8d7bb1ee20da",
-    "spec/v2/ext/entities/README.md": "24cbf19103cb4711f41088a79a49077eaf4750b0c746764a8302e33b74ea54c8",
-    "spec/v2/ext/grpc-transport/README.md": "0d01d939fc7a4eab050f141b42e4fe145f312bcdd89ef78359a47e33c4e94751",
-    "spec/v2/ext/kanban/README.md": "c6b3b3bbf6c9cecae674fc7874e145dc3e4f723a864409ad6e96b0173868f801",
-    "spec/v2/ext/knowledge/README.md": "067280b15e14b3c46550d7b0ee68d49e7d1455ce86218d05bbc44535eb668bf1",
-    "spec/v2/ext/launchStudio/README.md": "3c4258e781d069dced34ab45552ce5b2b4af6ec7e08f0e2e00584d87a7981b15",
-    "spec/v2/ext/messaging/README.md": "0ce7535498458ad63d9b7d5b143da618a2da2ce4033ca53ea3fc4cb0c65419db",
-    "spec/v2/ext/portability/README.md": "15b8a881df861ff289489ca13a3a4871cf6e14aed90ca018afadff2388a05476",
-    "spec/v2/ext/provider-idempotency/README.md": "e3f159b2d1b53c4c279b911de91d80b5410a1e6a05ba940a7f4d2c0d547cf000",
+    "spec/v2/ext/README.md": "ff91a503e0795e1b898e37d9e445add2d5975529723f7b32b2599b60a24c1ae3",
+    "spec/v2/ext/a2uiSurface/README.md": "742e3774cf62a857d0eeb2fcd27f07a0aa2ed2cddcec2bbb3b22a13f05a78bbf",
+    "spec/v2/ext/brand/README.md": "4eca8c070971f249d2191a31370d8e4f383d6a5399dafd7ba1831ae834c4e693",
+    "spec/v2/ext/canvas/README.md": "cdc1941d1425b53a5b10aa9fc01aacc4e55d0418f4690b2178e1682389d0a985",
+    "spec/v2/ext/chat/README.md": "4b64ddd875ef44794c8c4e2adfec9e409818b35ee7d16841f575a6022c97c11c",
+    "spec/v2/ext/coordination/README.md": "76c280ca561da9d827a56701868ee7a3064946c1931179d62160e196bd215526",
+    "spec/v2/ext/dataIntegration/README.md": "976f18de6f2b54ed9643b4b325daa1caff1ce71f92775a57cf859d4d67040d14",
+    "spec/v2/ext/entities/README.md": "fcdd4929461d394755d5dcbe6de3af74599abcf68ca29700debbf86f0d76b83c",
+    "spec/v2/ext/grpc-transport/README.md": "727a097a8e17f647e566d96c3e178b676acdba0c7a8d592b5c074799bc3782e1",
+    "spec/v2/ext/kanban/README.md": "6920ef8c302ee30c09cdc5fe6a705ccc0cc10724227f7e2617c13734bee3595b",
+    "spec/v2/ext/knowledge/README.md": "50d5d50a72f5cdd90692fba69c3b2e5674f931dcbf5efabb56b78ed66da00892",
+    "spec/v2/ext/launchStudio/README.md": "8085ffff8bee039b04f215752e04a5730f7fc0324528721f097cfeaf4dd1b52a",
+    "spec/v2/ext/messaging/README.md": "4db10394153e9639ff639f2a39951e69737ed02084a45b99d7ee9883052303b9",
+    "spec/v2/ext/portability/README.md": "c1a36eaf4016cc526bde6536fcb280eca34916504834610a3fb5ac87cafed3fa",
+    "spec/v2/ext/provider-idempotency/README.md": "590fa380be4719b949570306d5395fc5ac131e8e4c118f7866fe6ad2a5d88129",
     "spec/v2/ext/provider-idempotency/registry.json": "5b5fecad604fb4ab38da39f5abe697a4e57b05406c398f8afeb377331b2bd965",
-    "spec/v2/ext/restTransport/README.md": "8cfc6471ca1ca6e43bb53b21d47b33e73c6a5821e631eb4f565b971c01e2e5de",
-    "spec/v2/ext/sandbox-runtime-notes/README.md": "94a25409596e5122c217c566cb02bd44dde33c8130f52507988d498def598f29",
-    "spec/v2/ext/webResearch/README.md": "76409f9d6a4aa512ba2b8bdffe706b2b509503266037c3ef890950f7b8c9bd2b",
+    "spec/v2/ext/restTransport/README.md": "ad1466dac8b04796f60ca3b5419d66b31405215dfb54327cccfa7af1a3e1159d",
+    "spec/v2/ext/sandbox-runtime-notes/README.md": "f7d591670415138e3889b7841e33e6964b166929f5aa1b09a95a7f8df44c40f9",
+    "spec/v2/ext/webResearch/README.md": "e74fbe55a8c00040f1f87b5448259ee4eb3a26769d607f7d2dd9a671a2e2832b",
     "spec/v2/facets/a2a.schema.json": "6b0bceddec6d18d5115aa7d04720a0cc1ad7a9a0a78f53c208b34becaba5d16e",
     "spec/v2/facets/aiProviders.schema.json": "0c76e48e5d487b5be3b3ab1f6512a4e206c840ee5087d1336c7d7e2853b58d03",
     "spec/v2/facets/auth.schema.json": "73440c944ad12c41aab0618aeb799a90a0b59e97fc685527f248afb7d015381a",
@@ -268,12 +268,13 @@
     "spec/v2/facets/runList.schema.json": "6223e1baaebbb9f4faa71bfe968f8d22b4aa88046d0e43e8d5f56409e7f86e90",
     "spec/v2/facets/sandbox.schema.json": "e75f54486d387b2d089791aa93b5093cd1450f1920753a0f97fc23acdfe978ed",
     "spec/v2/facets/webhooks.schema.json": "4bf3f8eb3161a43910efac4c44ccaf9567060c9da52d4cf09bcf3888d1b92192",
+    "spec/v2/facets/workflowChainPacks.schema.json": "3c8786b91afb7a4477cb082f1b914438b901ce1c16512d001f3c83557d859687",
     "spec/v2/id-field-bindings.json": "e73c06f3055ad30173507ac817a458b96362c8f26209ba105c53653292cf63d3",
     "spec/v2/path-manifest.json": "c123c9fd77dc1b3f9c2e9346ace80cdae007e6511138894956abda01e61ec1c6",
     "spec/v2/peer-dependency-aliases.json": "d10299280abee08258502925bc327293ee413e0108cd6e6ec75ff6110653308d",
     "spec/v2/profiles.json": "0636f19fceae625390003a347e70ef4797d84766b5c24ce8a02cea52aadebca4",
-    "spec/v2/release.json": "10723a8b777cdfdfbe7dd13f249cf8bcceaea261ca9cbcbc8c3c70ca6eeda3f6",
+    "spec/v2/release.json": "0bcbacf7697213dced197b2bc0cf8ee0af61786db4518eb39aad9524c1a74d80",
     "spec/v2/retention-floors.json": "eaf3722d95c79947af1d4269ef85117e126518c588cfcf1a2b21b97269f51624"
   },
-  "corpusCommit": "afec2d1a9ef2f11dce1ab1f95d98d7589f969d23"
+  "corpusCommit": "ae9a19cf3e20a12f2d0ab08eb194f191c1609613"
 }

package/api/seams-v2.yaml

@@ -1,7 +1,7 @@
 openapi: 3.1.0
 info:
   title: OpenWOP conformance seams profile (openwop-conformance-seams-v2)
-  version: 2.8.0
+  version: 2.8.2
   description: 'GENERATED by scripts/derive-v2-api.py. RFC 0168 §C: the seams are a versioned conformance profile with their
     own document and path space (/conformance/seams/…), validated against the canonical v2 schemas with no tolerance path,
     forbidden from the capability namespace (a host advertises the profile, never a testSeams flag). This document carries

package/api/v2/asyncapi.yaml

@@ -1,7 +1,7 @@
 asyncapi: 3.1.0
 info:
   title: OpenWOP v2 event streams
-  version: 2.8.0
+  version: 2.8.2
   description: GENERATED by scripts/derive-v2-api.py (RFC 0171 §E.1, RFC 0172 §C.2). One run-events channel whose address
     is the OpenAPI path key; the server pathname is empty (bare origin). streamMode is a pattern over the closed set and its
     comma-separated combinations (`values` never combines). hostEvents has a real address (RFC 0171 §E.1) — the documented

package/api/v2/openapi.yaml

@@ -1,7 +1,7 @@
 openapi: 3.1.0
 info:
   title: OpenWOP v2 API
-  version: 2.8.0
+  version: 2.8.2
   summary: REST surface for declaring, executing, suspending, resuming, and observing multi-step workflows.
   description: GENERATED by scripts/derive-v2-api.py from api/openapi.yaml and the RFC 0167 children (v2 charter Phase 3,
     P3-C). Bare origin, unversioned path keys, negotiation by `OpenWOP-Version` + `protocolVersions[]` (RFC 0172 §A). No seam

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/spec-artifacts",
-  "version": "2.8.0",
+  "version": "2.8.2",
   "description": "The OpenWOP machine-readable contract: api/ (OpenAPI, AsyncAPI, the seams profile), schemas/ (v1 and v2 JSON Schemas), the spec/v1 and spec/v2 registries (errors, event codemap, declaration, deprecations, migrations, gaps) and CORPUS-STAMP.json — published from the openwop/openwop corpus tag; the peer dependency @openwop/openwop-conformance digest-checks at start (RFC 0168 §D.2).",
   "license": "Apache-2.0",
   "repository": {

package/schemas/v2/capabilities.schema.json

@@ -6458,16 +6458,6 @@
             "negative-existence"
           ]
         },
-        "deferredParameters": {
-          "type": "object",
-          "description": "RFC 0124 (WCP4, `Active`). OPTIONAL. When `supported: true`, the host offers a capability-gated deferred-parameter expansion mode in ADDITION to expansion-time substitution (which remains the default and floor): at drop time it materializes the chain's `parameters` into top-level workflow `variables[]` (author value as `defaultValue`) and rewrites `{{params.<name>}}` into a spec'd runtime binding (PromptTemplate `{{varName}}` with `source:\"variable\"`, or a variable-sourced PortValue), so chain parameters stay overridable per run via `configurable` while the persisted definition keeps ZERO `{{params.*}}` tokens. A parameter marked `x-openwop-sensitive` MUST be deferred or the expansion fail-closed (`sensitive_param_not_deferrable`, 422) — never frozen into persisted `config`. Omission (or `supported:false`) signals the host does NOT offer deferred mode. No host may advertise `supported:true` until RFC 0124 is `Accepted`. See `workflow-chain-packs.md` §\"Deferred-parameter expansion\".",
-          "properties": {},
-          "additionalProperties": false
-        },
-        "hostExpansionSeam": {
-          "type": "boolean",
-          "description": "RFC 0013 erratum (2026-07-05). OPTIONAL. A **conformance-only test seam** advertisement (category: test harness, cf. `observability.testSeams` — NOT a product capability): when `true`, the host serves `POST /v1/host/sample/workflow-chain:expand` returning the `vendor.openwop.workflow-chain-sample` v1.0.0 expansion that `conformance/src/scenarios/workflow-chain-host-expansion.test.ts` asserts against. Absent/`false` ⇒ that live-host expansion scenario soft-skips; the semantic `workflowChainPacks.supported` claim is witnessed by the server-free `workflow-chain-expansion.test.ts` legs. This flag is DISTINCT from `deferredParameters` (RFC 0124), which is witnessed through its own `POST /v1/host/sample/chain/deferred-expand` seam — so a host MAY advertise `supported` / `deferredParameters.supported` without standing up the RFC 0013 sample-pack seam it was never handed a published fixture for. Advertising `supported:true` no longer conscripts a host into the RFC 0013 host-expansion scenario."
-        },
         "subChains": {
           "type": "object",
           "description": "RFC 0133 (workflow-chain composition, `Accepted`). OPTIONAL. When `supported: true`, the host's `POST …/workflows/from-chain` implements RUNTIME sub-chain composition per `workflow-chain-packs.md` §\"Sub-chain composition (RFC 0133)\": for each `config.subChainRef` reachable from a parent chain, it resolves the referenced chain (sibling or external), recursively expands + co-registers it as its own owned workflow (deterministic TENANT-SCOPED id from `(tenantId, childChainId, version)` — two tenants never collide on the global registry, a shared child registers once across parents in a tenant, a repeat instantiation converges), rewrites the referencing node's `subChainRef` → the minted child `config.workflowId`, and dispatches the child as a child run (`core.subWorkflow` / `core.dispatch` child-run); the `from-chain` response carries `{ workflowId, subChainWorkflowIds[], nodeCount }`. Bounded by a cycle check (`sub_chain_cycle`) + a depth cap (`sub_chain_max_depth_exceeded`). A host that does NOT advertise this block MUST refuse a `subChains`-bearing chain at author/instantiate time with `sub_chain_unsupported` (422) — it never silently flattens. `producedVariables` (RFC 0133 §2) needs NO flag: it is pure variable emission under the base `workflowChainPacks.supported`. Conformance scenarios `chain-subchain-fanout.test.ts` + `chain-subchain-unsupported-refused.test.ts` gate on this flag; the server-free `chain-subchain-sibling` / `chain-subchain-cycle-rejected` / `chain-produced-var-roundtrip` legs run unconditionally against the reference library.",
@@ -6518,7 +6508,7 @@
         }
       ],
       "description": "core/capabilities.md#workflowChainPacks — witness: witnessable-gated; maturity experimental/none; RFC 0013",
-      "x-openwop-seeded-from": "v1"
+      "x-openwop-facets-from": "spec/v2/facets/workflowChainPacks.schema.json"
     },
     "packs": {
       "type": "object",

package/spec/v1/core-standard-manifest.json

@@ -4,7 +4,7 @@
   "provenance": {
     "suite": {
       "package": "@openwop/openwop-conformance",
-      "version": "2.8.0"
+      "version": "2.8.2"
     },
     "note": "Derived from the corpus at generation time. Regenerate with --write; verify with --check."
   },
@@ -419,5 +419,5 @@
       "$id": "https://openwop.dev/spec/v1/workspace-file.schema.json"
     }
   ],
-  "digest": "6923a074e6cc0ee6bfc59f79b640e5239cdc31e721e23e89ba18a9c8226b505b"
+  "digest": "2d5e2eb843ab9d9c6affb0d9219cfd08e43e4c7bd0a091617613d04d43e993ee"
 }

package/spec/v2/README.md

@@ -1,6 +1,6 @@
 # OpenWOP v2 specification
 
-> **Status: released · corpus v2.3.3.** The authoritative version is
+> **Status: released · current corpus.** The authoritative version is
 > [`release.json`](./release.json). Target v2 for new implementations.
 
 OpenWOP v2 is the current protocol major. Its contract consists of this

package/spec/v2/declaration.json

@@ -1370,10 +1370,11 @@
         "adoption": "none"
       },
       "facets": [
-        "deferredParameters",
-        "hostExpansionSeam",
         "subChains"
       ],
+      "normativeText": [
+        "spec/v2/core/workflow-chain-packs.md"
+      ],
       "floorScenarios": [],
       "requirementIds": [],
       "owningRfc": "0013"

package/spec/v2/ext/README.md

@@ -15,11 +15,31 @@ discovery claim.
 `scripts/check-ext-status-coherence.mjs` checks these labels against committed
 conformance evidence.
 
-| Status | Meaning | Predicate |
-| --- | --- | --- |
-| `Draft` | Declared, but not supported by qualifying interoperability evidence. | The family is declared in `spec/v2/declaration.json` with `anchor: ext`. |
-| `Stable` | Witnessed. At least one host at evidence tier 2 or better serves it, and a **certified** bundle in `evidence/v2-host-bundles/` records the family's declared witness class satisfied. | Every `Stable` doc's family has ≥ 1 `executed-pass` row under its witness id in a bundle whose relevant profile claim is `certified: true`, **and** the 7-day comment window has run since the promotion PR. |
-| `Retired` | Withdrawn. The family is removed from the declaration and the document names its replacement or the RFC that retired it. | The family is absent from the declaration; the doc carries a `Superseded by:` or `Retired by:` line. |
+### `Draft`
+
+Declared, but not supported by qualifying interoperability evidence.
+
+**Predicate:** The family is declared in `spec/v2/declaration.json` with
+`anchor: ext`.
+
+### `Stable`
+
+Witnessed. At least one host at evidence tier 2 or better serves it, and a
+**certified** bundle in `evidence/v2-host-bundles/` records the family's
+declared witness class as satisfied.
+
+**Predicate:** Every `Stable` document's family has at least one
+`executed-pass` row under its witness id in a bundle whose relevant profile
+claim is `certified: true`, and the seven-day comment window has run since the
+promotion PR.
+
+### `Retired`
+
+Withdrawn. The family is removed from the declaration, and the document names
+its replacement or the RFC that retired it.
+
+**Predicate:** The family is absent from the declaration; the document carries
+a `Superseded by:` or `Retired by:` line.
 
 The gate enforces both directions:
 

package/spec/v2/ext/a2uiSurface/README.md

@@ -1,7 +1,7 @@
 # `a2uiSurface` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `a2uiSurface` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/capabilities.md) (`a2uiSurface`), is useful for migration but is not a
+The v1 description,
+[`spec/v1/capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/capabilities.md)
+(`a2uiSurface`), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/brand/README.md

@@ -1,7 +1,7 @@
 # `brand` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `brand` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostbrand) (§host.brand), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostbrand)
+(§host.brand), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/canvas/README.md

@@ -1,7 +1,7 @@
 # `canvas` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `canvas` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostcanvas) (§host.canvas), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostcanvas)
+(§host.canvas), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/chat/README.md

@@ -1,7 +1,7 @@
 # `chat` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `chat` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostchat) (§host.chat), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostchat)
+(§host.chat), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/coordination/README.md

@@ -1,7 +1,7 @@
 # `coordination` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `coordination` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostcoordination) (§host.coordination), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostcoordination)
+(§host.coordination), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/dataIntegration/README.md

@@ -1,7 +1,7 @@
 # `dataIntegration` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `dataIntegration` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostdataintegration) (§host.dataIntegration), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostdataintegration)
+(§host.dataIntegration), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/entities/README.md

@@ -1,7 +1,7 @@
 # `entities` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `entities` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostentities) (§host.entities), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostentities)
+(§host.entities), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/grpc-transport/README.md

@@ -11,8 +11,8 @@
 | **advertised as** | not advertisable; v2 has no `grpc` discovery record |
 | **owning RFC** | RFC 0175 (demotion); RFC 0094 §H (v1 text) |
 
-The [v1 `openwop.proto`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v2/ext/grpc-transport/openwop.proto)
+The [v1 `openwop.proto`](https://github.com/openwop/openwop/blob/main/spec/v2/ext/grpc-transport/openwop.proto)
 is retained as a sketch and uses `package openwop.v1`; it is not a v2 contract.
 v2 has no normative gRPC transport because the conformance suite has no gRPC
 client or behavioral witness. The v1 contract remains in
-[`spec/v1/grpc-transport.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/grpc-transport.md).
+[`spec/v1/grpc-transport.md`](https://github.com/openwop/openwop/blob/main/spec/v1/grpc-transport.md).

package/spec/v2/ext/kanban/README.md

@@ -1,7 +1,7 @@
 # `kanban` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `kanban` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostkanban) (§host.kanban), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostkanban)
+(§host.kanban), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/knowledge/README.md

@@ -1,7 +1,7 @@
 # `knowledge` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `knowledge` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostknowledge) (§host.knowledge), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostknowledge)
+(§host.knowledge), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/launchStudio/README.md

@@ -1,7 +1,7 @@
 # `launchStudio` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `launchStudio` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostlaunchstudio) (§host.launchStudio), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostlaunchstudio)
+(§host.launchStudio), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/messaging/README.md

@@ -1,7 +1,7 @@
 # `messaging` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `messaging` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostmessaging) (§host.messaging), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostmessaging)
+(§host.messaging), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/portability/README.md

@@ -9,7 +9,7 @@
 | **technical:** | `experimental` |
 | **adoption:** | `none` |
 | **advertised as** | `extensions.<org>.portability` |
-| **owning RFC** | RFC 0168 (decided in C.1 per RFC 0174 §E.2), RFC 0086/0087 (v1 text) |
+| **owning RFC** | RFC 0168 §C.1; RFC 0174 §E.2; RFCs 0086 and 0087 (v1 text) |
 
 The v2 core API does not define goals, export, or import operations. The
 [`export-bundle` schema](../../../../schemas/v2/export-bundle.schema.json) records
@@ -17,4 +17,5 @@ the proposed bundle shape, but no portable transport or behavioral witness is
 defined. A host MAY expose an organization-specific portability extension; a
 client MUST NOT assume it is compatible with another host's extension.
 
-The v1 background is in [`spec/v1/portability.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/portability.md).
+The v1 background is in
+[`spec/v1/portability.md`](https://github.com/openwop/openwop/blob/main/spec/v1/portability.md).

package/spec/v2/ext/provider-idempotency/README.md

@@ -8,7 +8,7 @@
 | **witness:** | `witnessable-gated` |
 | **technical:** | `experimental` |
 | **adoption:** | `none` |
-| **advertised as** | not a discovery family — a data registry (`registry.json`) the Layer-2 obligation reads |
+| **advertised as** | not applicable; supporting registry only |
 | **owning RFC** | RFC 0173 §C.2, RFC 0150 G3 |
 
 [`registry.json`](./registry.json) lists providers known to expose a natural

package/spec/v2/ext/restTransport/README.md

@@ -1,7 +1,7 @@
 # `restTransport` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `restTransport` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/capabilities.md) (`restTransport`), is useful for migration but is not a
+The v1 description,
+[`spec/v1/capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/capabilities.md)
+(`restTransport`), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/ext/sandbox-runtime-notes/README.md

@@ -9,7 +9,7 @@
 | **technical:** | `experimental` |
 | **adoption:** | `none` |
 | **advertised as** | not advertisable (notes, not a surface) |
-| **owning RFC** | RFC 0173 §D (RFC 0035 superseded by the `packs` obligation at the cut) |
+| **owning RFC** | RFC 0173 §D; RFC 0035 (superseded) |
 
 RFC 0035's `node:vm` demonstrator is retained only as implementation history;
 `node:vm` is not an isolation model. The v2 contract is in

package/spec/v2/ext/webResearch/README.md

@@ -1,7 +1,7 @@
 # `webResearch` extension
 
 > **Status: Draft · v2 extension.** Discovery-only reservation; no portable
-> operations or payload contract is defined in v2.3.3.
+> operations or payload contract is defined in the current v2 corpus.
 
 | Field | Value |
 | --- | --- |
@@ -21,7 +21,9 @@ operations, payloads, or authorization semantics from its presence. A pack may
 name `webResearch` as a dependency only when the host and pack share
 an out-of-band definition of that dependency.
 
-The v1 description, [`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/v2.3.3/spec/v1/host-capabilities.md#hostwebresearch) (§host.webResearch), is useful for migration but is not a
+The v1 description,
+[`spec/v1/host-capabilities.md`](https://github.com/openwop/openwop/blob/main/spec/v1/host-capabilities.md#hostwebresearch)
+(§host.webResearch), is useful for migration but is not a
 standalone v2 interoperability contract. A future revision can replace this
 boundary with normative behavior, schemas, and a behavioral witness.
 

package/spec/v2/facets/workflowChainPacks.schema.json

@@ -0,0 +1,18 @@
+{
+  "$comment": "RFC 0013 \u00a7Composition depth \u2014 the v2 facet set for workflowChainPacks. Two v1-seeded facets are NOT carried into v2: `deferredParameters` (RFC 0124, still `Active`; spec/v2/core/workflow-chain-packs.md \u00a7Parameter substitution states the portable per-run deferral \"is a named v2.x additive RFC and is not part of v2.0\", so binding it as an advertisable v2 facet let a host truthfully advertise a capability v2.0 does not define) and `hostExpansionSeam` (a self-described conformance-only test seam on POST /v1/host/sample/workflow-chain:expand \u2014 spec/v2/core/conformance.md \u00a7The seams profile forbids a test-seam capability flag: seams are the profile openwop-conformance-seams-v2 in the /conformance/seams/ path space, and the v1 path is removeIn 2.0 per spec/v1/deprecations.json). No v2 host bundle advertises either.",
+  "properties": {
+    "subChains": {
+      "type": "object",
+      "description": "RFC 0133 (workflow-chain composition, `Accepted`). OPTIONAL. When `supported: true`, the host's `POST \u2026/workflows/from-chain` implements RUNTIME sub-chain composition per `workflow-chain-packs.md` \u00a7\"Sub-chain composition (RFC 0133)\": for each `config.subChainRef` reachable from a parent chain, it resolves the referenced chain (sibling or external), recursively expands + co-registers it as its own owned workflow (deterministic TENANT-SCOPED id from `(tenantId, childChainId, version)` \u2014 two tenants never collide on the global registry, a shared child registers once across parents in a tenant, a repeat instantiation converges), rewrites the referencing node's `subChainRef` \u2192 the minted child `config.workflowId`, and dispatches the child as a child run (`core.subWorkflow` / `core.dispatch` child-run); the `from-chain` response carries `{ workflowId, subChainWorkflowIds[], nodeCount }`. Bounded by a cycle check (`sub_chain_cycle`) + a depth cap (`sub_chain_max_depth_exceeded`). A host that does NOT advertise this block MUST refuse a `subChains`-bearing chain at author/instantiate time with `sub_chain_unsupported` (422) \u2014 it never silently flattens. `producedVariables` (RFC 0133 \u00a72) needs NO flag: it is pure variable emission under the base `workflowChainPacks.supported`. Conformance scenarios `chain-subchain-fanout.test.ts` + `chain-subchain-unsupported-refused.test.ts` gate on this flag; the server-free `chain-subchain-sibling` / `chain-subchain-cycle-rejected` / `chain-produced-var-roundtrip` legs run unconditionally against the reference library.",
+      "properties": {
+        "maxDepth": {
+          "type": "integer",
+          "minimum": 1,
+          "default": 8,
+          "description": "RFC 0133 \u00a71.3 (resolves UQ3). RECOMMENDED default 8. The maximum sub-chain nesting depth the host co-expands; exceeding it fails closed with the DISTINCT code `sub_chain_max_depth_exceeded` (the DoS depth backstop, alongside the `sub_chain_cycle` self-composition check \u2014 SECURITY `sub-chain-expansion-bounded`)."
+        }
+      },
+      "additionalProperties": false
+    }
+  }
+}

package/spec/v2/release.json

@@ -1,6 +1,6 @@
 {
   "$comment": "RFC 0172 §D.1 — the one release identity the v2 artifacts derive from. `version` is the next corpus tag `v<version>` (the publish workflow's coordinated-release tag pattern `v*`; RFC 0172's `openwop/v2.<minor>.<patch>` spelling is amended to this at its flip). api/v2/*.yaml info.version, the suite's 2.x version and @openwop/spec-artifacts read it. Bumped by the release PR that cuts the tag, never by hand elsewhere.",
-  "version": "2.8.0",
-  "corpusTag": "v2.8.0",
+  "version": "2.8.2",
+  "corpusTag": "v2.8.2",
   "updated": "2026-09-18"
 }