@openvtc/trust-tasks 0.21.9 → 0.21.11

package/src/auth/authenticate/0.2/payload.ts

@@ -0,0 +1,444 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/auth/authenticate/0.2/payload.schema.json
+ */
+
+import type { Ext, Session_AuthV0_2 as Session, TokenBundle } from "../../../_shared/components.js";
+
+
+/**
+ * The subject presents a previously-issued challenge along with the framework `proof` that binds the document to their VID. The proof IS the authentication. 0.2 adds the optional `sessionKey` member, a did:key VID the consumer binds to the created session so later documents in that session can be signed with it instead of the subject's own key.
+ */
+export interface AuthAuthenticate {
+  /**
+   * The exact challenge value returned by a prior auth/challenge call. Consumers MUST reject mismatch, expired, or re-used challenges.
+   */
+  challenge: string;
+  /**
+   * The sessionId returned alongside the challenge. Consumers use it to look up the server-side challenge binding.
+   */
+  sessionId: string;
+  /**
+   * Optional capability tags the subject is requesting on the issued tokens. The consumer's authorization layer decides which are granted; the issued TokenBundle's `scope` MAY be a subset.
+   */
+  scope?: string[];
+  /**
+   * A did:key VID the producer asks the consumer to bind to the session this authenticate document creates. The producer MUST hold the corresponding private key and SHOULD keep it non-extractable (for example, a WebCrypto non-extractable key). Once bound, the consumer MUST accept a framework `proof` made by this key, with `proofPurpose: authentication`, as the subject — for this session only, bounded by the session's `expiresAt` and `acr`, and never where a specification requires an `assertionMethod` attestation (SPEC.md §7.2 item 10; see Security & Privacy). The consumer MAY refuse a key type it does not support with `auth/authenticate:sessionKeyUnsupported`. It sits inside `payload`, so the subject's own `authentication` proof on this document covers it — a party cannot bind a session key without signing for it.
+   */
+  sessionKey?: string;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+/**
+ * Issued by the auth service after verifying the proof on the authenticate document. Carried in a Trust Task document whose type is https://trusttasks.org/spec/auth/authenticate/0.2#response.
+ */
+export interface AuthAuthenticateResponsePayload {
+  /**
+   * The session the consumer has just created or refreshed for this subject. Carries `sessionKey` when the request bound one.
+   */
+  session: Session;
+  /**
+   * Access + optional refresh tokens. Consumers MAY omit a refresh token when their policy doesn't support refresh.
+   */
+  tokens: TokenBundle;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, Session, TokenBundle };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/auth/authenticate/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = AuthAuthenticate;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/auth/authenticate/0.2#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = AuthAuthenticateResponsePayload;
+
+/**
+ * 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/auth/authenticate/0.2",
+  "title": "Auth — Authenticate",
+  "description": "The subject presents a previously-issued challenge along with the framework `proof` that binds the document to their VID. The proof IS the authentication. 0.2 adds the optional `sessionKey` member, a did:key VID the consumer binds to the created session so later documents in that session can be signed with it instead of the subject's own key.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "challenge",
+    "sessionId"
+  ],
+  "properties": {
+    "challenge": {
+      "type": "string",
+      "minLength": 16,
+      "description": "The exact challenge value returned by a prior auth/challenge call. Consumers MUST reject mismatch, expired, or re-used challenges."
+    },
+    "sessionId": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The sessionId returned alongside the challenge. Consumers use it to look up the server-side challenge binding."
+    },
+    "scope": {
+      "type": "array",
+      "items": {
+        "type": "string",
+        "minLength": 1
+      },
+      "description": "Optional capability tags the subject is requesting on the issued tokens. The consumer's authorization layer decides which are granted; the issued TokenBundle's `scope` MAY be a subset."
+    },
+    "sessionKey": {
+      "type": "string",
+      "pattern": "^did:key:z[1-9A-HJ-NP-Za-km-z]+$",
+      "maxLength": 512,
+      "description": "A did:key VID the producer asks the consumer to bind to the session this authenticate document creates. The producer MUST hold the corresponding private key and SHOULD keep it non-extractable (for example, a WebCrypto non-extractable key). Once bound, the consumer MUST accept a framework `proof` made by this key, with `proofPurpose: authentication`, as the subject — for this session only, bounded by the session's `expiresAt` and `acr`, and never where a specification requires an `assertionMethod` attestation (SPEC.md §7.2 item 10; see Security & Privacy). The consumer MAY refuse a key type it does not support with `auth/authenticate:sessionKeyUnsupported`. It sits inside `payload`, so the subject's own `authentication` proof on this document covers it — a party cannot bind a session key without signing for it."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Auth Authenticate — response payload",
+      "description": "Issued by the auth service after verifying the proof on the authenticate document. Carried in a Trust Task document whose type is https://trusttasks.org/spec/auth/authenticate/0.2#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "session",
+        "tokens"
+      ],
+      "properties": {
+        "session": {
+          "$ref": "#/$defs/Session",
+          "description": "The session the consumer has just created or refreshed for this subject. Carries `sessionKey` when the request bound one."
+        },
+        "tokens": {
+          "$ref": "#/$defs/TokenBundle",
+          "description": "Access + optional refresh tokens. Consumers MAY omit a refresh token when their policy doesn't support refresh."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    },
+    "TokenBundle": {
+      "$anchor": "tokenBundle",
+      "title": "TokenBundle",
+      "description": "An access token (typically short-lived JWT) paired with an optional refresh token (typically long-lived opaque string). The shapes follow OAuth 2.0 (RFC 6749 §5.1) conventions but are not coupled to any particular OAuth profile.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "accessToken",
+        "tokenType",
+        "expiresIn"
+      ],
+      "properties": {
+        "accessToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Bearer-style access token. Consumers presenting this token to downstream services prove the holder of the original session. Format is consumer-defined — JWT is common, but opaque strings are also valid."
+        },
+        "refreshToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Long-lived token redeemable via auth/refresh for a new access token. MAY be absent when the issuer does not support refresh."
+        },
+        "tokenType": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Token presentation scheme. Almost always \"Bearer\"; reserved for future schemes."
+        },
+        "expiresIn": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "Seconds from issuance until the access token expires."
+        },
+        "refreshExpiresIn": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "Seconds from issuance until the refresh token expires, when one was issued."
+        },
+        "scope": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Capability tags effective on this token. Format is consumer-defined; the framework imposes no syntax."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "Session": {
+      "$anchor": "session",
+      "title": "Session",
+      "description": "A logical authentication context bound to a subject. Producers and consumers exchange Session-shaped data in challenge issuance, authentication responses, and introspection (whoami).",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "subject",
+        "issuedAt",
+        "expiresAt"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Opaque, server-chosen session identifier. Stable for the lifetime of the session. Consumers MUST treat the value as opaque; no structure is implied."
+        },
+        "subject": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The authenticated party's VID (typically a DID URL)."
+        },
+        "issuedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO-8601 timestamp when the session was created."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO-8601 timestamp when the session ceases to be valid. Producers SHOULD refresh before this time; consumers MUST reject after."
+        },
+        "amr": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Authentication Methods References per [RFC 8176]. Typical values: \"did\" (challenge-response), \"passkey\" (WebAuthn), \"vta\" (verifiable-trust agent approval). Multi-factor sessions list every method used."
+        },
+        "acr": {
+          "type": "string",
+          "description": "Authentication Context Class Reference per [OIDC Core §2]. Profiles define their own values; the recommended set is \"aal1\" (single-factor DID auth), \"aal2\" (a second possession-or-biometric factor confirmed), and \"aal3\" (hardware-bound second factor)."
+        },
+        "sessionKey": {
+          "type": "string",
+          "pattern": "^did:key:z[1-9A-HJ-NP-Za-km-z]+$",
+          "maxLength": 512,
+          "description": "The did:key VID bound to this session by auth/authenticate/0.2, when the producer registered one. Present here so introspection (auth/whoami, auth/sessions/list) can show the binding a client already holds; it is descriptive, not an additional grant — the binding, its scope and its lifetime are governed entirely by the auth/authenticate/0.2 specification that established it. Absent when the session was established without a session key, or by a specification version that does not carry one."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    }
+  }
+} 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": "Auth Authenticate — response payload",
+      "description": "Issued by the auth service after verifying the proof on the authenticate document. Carried in a Trust Task document whose type is https://trusttasks.org/spec/auth/authenticate/0.2#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "session",
+        "tokens"
+      ],
+      "properties": {
+        "session": {
+          "$ref": "#/$defs/Session",
+          "description": "The session the consumer has just created or refreshed for this subject. Carries `sessionKey` when the request bound one."
+        },
+        "tokens": {
+          "$ref": "#/$defs/TokenBundle",
+          "description": "Access + optional refresh tokens. Consumers MAY omit a refresh token when their policy doesn't support refresh."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "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-]+)+$"
+      }
+    },
+    "TokenBundle": {
+      "$anchor": "tokenBundle",
+      "title": "TokenBundle",
+      "description": "An access token (typically short-lived JWT) paired with an optional refresh token (typically long-lived opaque string). The shapes follow OAuth 2.0 (RFC 6749 §5.1) conventions but are not coupled to any particular OAuth profile.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "accessToken",
+        "tokenType",
+        "expiresIn"
+      ],
+      "properties": {
+        "accessToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Bearer-style access token. Consumers presenting this token to downstream services prove the holder of the original session. Format is consumer-defined — JWT is common, but opaque strings are also valid."
+        },
+        "refreshToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Long-lived token redeemable via auth/refresh for a new access token. MAY be absent when the issuer does not support refresh."
+        },
+        "tokenType": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Token presentation scheme. Almost always \"Bearer\"; reserved for future schemes."
+        },
+        "expiresIn": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "Seconds from issuance until the access token expires."
+        },
+        "refreshExpiresIn": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "Seconds from issuance until the refresh token expires, when one was issued."
+        },
+        "scope": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Capability tags effective on this token. Format is consumer-defined; the framework imposes no syntax."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    },
+    "Session": {
+      "$anchor": "session",
+      "title": "Session",
+      "description": "A logical authentication context bound to a subject. Producers and consumers exchange Session-shaped data in challenge issuance, authentication responses, and introspection (whoami).",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "subject",
+        "issuedAt",
+        "expiresAt"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "minLength": 1,
+          "description": "Opaque, server-chosen session identifier. Stable for the lifetime of the session. Consumers MUST treat the value as opaque; no structure is implied."
+        },
+        "subject": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The authenticated party's VID (typically a DID URL)."
+        },
+        "issuedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO-8601 timestamp when the session was created."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "ISO-8601 timestamp when the session ceases to be valid. Producers SHOULD refresh before this time; consumers MUST reject after."
+        },
+        "amr": {
+          "type": "array",
+          "minItems": 1,
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Authentication Methods References per [RFC 8176]. Typical values: \"did\" (challenge-response), \"passkey\" (WebAuthn), \"vta\" (verifiable-trust agent approval). Multi-factor sessions list every method used."
+        },
+        "acr": {
+          "type": "string",
+          "description": "Authentication Context Class Reference per [OIDC Core §2]. Profiles define their own values; the recommended set is \"aal1\" (single-factor DID auth), \"aal2\" (a second possession-or-biometric factor confirmed), and \"aal3\" (hardware-bound second factor)."
+        },
+        "sessionKey": {
+          "type": "string",
+          "pattern": "^did:key:z[1-9A-HJ-NP-Za-km-z]+$",
+          "maxLength": 512,
+          "description": "The did:key VID bound to this session by auth/authenticate/0.2, when the producer registered one. Present here so introspection (auth/whoami, auth/sessions/list) can show the binding a client already holds; it is descriptive, not an additional grant — the binding, its scope and its lifetime are governed entirely by the auth/authenticate/0.2 specification that established it. Absent when the session was established without a session key, or by a specification version that does not carry one."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext",
+          "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+        }
+      }
+    }
+  }
+} 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/auth/passkey/login/finish/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/passkey/login/finish/0.1/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session, TokenBundle } from "../../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session, TokenBundle } from "../../../../../_shared/components.js";
 
 
 /**

package/src/auth/passkey/login/finish/0.2/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/passkey/login/finish/0.2/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session, TokenBundle } from "../../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session, TokenBundle } from "../../../../../_shared/components.js";
 
 
 /**

package/src/auth/refresh/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/refresh/0.1/payload.schema.json
  */
 
-import type { Ext, Session, TokenBundle } from "../../../_shared/components.js";
+import type { Ext, Session_AuthV0_1 as Session, TokenBundle } from "../../../_shared/components.js";
 
 
 /**

package/src/auth/sessions/list/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/sessions/list/0.1/payload.schema.json
  */
 
-import type { Ext, Session } from "../../../../_shared/components.js";
+import type { Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/step-up/approve-response/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/step-up/approve-response/0.1/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session } from "../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/step-up/approve-response/0.2/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/step-up/approve-response/0.2/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session } from "../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/step-up/approve-response/0.3/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/step-up/approve-response/0.3/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session } from "../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/step-up/approve-response/0.4/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/step-up/approve-response/0.4/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session } from "../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/step-up/approve-response/0.5/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/step-up/approve-response/0.5/payload.schema.json
  */
 
-import type { AuthenticatorAssertionResponseLogin, Ext, Session } from "../../../../_shared/components.js";
+import type { AuthenticatorAssertionResponseLogin, Ext, Session_AuthV0_1 as Session } from "../../../../_shared/components.js";
 
 
 /**

package/src/auth/whoami/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/auth/whoami/0.1/payload.schema.json
  */
 
-import type { Ext, Session } from "../../../_shared/components.js";
+import type { Ext, Session_AuthV0_1 as Session } from "../../../_shared/components.js";
 
 
 /**

package/src/index.ts

@@ -29,7 +29,9 @@ export * as PasskeyInviteShared_v0_1 from "./auth/_shared/0.1/passkey-invite.js"
 export * as SessionShared_v0_1 from "./auth/_shared/0.1/session.js";
 export * as TokensShared_v0_1 from "./auth/_shared/0.1/tokens.js";
 export * as WebauthnShared_v0_1 from "./auth/_shared/0.1/webauthn.js";
+export * as SessionShared_v0_2 from "./auth/_shared/0.2/session.js";
 export * as AuthAuthenticate_v0_1 from "./auth/authenticate/0.1/payload.js";
+export * as AuthAuthenticate_v0_2 from "./auth/authenticate/0.2/payload.js";
 export * as AuthChallenge_v0_1 from "./auth/challenge/0.1/payload.js";
 export * as AuthPasskeyAdminList_v0_1 from "./auth/passkey/admin-list/0.1/payload.js";
 export * as AuthPasskeyEnrollFinish_v0_1 from "./auth/passkey/enroll/finish/0.1/payload.js";
@@ -394,6 +396,7 @@ export * as TrustCeremonyReceipt_v0_1 from "./trust-ceremony-receipt/0.1/payload
 export * as TrustTaskControl_v0_1 from "./trust-task-control/0.1/payload.js";
 export * as TrustTaskDiscovery_v0_1 from "./trust-task-discovery/0.1/payload.js";
 export * as TrustTaskDiscovery_v0_2 from "./trust-task-discovery/0.2/payload.js";
+export * as TrustTaskDiscovery_v0_3 from "./trust-task-discovery/0.3/payload.js";
 export * as TrustTaskError_v0_1 from "./trust-task-error/0.1/payload.js";
 export * as TrustTaskError_v0_2 from "./trust-task-error/0.2/payload.js";
 export * as TrustTaskError_v0_3 from "./trust-task-error/0.3/payload.js";