@openvtc/trust-tasks 0.16.7 → 0.16.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openvtc/trust-tasks",
-  "version": "0.16.7",
+  "version": "0.16.9",
   "description": "Generated TypeScript bindings for the Trust Tasks framework registry.",
   "type": "module",
   "main": "./dist/index.js",

package/src/_shared/components.ts

@@ -45,7 +45,9 @@ export type Capability_DeviceV0_1 =
   | "sign-trust-task"
   | "credential-write"
   | "memory-read"
-  | "memory-write";
+  | "memory-write"
+  | "room-present"
+  | "room-open";
 /**
  * Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything.
  */
@@ -61,7 +63,9 @@ export type Capability_DeviceV0_2 =
   | "signTrustTask"
   | "credentialWrite"
   | "memoryRead"
-  | "memoryWrite";
+  | "memoryWrite"
+  | "roomPresent"
+  | "roomOpen";
 /**
  * Discriminator: is this consumer a user-driven Companion or a headless Service?
  */

package/src/device/list/0.1/payload.ts

@@ -245,7 +245,9 @@ export const PAYLOAD_SCHEMA = {
         "sign-trust-task",
         "credential-write",
         "memory-read",
-        "memory-write"
+        "memory-write",
+        "room-present",
+        "room-open"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },
@@ -581,7 +583,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "sign-trust-task",
         "credential-write",
         "memory-read",
-        "memory-write"
+        "memory-write",
+        "room-present",
+        "room-open"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },

package/src/device/list/0.2/payload.ts

@@ -245,7 +245,9 @@ export const PAYLOAD_SCHEMA = {
         "signTrustTask",
         "credentialWrite",
         "memoryRead",
-        "memoryWrite"
+        "memoryWrite",
+        "roomPresent",
+        "roomOpen"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },
@@ -581,7 +583,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "signTrustTask",
         "credentialWrite",
         "memoryRead",
-        "memoryWrite"
+        "memoryWrite",
+        "roomPresent",
+        "roomOpen"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },

package/src/device/register/0.1/payload.ts

@@ -213,7 +213,9 @@ export const PAYLOAD_SCHEMA = {
         "sign-trust-task",
         "credential-write",
         "memory-read",
-        "memory-write"
+        "memory-write",
+        "room-present",
+        "room-open"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },
@@ -539,7 +541,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "sign-trust-task",
         "credential-write",
         "memory-read",
-        "memory-write"
+        "memory-write",
+        "room-present",
+        "room-open"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },

package/src/device/register/0.2/payload.ts

@@ -213,7 +213,9 @@ export const PAYLOAD_SCHEMA = {
         "signTrustTask",
         "credentialWrite",
         "memoryRead",
-        "memoryWrite"
+        "memoryWrite",
+        "roomPresent",
+        "roomOpen"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },
@@ -539,7 +541,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "signTrustTask",
         "credentialWrite",
         "memoryRead",
-        "memoryWrite"
+        "memoryWrite",
+        "roomPresent",
+        "roomOpen"
       ],
       "description": "Fine-grained capability flag scoped to the device's allowed contexts. See SPEC.md for the full semantics of each. Capability values are additive: a consumer MUST ignore a value it does not recognise rather than reject the binding, and MUST NOT treat an unrecognised value as conferring anything."
     },

package/src/index.ts

@@ -205,6 +205,12 @@ export * as RegistryRecordUpdate_v0_1 from "./registry/record/update/0.1/payload
 export * as RoomShared_v0_1 from "./rooms/_shared/0.1/room.js";
 export * as RoomsCreate_v0_1 from "./rooms/create/0.1/payload.js";
 export * as RoomsEpochMint_v0_1 from "./rooms/epoch/mint/0.1/payload.js";
+export * as RoomsKeysCommit_v0_1 from "./rooms/keys/commit/0.1/payload.js";
+export * as RoomsKeysKeyPackage_v0_1 from "./rooms/keys/key-package/0.1/payload.js";
+export * as RoomsKeysOpen_v0_1 from "./rooms/keys/open/0.1/payload.js";
+export * as RoomsKeysPresent_v0_1 from "./rooms/keys/present/0.1/payload.js";
+export * as RoomsKeysWelcome_v0_1 from "./rooms/keys/welcome/0.1/payload.js";
+export * as RoomsRecordsCurate_v0_1 from "./rooms/records/curate/0.1/payload.js";
 export * as RoomsRecordsGet_v0_1 from "./rooms/records/get/0.1/payload.js";
 export * as RoomsRecordsList_v0_1 from "./rooms/records/list/0.1/payload.js";
 export * as RoomsRecordsPut_v0_1 from "./rooms/records/put/0.1/payload.js";
@@ -283,6 +289,11 @@ export * as VtaAppStateGet_v1_0 from "./vta/app-state/get/1.0/payload.js";
 export * as VtaAppStateList_v1_0 from "./vta/app-state/list/1.0/payload.js";
 export * as VtaAppStatePutMany_v1_0 from "./vta/app-state/put-many/1.0/payload.js";
 export * as VtaAppStatePut_v1_0 from "./vta/app-state/put/1.0/payload.js";
+export * as VtaBackupAbort_v1_0 from "./vta/backup/abort/1.0/payload.js";
+export * as VtaBackupCompleteExport_v1_0 from "./vta/backup/complete-export/1.0/payload.js";
+export * as VtaBackupFinalizeImport_v1_0 from "./vta/backup/finalize-import/1.0/payload.js";
+export * as VtaBackupInitiateExport_v1_0 from "./vta/backup/initiate-export/1.0/payload.js";
+export * as VtaBackupInitiateImport_v1_0 from "./vta/backup/initiate-import/1.0/payload.js";
 export * as VtaContextsCreate_v1_0 from "./vta/contexts/create/1.0/payload.js";
 export * as VtaContextsDelete_v1_0 from "./vta/contexts/delete/1.0/payload.js";
 export * as VtaContextsDidTemplatesCreate_v1_0 from "./vta/contexts/did-templates/create/1.0/payload.js";
@@ -312,6 +323,7 @@ export * as VtaDidTemplatesRender_v1_0 from "./vta/did-templates/render/1.0/payl
 export * as VtaDidTemplatesRender_v2_0 from "./vta/did-templates/render/2.0/payload.js";
 export * as VtaDidTemplatesUpdate_v1_0 from "./vta/did-templates/update/1.0/payload.js";
 export * as VtaDidTemplatesUpdate_v2_0 from "./vta/did-templates/update/2.0/payload.js";
+export * as VtaManagementReloadServices_v1_0 from "./vta/management/reload-services/1.0/payload.js";
 export * as VtaMemoryDelete_v0_1 from "./vta/memory/delete/0.1/payload.js";
 export * as VtaMemoryList_v0_1 from "./vta/memory/list/0.1/payload.js";
 export * as VtaMemoryPut_v0_1 from "./vta/memory/put/0.1/payload.js";

package/src/rooms/keys/commit/0.1/payload.ts

@@ -0,0 +1,195 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/rooms/keys/commit/0.1/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+/**
+ * A room's owner delivers an MLS Commit to a member's key-holding agent, advancing it one epoch. Every member must apply every commit, in order: an agent that misses one is stuck at its last epoch and can open nothing sealed after it.
+ */
+export interface RoomsKeysCommitPayload {
+  /**
+   * The room whose group is advancing.
+   */
+  roomId: string;
+  /**
+   * The MLS Commit message, base64url.
+   */
+  commit: string;
+  /**
+   * The MLS epoch this commit produces — the recipient's epoch after applying it. Stated so a recipient can tell a replay from a gap without parsing the commit: equal to its current epoch is a replay, more than one ahead is a gap.
+   */
+  epoch: number;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+/**
+ * Success response to rooms/keys/commit. Type https://trusttasks.org/spec/rooms/keys/commit/0.1#response.
+ */
+export interface RoomsKeysCommitResponsePayload {
+  /**
+   * The recipient's epoch after the operation. On a replay this is unchanged, which is how a sender distinguishes 'applied' from 'already had it' without either being an error.
+   */
+  epoch: number;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/rooms/keys/commit/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = RoomsKeysCommitPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/rooms/keys/commit/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = RoomsKeysCommitResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/rooms/keys/commit/0.1",
+  "title": "Rooms Keys Commit — payload",
+  "description": "A room's owner delivers an MLS Commit to a member's key-holding agent, advancing it one epoch. Every member must apply every commit, in order: an agent that misses one is stuck at its last epoch and can open nothing sealed after it.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "roomId",
+    "commit",
+    "epoch"
+  ],
+  "properties": {
+    "roomId": {
+      "type": "string",
+      "description": "The room whose group is advancing."
+    },
+    "commit": {
+      "type": "string",
+      "description": "The MLS Commit message, base64url."
+    },
+    "epoch": {
+      "type": "integer",
+      "minimum": 1,
+      "description": "The MLS epoch this commit produces — the recipient's epoch after applying it. Stated so a recipient can tell a replay from a gap without parsing the commit: equal to its current epoch is a replay, more than one ahead is a gap."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Keys Commit — response payload",
+      "description": "Success response to rooms/keys/commit. Type https://trusttasks.org/spec/rooms/keys/commit/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "epoch"
+      ],
+      "properties": {
+        "epoch": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The recipient's epoch after the operation. On a replay this is unchanged, which is how a sender distinguishes 'applied' from 'already had it' without either being an error."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Keys Commit — response payload",
+      "description": "Success response to rooms/keys/commit. Type https://trusttasks.org/spec/rooms/keys/commit/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "epoch"
+      ],
+      "properties": {
+        "epoch": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The recipient's epoch after the operation. On a replay this is unchanged, which is how a sender distinguishes 'applied' from 'already had it' without either being an error."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/rooms/keys/key-package/0.1/payload.ts

@@ -0,0 +1,196 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/rooms/keys/key-package/0.1/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+/**
+ * An invited party asks the agent that will hold its room keys to mint an MLS KeyPackage, so the room's owner can add it to the group. The private half stays with the agent; only the KeyPackage travels.
+ */
+export interface RoomsKeysKeyPackagePayload {
+  /**
+   * The room to mint a KeyPackage for. Scoped per room rather than reused across rooms: one KeyPackage presented to two rooms correlates a member across them, which is the linkage a `private` room exists to deny.
+   */
+  roomId: string;
+  /**
+   * The invitation credential (VIC) the room issued to this party, serialized per the governing profile. Where an implementation requires one — and one that mints group state on unauthenticated request should — this is what authorizes the mint.
+   */
+  invitation?: string;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+/**
+ * Success response to rooms/keys/key-package. Type https://trusttasks.org/spec/rooms/keys/key-package/0.1#response.
+ */
+export interface RoomsKeysKeyPackageResponsePayload {
+  /**
+   * The MLS KeyPackage, base64url. Public: it carries a signature key, an HPKE init key and the leaf's credential, and nothing that opens anything.
+   */
+  keyPackage: string;
+  /**
+   * When the KeyPackage stops being offered. A KeyPackage is single-use and an unused one is retained key material, so an implementation SHOULD bound how long it holds the private half.
+   */
+  expiresAt?: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/rooms/keys/key-package/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = RoomsKeysKeyPackagePayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/rooms/keys/key-package/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = RoomsKeysKeyPackageResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/rooms/keys/key-package/0.1",
+  "title": "Rooms Keys Key-Package — payload",
+  "description": "An invited party asks the agent that will hold its room keys to mint an MLS KeyPackage, so the room's owner can add it to the group. The private half stays with the agent; only the KeyPackage travels.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "roomId"
+  ],
+  "properties": {
+    "roomId": {
+      "type": "string",
+      "description": "The room to mint a KeyPackage for. Scoped per room rather than reused across rooms: one KeyPackage presented to two rooms correlates a member across them, which is the linkage a `private` room exists to deny."
+    },
+    "invitation": {
+      "type": "string",
+      "description": "The invitation credential (VIC) the room issued to this party, serialized per the governing profile. Where an implementation requires one — and one that mints group state on unauthenticated request should — this is what authorizes the mint."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Keys Key-Package — response payload",
+      "description": "Success response to rooms/keys/key-package. Type https://trusttasks.org/spec/rooms/keys/key-package/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "keyPackage"
+      ],
+      "properties": {
+        "keyPackage": {
+          "type": "string",
+          "description": "The MLS KeyPackage, base64url. Public: it carries a signature key, an HPKE init key and the leaf's credential, and nothing that opens anything."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the KeyPackage stops being offered. A KeyPackage is single-use and an unused one is retained key material, so an implementation SHOULD bound how long it holds the private half."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Keys Key-Package — response payload",
+      "description": "Success response to rooms/keys/key-package. Type https://trusttasks.org/spec/rooms/keys/key-package/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "keyPackage"
+      ],
+      "properties": {
+        "keyPackage": {
+          "type": "string",
+          "description": "The MLS KeyPackage, base64url. Public: it carries a signature key, an HPKE init key and the leaf's credential, and nothing that opens anything."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the KeyPackage stops being offered. A KeyPackage is single-use and an unused one is retained key material, so an implementation SHOULD bound how long it holds the private half."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;