@openvtc/trust-tasks 0.14.2 → 0.16.0

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

@@ -3,54 +3,8 @@
  * Source: specs/vault/upsert/0.1/payload.schema.json
  */
 
-/**
- * A single binding target for a vault entry. Tagged union over the discriminator `kind`. A VaultEntry's `targets` array MAY mix any number of these.
- */
-export type SiteTarget = WebOrigin | Did | IosApp | AndroidApp;
-/**
- * Discriminator for the secret type stored in the entry. Definitions:
- * - `password` — username + password (+ optional TOTP seed).
- * - `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).
- * - `oauth-tokens` — OAuth 2.0 refresh + access token bundle for a specific provider.
- * - `did-self-issued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.
- * - `didcomm-peer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.
- * - `bearer-token` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).
- * - `ssh-key` — SSH private key + comment.
- * - `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.
- */
-export type SecretKind =
-  | "password"
-  | "passkey"
-  | "oauth-tokens"
-  | "did-self-issued"
-  | "didcomm-peer"
-  | "bearer-token"
-  | "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: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;
-/**
- * Discriminator for the secret type stored in the entry. Definitions:
- * - `password` — username + password (+ optional TOTP seed).
- * - `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).
- * - `oauth-tokens` — OAuth 2.0 refresh + access token bundle for a specific provider.
- * - `did-self-issued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.
- * - `didcomm-peer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.
- * - `bearer-token` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).
- * - `ssh-key` — SSH private key + comment.
- * - `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.
- */
-export type SecretKind1 =
-  | "password"
-  | "passkey"
-  | "oauth-tokens"
-  | "did-self-issued"
-  | "didcomm-peer"
-  | "bearer-token"
-  | "ssh-key"
-  | "custom";
+import type { AndroidApp_VaultV0_1 as AndroidApp, AttachmentRef_VaultV0_1 as AttachmentRef, Did_VaultV0_1 as Did, DidcommAuthcryptEnvelope_VaultV0_1 as DidcommAuthcryptEnvelope, Ext, HpkeArmoredEnvelope_VaultV0_1 as HpkeArmoredEnvelope, IosApp_VaultV0_1 as IosApp, SealedEnvelope_VaultV0_1 as SealedEnvelope, SecretKind_VaultV0_1 as SecretKind, SiteTarget_VaultV0_1 as SiteTarget, TspMessageEnvelope_VaultV0_1 as TspMessageEnvelope, VaultEntry_VaultV0_1 as VaultEntry, WebOrigin_VaultV0_1 as WebOrigin } from "../../../_shared/components.js";
+
 
 /**
  * Create a new vault entry or update an existing one. The secret material — if present — rides inside a pluggable cipher envelope (see `vault/_shared/0.1/sealed-envelope`), so the Trust Task carries ciphertext and an authenticator, not plaintext. Updates may be partial: any populated metadata field replaces the current value; omitted fields are left untouched; explicit null clears the field (per `clearFields`). Optimistic-concurrency check via `expectedVersion`.
@@ -80,6 +34,9 @@ export interface VaultUpsertPayload {
   selectors?: string[];
   customFieldNames?: string[];
   expiresAt?: string;
+  /**
+   * 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.
+   */
   sealedSecret?: SealedEnvelope;
   /**
    * List of metadata fields to explicitly clear on this upsert. Distinguishes "don't touch" (field omitted from payload) from "clear" (field listed here).
@@ -87,92 +44,6 @@ export interface VaultUpsertPayload {
   clearFields?: ("notes" | "favicon" | "expiresAt" | "tags" | "selectors" | "customFieldNames")[];
   ext?: Ext;
 }
-export interface WebOrigin {
-  kind: "web-origin";
-  /**
-   * Web origin per RFC 6454 (scheme + host + optional port), e.g. "https://github.com". Compared by exact string equality after canonicalisation (lowercase host, default port elided). Consumers wanting subdomain coverage SHOULD add multiple targets, not encode a wildcard.
-   */
-  origin: string;
-}
-export interface Did {
-  kind: "did";
-  /**
-   * DID identifying the relying party (e.g. did:web:rp.example). The vault maintainer is responsible for any DID resolution required to act on this entry.
-   */
-  did: string;
-}
-export interface IosApp {
-  kind: "ios-app";
-  /**
-   * iOS bundle identifier in reverse-DNS form (e.g. "com.github.stwalkerster.codehub"). Compared by exact string equality. Matches when an iOS Companion identifies the requesting app via its bundle id (typically via the OS Credential Manager integration).
-   */
-  bundleId: string;
-  /**
-   * Optional Apple Developer Team identifier (10-character alphanumeric). When supplied, the maintainer SHOULD also verify the team id of the requesting app before matching — defense in depth against bundle-id squatting on jailbroken devices.
-   */
-  teamId?: string;
-}
-export interface AndroidApp {
-  kind: "android-app";
-  /**
-   * Android package name in reverse-DNS form (e.g. "com.github.android").
-   */
-  packageName: string;
-  /**
-   * SHA-256 fingerprints of the app's signing certificates, in colon-separated hex (the format `apksigner` and the Play Console emit). At least one fingerprint MUST be present. The maintainer matches when ANY of the provided fingerprints matches the requesting app's signature — this supports apps signed by multiple keys (e.g. during certificate rotation via Play App Signing).
-   *
-   * @minItems 1
-   */
-  sha256CertFingerprints: [string, ...string[]];
-}
-/**
- * DIDComm v2 authcrypt JWE (ECDH-1PU + A256CBC-HS512, X25519/P-256 key agreement). Sender authentication is the JWE's `skid` — the producer's DID#keyAgreement. The maintainer's keyAgreement key is the recipient. Cleartext is JCS-canonical JSON of the variant's payload type.
- *
- * M2A is the only implementation today; this is also the canonical default for new code.
- */
-export interface DidcommAuthcryptEnvelope {
-  envelope: "didcomm-authcrypt";
-  /**
-   * Compact DIDComm v2 JWE (base64url-encoded, dot-separated). Unpacks via the framework's standard DIDComm machinery; cleartext is the payload-specific JSON.
-   */
-  jwe: string;
-}
-/**
- * OpenPGP-style ASCII-armored HPKE bundle — the existing OpenVTC sealed-transfer wire form (X25519-HKDF-SHA256 KEM + ChaCha20-Poly1305 AEAD, framed in armor with Bundle-Id / Digest-Algo headers and a CRC24 checksum). Producer assertion (`did-signed` / `attested` / `pinned-only`) is the integrity / authenticity anchor.
- *
- * No open-source implementation reads this yet outside vta-sdk's `sealed_transfer` crate; new code SHOULD prefer the DIDComm variant. Defined here for parity with the existing offline-bundle / cross-VTA workflows that the design plan reserves for M5+.
- */
-export interface HpkeArmoredEnvelope {
-  envelope: "hpke-armored";
-  /**
-   * ASCII-armored bundle text. Multi-line base64 with framing headers + CRC24.
-   */
-  armored: string;
-  /**
-   * did:key identifier of the X25519 public key the envelope was sealed to. The recipient uses this to select the matching private key.
-   */
-  recipientKeyId: string;
-  /**
-   * Producer-assertion mode per the sealed-transfer framework. `did-signed` = Ed25519 signature by issuer; `attested` = TEE attestation quote (e.g. Nitro); `pinned-only` = OOB SHA-256 digest only (dev/test, NOT for production).
-   */
-  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 (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
- */
-export interface TspMessageEnvelope {
-  envelope: "tsp-message";
-  /**
-   * Base64url-encoded TSP message bytes. Format reference: https://trustoverip.github.io/tswg-tsp-specification/#message-format
-   */
-  message: string;
-}
-/**
- * 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.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
-}
 export interface VaultUpsertResponsePayload {
   entry: VaultEntry;
   /**
@@ -181,130 +52,9 @@ export interface VaultUpsertResponsePayload {
   created?: boolean;
   ext?: Ext;
 }
-export interface VaultEntry {
-  /**
-   * Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.
-   */
-  id: string;
-  /**
-   * Identifier of the trust context (persona) the entry belongs to. Opaque string interpreted by the vault maintainer; corresponds to a single ContextRecord on the VTA side.
-   */
-  contextId: string;
-  /**
-   * One or more binding targets — web origins, mobile app identifiers, and/or DIDs — that this credential applies to. A request from any matching target uses this entry. A typical entry for a service that exists as both a website and mobile apps will list a web origin, an iOS bundle id, and an Android package id; passkeys for that service typically list only the origin (because iOS Associated Domains and Android Asset Links bind apps to the domain at the OS level).
-   *
-   * @minItems 1
-   */
-  targets: [SiteTarget, ...SiteTarget[]];
-  /**
-   * Human-readable display name (e.g. "Work GitHub", "Personal bank — checking"). Maintainers MAY enforce a maximum length; the wire spec does not.
-   */
-  label: string;
-  secretKind: SecretKind1;
-  /**
-   * User-defined tags for organisation and filtering (e.g. ["family", "finance"]). Maintainers MAY enforce a maximum count; the wire spec does not.
-   */
-  tags?: string[];
-  /**
-   * Non-sensitive notes the user attached to the entry. Visible in metadata view (suitable for support contact, account number, expiry policy memos). SENSITIVE notes belong in the secret payload as a `secureNotes` field — those are only released by vault/release/0.1.
-   */
-  notes?: string;
-  /**
-   * Optional URI of an icon to display in the consumer UI. Maintainers MAY fetch and cache; consumers SHOULD treat as untrusted content and fetch via a sandboxed pipeline.
-   */
-  favicon?: string;
-  /**
-   * Opaque maintainer-defined selector strings fed to the policy engine when this entry is requested (e.g. "recent_uv_required", "network_class=corp", "step_up_push"). Consumers MUST treat selectors as opaque; they exist for policy authoring on the maintainer side.
-   */
-  selectors?: string[];
-  /**
-   * Names of additional fields the user has attached (e.g. ["security-question-1", "account-number"]). The VALUES live in the secret payload and are only delivered by vault/release/0.1. Exposing names in metadata lets the consumer render the right form layout before requesting release.
-   */
-  customFieldNames?: string[];
-  /**
-   * References to encrypted blobs associated with the entry (recovery codes, PEM files, screenshots of authenticator setup). The blobs themselves are fetched via a separate mechanism the maintainer documents; metadata view exposes only the descriptor.
-   */
-  attachments?: AttachmentRef[];
-  /**
-   * Optional time after which the credential is no longer expected to be valid (e.g. an OAuth refresh token's known expiry, a time-limited API token, an enterprise password rotation policy). Maintainers MAY surface this in the consumer UI as a warning.
-   */
-  expiresAt?: string;
-  /**
-   * Set by the maintainer (via HIBP integration or equivalent) when the password material associated with this entry is known to appear in a public breach. Consumers SHOULD surface this prominently. Cleared when the user rotates the password and the new password is not in any known breach.
-   */
-  breachedAt?: string;
-  /**
-   * Set whenever the password component of the secret payload is rotated. Maintainers MUST update this on every secret-material change for entries of kind `password` (or any kind that carries a password component). Used by consumers to surface rotation-overdue warnings.
-   */
-  passwordChangedAt?: string;
-  createdAt: string;
-  /**
-   * VID of the consumer that originally created the entry.
-   */
-  createdBy?: string;
-  updatedAt: string;
-  /**
-   * VID of the consumer that last modified the entry.
-   */
-  updatedBy?: string;
-  /**
-   * Most recent time the entry was used (either released or proxy-login performed). Maintainers MAY return this with reduced precision (e.g. hour-floored) when releasing to a less-trusted consumer.
-   */
-  lastUsedAt?: string;
-  /**
-   * Monotonic version counter incremented on every mutation. Used by consumers for optimistic-concurrency checks on vault/upsert and as the seq baseline for vault/sync.
-   */
-  version: number;
-  /**
-   * Optional cached DID the entry will act AS for DID-shaped flows — mirrors the `did` field of the entry's secret payload when `secretKind` carries one (`did-self-issued`, `didcomm-peer`). Absent for kinds that have no DID concept (`password`, `passkey`, `oauth-tokens`, `bearer-token`, `ssh-key`, `custom`). MAINTAINER-DERIVED, NOT CONSUMER-SUPPLIED: the maintainer MUST recompute this from the canonical secret at every upsert / secret rotation; a producer-supplied value on `vault/upsert/0.1` MUST be ignored (no error, but no honour). Read-only on the wire, present in metadata views so consumers can drive RP-side flows (e.g. fetch `/auth/challenge` keyed on the principal DID before requesting a proxy-login) without releasing the secret.
-   */
-  principalDid?: string;
-  /**
-   * Archival-lifecycle state of this entry. Absent means `active`, so a maintainer that models no lifecycle omits it and every existing document stays valid. Deliberately carries no JSON Schema `default`: a declared default is materialised by generated bindings, which would make an absent `status` reappear as an explicit `"active"` on re-serialisation and break round-trip idempotence for every existing document. This member is what makes `vault/list`'s `status: "all"` selector usable: that view returns entries in every state by design, and without a state on the entry itself a consumer cannot tell which is which. An `archived` entry is hidden from ordinary listings but intact; a `deleted` entry is a tombstone inside its grace window, still restorable until `graceUntil` passes.
-   */
-  status?: "active" | "archived" | "deleted";
-  /**
-   * When the entry was archived. Present iff `status` is `archived`.
-   */
-  archivedAt?: string;
-  /**
-   * When the entry was soft-deleted. Present iff `status` is `deleted`. A soft delete is reversible: this records when the grace window opened, not when the entry ceased to exist.
-   */
-  deletedAt?: string;
-  /**
-   * Deadline after which a `deleted` entry is irreversibly purged. Present iff `status` is `deleted`. It is the one member a consumer showing a trash view actually needs — "deleted" without a deadline cannot be distinguished from "gone", and the difference is whether the holder can still get their credential back.
-   */
-  graceUntil?: string;
-  ext?: Ext1;
-}
-export interface AttachmentRef {
-  /**
-   * Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.
-   */
-  id: string;
-  /**
-   * User-supplied filename (e.g. "recovery-codes.txt").
-   */
-  name: string;
-  /**
-   * Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.
-   */
-  sizeBytes: number;
-  /**
-   * Hex-encoded SHA-256 of the encrypted blob bytes (post-encryption). Lets the consumer verify integrity after fetch.
-   */
-  sha256: string;
-  /**
-   * Optional MIME type hint for the consumer UI (e.g. "text/plain", "application/x-pem-file").
-   */
-  contentType?: string;
-}
-/**
- * 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.
- */
-export interface Ext1 {
-  [k: string]: unknown | undefined;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { AndroidApp, AttachmentRef, Did, DidcommAuthcryptEnvelope, Ext, HpkeArmoredEnvelope, IosApp, SealedEnvelope, SecretKind, SiteTarget, TspMessageEnvelope, VaultEntry, WebOrigin };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vault/upsert/0.1" as const;
@@ -365,7 +115,8 @@ export const PAYLOAD_SCHEMA = {
     },
     "label": {
       "type": "string",
-      "minLength": 1
+      "minLength": 1,
+      "maxLength": 256
     },
     "secretKind": {
       "$ref": "#/$defs/SecretKind"
@@ -500,7 +251,8 @@ export const PAYLOAD_SCHEMA = {
         "label": {
           "type": "string",
           "minLength": 1,
-          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Maintainers MAY enforce a maximum length; the wire spec does not."
+          "maxLength": 256,
+          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Bounded on the wire at 256 characters; a maintainer MAY enforce a shorter limit."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -948,7 +700,8 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "label": {
           "type": "string",
           "minLength": 1,
-          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Maintainers MAY enforce a maximum length; the wire spec does not."
+          "maxLength": 256,
+          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Bounded on the wire at 256 characters; a maintainer MAY enforce a shorter limit."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -1335,6 +1088,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -1348,5 +1102,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;

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

@@ -3,54 +3,8 @@
  * Source: specs/vault/upsert/0.2/payload.schema.json
  */
 
-/**
- * A single binding target for a vault entry. Tagged union over the discriminator `kind`. A VaultEntry's `targets` array MAY mix any number of these.
- */
-export type SiteTarget = WebOrigin | Did | IosApp | AndroidApp;
-/**
- * Discriminator for the secret type stored in the entry. Definitions:
- * - `password` — username + password (+ optional TOTP seed).
- * - `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).
- * - `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.
- * - `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.
- * - `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.
- * - `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).
- * - `sshKey` — SSH private key + comment.
- * - `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.
- */
-export type SecretKind =
-  | "password"
-  | "passkey"
-  | "oauthTokens"
-  | "didSelfIssued"
-  | "didcommPeer"
-  | "bearerToken"
-  | "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: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;
-/**
- * Discriminator for the secret type stored in the entry. Definitions:
- * - `password` — username + password (+ optional TOTP seed).
- * - `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).
- * - `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.
- * - `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.
- * - `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.
- * - `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).
- * - `sshKey` — SSH private key + comment.
- * - `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.
- */
-export type SecretKind1 =
-  | "password"
-  | "passkey"
-  | "oauthTokens"
-  | "didSelfIssued"
-  | "didcommPeer"
-  | "bearerToken"
-  | "sshKey"
-  | "custom";
+import type { AndroidApp_VaultV0_2 as AndroidApp, AttachmentRef_VaultV0_1 as AttachmentRef, Did_VaultV0_2 as Did, DidcommAuthcryptEnvelope_VaultV0_2 as DidcommAuthcryptEnvelope, Ext, HpkeArmoredEnvelope_VaultV0_2 as HpkeArmoredEnvelope, IosApp_VaultV0_2 as IosApp, SealedEnvelope_VaultV0_2 as SealedEnvelope, SecretKind_VaultV0_2 as SecretKind, SiteTarget_VaultV0_2 as SiteTarget, TspMessageEnvelope_VaultV0_2 as TspMessageEnvelope, VaultEntry_VaultV0_2 as VaultEntry, WebOrigin_VaultV0_2 as WebOrigin } from "../../../_shared/components.js";
+
 
 /**
  * Create a new vault entry or update an existing one. The secret material — if present — rides inside a pluggable cipher envelope (see `vault/_shared/0.1/sealed-envelope`), so the Trust Task carries ciphertext and an authenticator, not plaintext. Updates may be partial: any populated metadata field replaces the current value; omitted fields are left untouched; explicit null clears the field (per `clearFields`). Optimistic-concurrency check via `expectedVersion`.
@@ -80,6 +34,9 @@ export interface VaultUpsertPayload {
   selectors?: string[];
   customFieldNames?: string[];
   expiresAt?: string;
+  /**
+   * 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.
+   */
   sealedSecret?: SealedEnvelope;
   /**
    * List of metadata fields to explicitly clear on this upsert. Distinguishes "don't touch" (field omitted from payload) from "clear" (field listed here).
@@ -87,92 +44,6 @@ export interface VaultUpsertPayload {
   clearFields?: ("notes" | "favicon" | "expiresAt" | "tags" | "selectors" | "customFieldNames")[];
   ext?: Ext;
 }
-export interface WebOrigin {
-  kind: "webOrigin";
-  /**
-   * Web origin per RFC 6454 (scheme + host + optional port), e.g. "https://github.com". Compared by exact string equality after canonicalisation (lowercase host, default port elided). Consumers wanting subdomain coverage SHOULD add multiple targets, not encode a wildcard.
-   */
-  origin: string;
-}
-export interface Did {
-  kind: "did";
-  /**
-   * DID identifying the relying party (e.g. did:web:rp.example). The vault maintainer is responsible for any DID resolution required to act on this entry.
-   */
-  did: string;
-}
-export interface IosApp {
-  kind: "iosApp";
-  /**
-   * iOS bundle identifier in reverse-DNS form (e.g. "com.github.stwalkerster.codehub"). Compared by exact string equality. Matches when an iOS Companion identifies the requesting app via its bundle id (typically via the OS Credential Manager integration).
-   */
-  bundleId: string;
-  /**
-   * Optional Apple Developer Team identifier (10-character alphanumeric). When supplied, the maintainer SHOULD also verify the team id of the requesting app before matching — defense in depth against bundle-id squatting on jailbroken devices.
-   */
-  teamId?: string;
-}
-export interface AndroidApp {
-  kind: "androidApp";
-  /**
-   * Android package name in reverse-DNS form (e.g. "com.github.android").
-   */
-  packageName: string;
-  /**
-   * SHA-256 fingerprints of the app's signing certificates, in colon-separated hex (the format `apksigner` and the Play Console emit). At least one fingerprint MUST be present. The maintainer matches when ANY of the provided fingerprints matches the requesting app's signature — this supports apps signed by multiple keys (e.g. during certificate rotation via Play App Signing).
-   *
-   * @minItems 1
-   */
-  sha256CertFingerprints: [string, ...string[]];
-}
-/**
- * DIDComm v2 authcrypt JWE (ECDH-1PU + A256CBC-HS512, X25519/P-256 key agreement). Sender authentication is the JWE's `skid` — the producer's DID#keyAgreement. The maintainer's keyAgreement key is the recipient. Cleartext is JCS-canonical JSON of the variant's payload type.
- *
- * M2A is the only implementation today; this is also the canonical default for new code.
- */
-export interface DidcommAuthcryptEnvelope {
-  envelope: "didcommAuthcrypt";
-  /**
-   * Compact DIDComm v2 JWE (base64url-encoded, dot-separated). Unpacks via the framework's standard DIDComm machinery; cleartext is the payload-specific JSON.
-   */
-  jwe: string;
-}
-/**
- * OpenPGP-style ASCII-armored HPKE bundle — the existing OpenVTC sealed-transfer wire form (X25519-HKDF-SHA256 KEM + ChaCha20-Poly1305 AEAD, framed in armor with Bundle-Id / Digest-Algo headers and a CRC24 checksum). Producer assertion (`didSigned` / `attested` / `pinnedOnly`) is the integrity / authenticity anchor.
- *
- * No open-source implementation reads this yet outside vta-sdk's `sealed_transfer` crate; new code SHOULD prefer the DIDComm variant. Defined here for parity with the existing offline-bundle / cross-VTA workflows that the design plan reserves for M5+.
- */
-export interface HpkeArmoredEnvelope {
-  envelope: "hpkeArmored";
-  /**
-   * ASCII-armored bundle text. Multi-line base64 with framing headers + CRC24.
-   */
-  armored: string;
-  /**
-   * did:key identifier of the X25519 public key the envelope was sealed to. The recipient uses this to select the matching private key.
-   */
-  recipientKeyId: string;
-  /**
-   * Producer-assertion mode per the sealed-transfer framework. `didSigned` = Ed25519 signature by issuer; `attested` = TEE attestation quote (e.g. Nitro); `pinnedOnly` = OOB SHA-256 digest only (dev/test, NOT for production).
-   */
-  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 (`envelopeUnsupported`) until they're wired up — rather than silently failing in DIDComm parsing.
- */
-export interface TspMessageEnvelope {
-  envelope: "tspMessage";
-  /**
-   * Base64url-encoded TSP message bytes. Format reference: https://trustoverip.github.io/tswg-tsp-specification/#message-format
-   */
-  message: string;
-}
-/**
- * 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.
- */
-export interface Ext {
-  [k: string]: unknown | undefined;
-}
 export interface VaultUpsertResponsePayload {
   entry: VaultEntry;
   /**
@@ -181,114 +52,9 @@ export interface VaultUpsertResponsePayload {
   created?: boolean;
   ext?: Ext;
 }
-export interface VaultEntry {
-  /**
-   * Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.
-   */
-  id: string;
-  /**
-   * Identifier of the trust context (persona) the entry belongs to. Opaque string interpreted by the vault maintainer; corresponds to a single ContextRecord on the VTA side.
-   */
-  contextId: string;
-  /**
-   * One or more binding targets — web origins, mobile app identifiers, and/or DIDs — that this credential applies to. A request from any matching target uses this entry. A typical entry for a service that exists as both a website and mobile apps will list a web origin, an iOS bundle id, and an Android package id; passkeys for that service typically list only the origin (because iOS Associated Domains and Android Asset Links bind apps to the domain at the OS level).
-   *
-   * @minItems 1
-   */
-  targets: [SiteTarget, ...SiteTarget[]];
-  /**
-   * Human-readable display name (e.g. "Work GitHub", "Personal bank — checking"). Maintainers MAY enforce a maximum length; the wire spec does not.
-   */
-  label: string;
-  secretKind: SecretKind1;
-  /**
-   * User-defined tags for organisation and filtering (e.g. ["family", "finance"]). Maintainers MAY enforce a maximum count; the wire spec does not.
-   */
-  tags?: string[];
-  /**
-   * Non-sensitive notes the user attached to the entry. Visible in metadata view (suitable for support contact, account number, expiry policy memos). SENSITIVE notes belong in the secret payload as a `secureNotes` field — those are only released by vault/release/0.1.
-   */
-  notes?: string;
-  /**
-   * Optional URI of an icon to display in the consumer UI. Maintainers MAY fetch and cache; consumers SHOULD treat as untrusted content and fetch via a sandboxed pipeline.
-   */
-  favicon?: string;
-  /**
-   * Opaque maintainer-defined selector strings fed to the policy engine when this entry is requested (e.g. "recent_uv_required", "network_class=corp", "step_up_push"). Consumers MUST treat selectors as opaque; they exist for policy authoring on the maintainer side.
-   */
-  selectors?: string[];
-  /**
-   * Names of additional fields the user has attached (e.g. ["security-question-1", "account-number"]). The VALUES live in the secret payload and are only delivered by vault/release/0.1. Exposing names in metadata lets the consumer render the right form layout before requesting release.
-   */
-  customFieldNames?: string[];
-  /**
-   * References to encrypted blobs associated with the entry (recovery codes, PEM files, screenshots of authenticator setup). The blobs themselves are fetched via a separate mechanism the maintainer documents; metadata view exposes only the descriptor.
-   */
-  attachments?: AttachmentRef[];
-  /**
-   * Optional time after which the credential is no longer expected to be valid (e.g. an OAuth refresh token's known expiry, a time-limited API token, an enterprise password rotation policy). Maintainers MAY surface this in the consumer UI as a warning.
-   */
-  expiresAt?: string;
-  /**
-   * Set by the maintainer (via HIBP integration or equivalent) when the password material associated with this entry is known to appear in a public breach. Consumers SHOULD surface this prominently. Cleared when the user rotates the password and the new password is not in any known breach.
-   */
-  breachedAt?: string;
-  /**
-   * Set whenever the password component of the secret payload is rotated. Maintainers MUST update this on every secret-material change for entries of kind `password` (or any kind that carries a password component). Used by consumers to surface rotation-overdue warnings.
-   */
-  passwordChangedAt?: string;
-  createdAt: string;
-  /**
-   * VID of the consumer that originally created the entry.
-   */
-  createdBy?: string;
-  updatedAt: string;
-  /**
-   * VID of the consumer that last modified the entry.
-   */
-  updatedBy?: string;
-  /**
-   * Most recent time the entry was used (either released or proxy-login performed). Maintainers MAY return this with reduced precision (e.g. hour-floored) when releasing to a less-trusted consumer.
-   */
-  lastUsedAt?: string;
-  /**
-   * Monotonic version counter incremented on every mutation. Used by consumers for optimistic-concurrency checks on vault/upsert and as the seq baseline for vault/sync.
-   */
-  version: number;
-  /**
-   * Optional cached DID the entry will act AS for DID-shaped flows — mirrors the `did` field of the entry's secret payload when `secretKind` carries one (`didSelfIssued`, `didcommPeer`). Absent for kinds that have no DID concept (`password`, `passkey`, `oauthTokens`, `bearerToken`, `sshKey`, `custom`). MAINTAINER-DERIVED, NOT CONSUMER-SUPPLIED: the maintainer MUST recompute this from the canonical secret at every upsert / secret rotation; a producer-supplied value on `vault/upsert/0.1` MUST be ignored (no error, but no honour). Read-only on the wire, present in metadata views so consumers can drive RP-side flows (e.g. fetch `/auth/challenge` keyed on the principal DID before requesting a proxy-login) without releasing the secret.
-   */
-  principalDid?: string;
-  ext?: Ext1;
-}
-export interface AttachmentRef {
-  /**
-   * Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.
-   */
-  id: string;
-  /**
-   * User-supplied filename (e.g. "recovery-codes.txt").
-   */
-  name: string;
-  /**
-   * Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.
-   */
-  sizeBytes: number;
-  /**
-   * Hex-encoded SHA-256 of the encrypted blob bytes (post-encryption). Lets the consumer verify integrity after fetch.
-   */
-  sha256: string;
-  /**
-   * Optional MIME type hint for the consumer UI (e.g. "text/plain", "application/x-pem-file").
-   */
-  contentType?: string;
-}
-/**
- * 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.
- */
-export interface Ext1 {
-  [k: string]: unknown | undefined;
-}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { AndroidApp, AttachmentRef, Did, DidcommAuthcryptEnvelope, Ext, HpkeArmoredEnvelope, IosApp, SealedEnvelope, SecretKind, SiteTarget, TspMessageEnvelope, VaultEntry, WebOrigin };
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vault/upsert/0.2" as const;
@@ -349,7 +115,8 @@ export const PAYLOAD_SCHEMA = {
     },
     "label": {
       "type": "string",
-      "minLength": 1
+      "minLength": 1,
+      "maxLength": 256
     },
     "secretKind": {
       "$ref": "#/$defs/SecretKind"
@@ -484,7 +251,8 @@ export const PAYLOAD_SCHEMA = {
         "label": {
           "type": "string",
           "minLength": 1,
-          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Maintainers MAY enforce a maximum length; the wire spec does not."
+          "maxLength": 256,
+          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Bounded on the wire at 256 characters; a maintainer MAY enforce a shorter limit."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -908,7 +676,8 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "label": {
           "type": "string",
           "minLength": 1,
-          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Maintainers MAY enforce a maximum length; the wire spec does not."
+          "maxLength": 256,
+          "description": "Human-readable display name (e.g. \"Work GitHub\", \"Personal bank — checking\"). Bounded on the wire at 256 characters; a maintainer MAY enforce a shorter limit."
         },
         "secretKind": {
           "$ref": "#/$defs/SecretKind",
@@ -1271,6 +1040,7 @@ export const SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: PAYLOAD_SCHEMA,
 } as const;
 
@@ -1284,5 +1054,6 @@ export const RESPONSE_SPEC = {
   isBearer: false,
   isProofRequired: true,
   isRecipientRequired: true,
+  isIssuedAtRequired: true,
   payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
 } as const;