@openvtc/trust-tasks 0.13.1 → 0.14.1

package/src/vault/proxy-login/0.2/payload.ts

@@ -8,7 +8,7 @@
  */
 export type SiteTarget = WebOrigin | Did | IosApp | AndroidApp;
 /**
- * Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelope_unsupported`.
+ * Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelopeUnsupported`.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 
@@ -145,7 +145,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "didSigned" | "attested" | "pinnedOnly";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tspMessage";
@@ -232,7 +232,7 @@ export const PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSessionBlob": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelope_unsupported`."
+          "description": "Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelopeUnsupported`."
         },
         "ext": {
           "$ref": "#/$defs/Ext"
@@ -266,7 +266,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -517,7 +517,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSessionBlob": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelope_unsupported`."
+          "description": "Pluggable cipher envelope containing the SessionBlob cleartext (see `vault/_shared/0.1/session-blob`). The consumer unseals to recover cookies/headers, then injects into its browser session for the bound origin. Consumers reject envelope kinds they don't implement with `vault/proxy-login:envelopeUnsupported`."
         },
         "ext": {
           "$ref": "#/$defs/Ext"
@@ -551,7 +551,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vault/release/0.1/payload.ts

@@ -8,7 +8,7 @@
  */
 export type SiteTarget = WebOrigin | Did | IosApp | AndroidApp;
 /**
- * Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`.
+ * Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 /**
@@ -25,7 +25,7 @@ export type SecretKind =
   | "custom";
 
 /**
- * Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:not_proxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).
+ * Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:notProxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).
  */
 export interface VaultReleasePayload {
   entryId: string;
@@ -155,7 +155,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "did-signed" | "attested" | "pinned-only";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tsp-message";
@@ -190,7 +190,7 @@ export const PAYLOAD_SCHEMA = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://trusttasks.org/spec/vault/release/0.1",
   "title": "Vault Release — payload",
-  "description": "Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:not_proxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).",
+  "description": "Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:notProxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).",
   "type": "object",
   "additionalProperties": false,
   "required": [
@@ -237,7 +237,7 @@ export const PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSecret": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`."
+          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -296,7 +296,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -549,7 +549,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSecret": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`."
+          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -608,7 +608,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vault/release/0.2/payload.ts

@@ -8,7 +8,7 @@
  */
 export type SiteTarget = WebOrigin | Did | IosApp | AndroidApp;
 /**
- * Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`.
+ * Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 /**
@@ -25,7 +25,7 @@ export type SecretKind =
   | "custom";
 
 /**
- * Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:not_proxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).
+ * Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:notProxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).
  */
 export interface VaultReleasePayload {
   entryId: string;
@@ -155,7 +155,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "didSigned" | "attested" | "pinnedOnly";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tspMessage";
@@ -190,7 +190,7 @@ export const PAYLOAD_SCHEMA = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://trusttasks.org/spec/vault/release/0.2",
   "title": "Vault Release — payload",
-  "description": "Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:not_proxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).",
+  "description": "Consumer requests that the maintainer release the cleartext secret material of a vault entry. The response carries the secret in a pluggable cipher envelope (see vault/_shared/0.1/sealed-envelope); the cleartext shape is `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. This is the fallback when proxy-login is not viable (`vault/proxy-login:notProxyable`) or when the consumer needs the raw secret for a flow the maintainer cannot perform (e.g. autofill into a desktop app, copy-to-clipboard for offline use).",
   "type": "object",
   "additionalProperties": false,
   "required": [
@@ -237,7 +237,7 @@ export const PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSecret": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`."
+          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -296,7 +296,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -549,7 +549,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
       "properties": {
         "sealedSecret": {
           "$ref": "#/$defs/SealedEnvelope",
-          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelope_unsupported`."
+          "description": "Pluggable cipher envelope. Cleartext is a `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. Consumers reject envelope kinds they don't implement with `vault/release:envelopeUnsupported`."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -608,7 +608,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vault/sign-trust-task/0.1/payload.ts

@@ -8,7 +8,7 @@
  */
 export interface VaultSignTrustTaskPayload {
   /**
-   * Identifier of the vault entry whose principal will sign. The maintainer rejects with `not_signable` when `entry.secretKind` is not `did-self-issued` or `didcomm-peer` (other kinds have no DID-based signing identity).
+   * Identifier of the vault entry whose principal will sign. The maintainer rejects with `notSignable` when `entry.secretKind` is not `did-self-issued` or `didcomm-peer` (other kinds have no DID-based signing identity).
    */
   entryId: string;
   unsignedEnvelope: UnsignedTrustTaskEnvelope;
@@ -17,7 +17,7 @@ export interface VaultSignTrustTaskPayload {
   ext?: Ext;
 }
 /**
- * The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelope_issuer_mismatch`).
+ * The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelopeIssuerMismatch`).
  */
 export interface UnsignedTrustTaskEnvelope {
   /**
@@ -33,7 +33,7 @@ export interface UnsignedTrustTaskEnvelope {
    */
   type: string;
   /**
-   * Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting.
+   * Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting.
    */
   issuer: string;
   /**
@@ -45,7 +45,7 @@ export interface UnsignedTrustTaskEnvelope {
    */
   issuedAt: string;
   /**
-   * Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time.
+   * Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time.
    */
   expiresAt?: string;
   /**
@@ -80,7 +80,7 @@ export interface ConsumerContext {
   networkClass?: "unknown" | "home" | "corp" | "public" | "vpn";
 }
 /**
- * Step-up proof on retry after `step_up_required`.
+ * Step-up proof on retry after `stepUpRequired`.
  */
 export interface StepUpProof {
   kind: "webauthn-uv" | "push-approval" | "totp";
@@ -137,11 +137,11 @@ export const PAYLOAD_SCHEMA = {
     "entryId": {
       "type": "string",
       "minLength": 1,
-      "description": "Identifier of the vault entry whose principal will sign. The maintainer rejects with `not_signable` when `entry.secretKind` is not `did-self-issued` or `didcomm-peer` (other kinds have no DID-based signing identity)."
+      "description": "Identifier of the vault entry whose principal will sign. The maintainer rejects with `notSignable` when `entry.secretKind` is not `did-self-issued` or `didcomm-peer` (other kinds have no DID-based signing identity)."
     },
     "unsignedEnvelope": {
       "$ref": "#/$defs/UnsignedTrustTaskEnvelope",
-      "description": "The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelope_issuer_mismatch`)."
+      "description": "The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelopeIssuerMismatch`)."
     },
     "consumerContext": {
       "$ref": "#/$defs/ConsumerContext",
@@ -149,7 +149,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "stepUpProof": {
       "$ref": "#/$defs/StepUpProof",
-      "description": "Step-up proof on retry after `step_up_required`."
+      "description": "Step-up proof on retry after `stepUpRequired`."
     },
     "ext": {
       "$ref": "#/$defs/Ext"
@@ -189,7 +189,7 @@ export const PAYLOAD_SCHEMA = {
         "issuer": {
           "type": "string",
           "minLength": 1,
-          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting."
+          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting."
         },
         "recipient": {
           "type": "string",
@@ -204,7 +204,7 @@ export const PAYLOAD_SCHEMA = {
         "expiresAt": {
           "type": "string",
           "format": "date-time",
-          "description": "Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time."
+          "description": "Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time."
         },
         "payload": {
           "description": "Inner task's payload object. Opaque to the maintainer — passed through unchanged into the signed envelope."
@@ -354,7 +354,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "issuer": {
           "type": "string",
           "minLength": 1,
-          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting."
+          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting."
         },
         "recipient": {
           "type": "string",
@@ -369,7 +369,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "expiresAt": {
           "type": "string",
           "format": "date-time",
-          "description": "Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time."
+          "description": "Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time."
         },
         "payload": {
           "description": "Inner task's payload object. Opaque to the maintainer — passed through unchanged into the signed envelope."

package/src/vault/sign-trust-task/0.2/payload.ts

@@ -8,7 +8,7 @@
  */
 export interface VaultSignTrustTaskPayload {
   /**
-   * Identifier of the vault entry whose principal will sign. The maintainer rejects with `not_signable` when `entry.secretKind` is not `didSelfIssued` or `didcommPeer` (other kinds have no DID-based signing identity).
+   * Identifier of the vault entry whose principal will sign. The maintainer rejects with `notSignable` when `entry.secretKind` is not `didSelfIssued` or `didcommPeer` (other kinds have no DID-based signing identity).
    */
   entryId: string;
   unsignedEnvelope: UnsignedTrustTaskEnvelope;
@@ -17,7 +17,7 @@ export interface VaultSignTrustTaskPayload {
   ext?: Ext;
 }
 /**
- * The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelope_issuer_mismatch`).
+ * The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelopeIssuerMismatch`).
  */
 export interface UnsignedTrustTaskEnvelope {
   /**
@@ -33,7 +33,7 @@ export interface UnsignedTrustTaskEnvelope {
    */
   type: string;
   /**
-   * Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting.
+   * Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting.
    */
   issuer: string;
   /**
@@ -45,7 +45,7 @@ export interface UnsignedTrustTaskEnvelope {
    */
   issuedAt: string;
   /**
-   * Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time.
+   * Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time.
    */
   expiresAt?: string;
   /**
@@ -137,11 +137,11 @@ export const PAYLOAD_SCHEMA = {
     "entryId": {
       "type": "string",
       "minLength": 1,
-      "description": "Identifier of the vault entry whose principal will sign. The maintainer rejects with `not_signable` when `entry.secretKind` is not `didSelfIssued` or `didcommPeer` (other kinds have no DID-based signing identity)."
+      "description": "Identifier of the vault entry whose principal will sign. The maintainer rejects with `notSignable` when `entry.secretKind` is not `didSelfIssued` or `didcommPeer` (other kinds have no DID-based signing identity)."
     },
     "unsignedEnvelope": {
       "$ref": "#/$defs/UnsignedTrustTaskEnvelope",
-      "description": "The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelope_issuer_mismatch`)."
+      "description": "The Trust Task document to sign. MUST satisfy the framework's structural requirements (id/type/issuer/recipient/issuedAt/payload). MUST NOT carry a `proof`. `issuer` MUST equal the referenced entry's principalDid — the maintainer refuses to silently rewrite `issuer` (see `envelopeIssuerMismatch`)."
     },
     "consumerContext": {
       "$ref": "#/$defs/ConsumerContext",
@@ -189,7 +189,7 @@ export const PAYLOAD_SCHEMA = {
         "issuer": {
           "type": "string",
           "minLength": 1,
-          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting."
+          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting."
         },
         "recipient": {
           "type": "string",
@@ -204,7 +204,7 @@ export const PAYLOAD_SCHEMA = {
         "expiresAt": {
           "type": "string",
           "format": "date-time",
-          "description": "Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time."
+          "description": "Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time."
         },
         "payload": {
           "description": "Inner task's payload object. Opaque to the maintainer — passed through unchanged into the signed envelope."
@@ -354,7 +354,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "issuer": {
           "type": "string",
           "minLength": 1,
-          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelope_issuer_mismatch` rather than overwriting."
+          "description": "Issuer DID of the inner task. MUST equal the vault entry's principalDid — the maintainer rejects mismatches with `envelopeIssuerMismatch` rather than overwriting."
         },
         "recipient": {
           "type": "string",
@@ -369,7 +369,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "expiresAt": {
           "type": "string",
           "format": "date-time",
-          "description": "Optional inner-task expiry. The maintainer rejects with `envelope_expired` when this is in the past at sign time."
+          "description": "Optional inner-task expiry. The maintainer rejects with `envelopeExpired` when this is in the past at sign time."
         },
         "payload": {
           "description": "Inner task's payload object. Opaque to the maintainer — passed through unchanged into the signed envelope."

package/src/vault/upsert/0.1/payload.ts

@@ -28,7 +28,7 @@ export type SecretKind =
   | "ssh-key"
   | "custom";
 /**
- * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `did-self-issued` or `didcomm-peer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
+ * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `did-self-issued` or `didcomm-peer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 /**
@@ -61,7 +61,7 @@ export interface VaultUpsertPayload {
    */
   id?: string;
   /**
-   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create.
+   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create.
    */
   expectedVersion?: number;
   /**
@@ -158,7 +158,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "did-signed" | "attested" | "pinned-only";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tsp-message";
@@ -349,7 +349,7 @@ export const PAYLOAD_SCHEMA = {
     "expectedVersion": {
       "type": "integer",
       "minimum": 0,
-      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create."
+      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create."
     },
     "contextId": {
       "type": "string",
@@ -410,7 +410,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "sealedSecret": {
       "$ref": "#/$defs/SealedEnvelope",
-      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `did-self-issued` or `didcomm-peer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
+      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `did-self-issued` or `didcomm-peer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
     },
     "clearFields": {
       "type": "array",
@@ -799,7 +799,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -1247,7 +1247,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tsp-message` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vault/upsert/0.2/payload.ts

@@ -28,7 +28,7 @@ export type SecretKind =
   | "sshKey"
   | "custom";
 /**
- * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
+ * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 /**
@@ -61,7 +61,7 @@ export interface VaultUpsertPayload {
    */
   id?: string;
   /**
-   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create.
+   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create.
    */
   expectedVersion?: number;
   /**
@@ -158,7 +158,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "didSigned" | "attested" | "pinnedOnly";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tspMessage";
@@ -333,7 +333,7 @@ export const PAYLOAD_SCHEMA = {
     "expectedVersion": {
       "type": "integer",
       "minimum": 0,
-      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create."
+      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create."
     },
     "contextId": {
       "type": "string",
@@ -394,7 +394,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "sealedSecret": {
       "$ref": "#/$defs/SealedEnvelope",
-      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
+      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
     },
     "clearFields": {
       "type": "array",
@@ -759,7 +759,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -1183,7 +1183,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vault/upsert/0.3/payload.ts

@@ -28,7 +28,7 @@ export type SecretKind =
   | "sshKey"
   | "custom";
 /**
- * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
+ * Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated.
  */
 export type SealedEnvelope = DidcommAuthcryptEnvelope | HpkeArmoredEnvelope | TspMessageEnvelope;
 /**
@@ -65,7 +65,7 @@ export interface VaultUpsertPayload {
    */
   id?: string;
   /**
-   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create.
+   * When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create.
    */
   expectedVersion?: number;
   /**
@@ -162,7 +162,7 @@ export interface HpkeArmoredEnvelope {
   producerAssertion?: "didSigned" | "attested" | "pinnedOnly";
 }
 /**
- * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
+ * Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
  */
 export interface TspMessageEnvelope {
   envelope: "tspMessage";
@@ -334,7 +334,7 @@ export const PAYLOAD_SCHEMA = {
     "expectedVersion": {
       "type": "integer",
       "minimum": 0,
-      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:version_conflict` if the current version differs. Omit on create."
+      "description": "When updating, the consumer's last-observed `version` for the entry. The maintainer rejects with `vault/upsert:versionConflict` if the current version differs. Omit on create."
     },
     "contextId": {
       "type": "string",
@@ -395,7 +395,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "sealedSecret": {
       "$ref": "#/$defs/SealedEnvelope",
-      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelope_unsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
+      "description": "Pluggable cipher envelope (discriminated by `envelope`) whose cleartext is a JCS-canonical JSON conforming to `vault/_shared/0.1/vault-secret#/$defs/VaultSecret`. The supported envelope kinds are listed in the SealedEnvelope shared schema; M2A consumers reject any kind they don't implement with `vault/upsert:envelopeUnsupported`. REQUIRED on create unless `secretKind` is `didSelfIssued` or `didcommPeer` (those carry only references to maintainer-internal key ids and have no extra secret bytes). On update, omit if the secret material is unchanged; populate if the secret is being rotated."
     },
     "clearFields": {
       "type": "array",
@@ -769,7 +769,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [
@@ -1202,7 +1202,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
     },
     "TspMessageEnvelope": {
       "title": "TspMessageEnvelope",
-      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelope_unsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
+      "description": "Trust Spanning Protocol message (https://trustoverip.github.io/tswg-tsp-specification/). Reserved variant; no OpenVTC component reads or emits this today. Listed in the union so implementations can declare intent to use TSP in discovery and so consumers reject `tspMessage` envelopes explicitly (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.",
       "type": "object",
       "additionalProperties": false,
       "required": [

package/src/vta/memory/list/0.1/payload.ts

@@ -193,7 +193,7 @@ export const SPEC = {
 export const RESPONSE_SPEC = {
   typeUri: RESPONSE_TYPE_URI,
   isBearer: false,
-  isProofRequired: false,
+  isProofRequired: true,
   isRecipientRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;