@openvtc/trust-tasks 0.27.3 → 0.27.5

package/dist/vault/list/0.4/payload.d.ts

@@ -0,0 +1,1537 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vault/list/0.4/payload.schema.json
+ */
+import type { AndroidApp_VaultV0_2 as AndroidApp, AttachmentRef_VaultV0_3 as AttachmentRef, Did_VaultV0_2 as Did, DigestMultibase, Ext, IosApp_VaultV0_2 as IosApp, SecretKind_VaultV0_2 as SecretKind, SiteTarget_VaultV0_2 as SiteTarget, VaultEntry_VaultV0_3 as VaultEntry, WebOrigin_VaultV0_2 as WebOrigin } from "../../../_shared/components.js";
+/**
+ * Query a vault maintainer for the metadata view of stored entries. All filters are AND-combined. Pagination is opaque-cursor based; the maintainer chooses page size within the caller's bound and its own ceiling. Secret material is NEVER returned by this task — even when the requesting consumer has VaultRead capability for the entry, the secret is only released via vault/release/0.1.
+ */
+export interface VaultListPayload {
+    /**
+     * Optional filter — only entries belonging to this trust context (persona) are returned. Omit to query across all contexts the requesting consumer has VaultRead on.
+     */
+    contextId?: string;
+    /**
+     * Optional filter — only entries with at least one `targets[]` entry of kind `webOrigin` whose origin starts with this prefix. Useful for "all my github.* logins". Maintainers MUST canonicalise (lowercase host) before comparison.
+     */
+    targetOriginPrefix?: string;
+    /**
+     * Optional filter — only entries with at least one `targets[]` entry of kind `did` exactly equal to this value.
+     */
+    targetDid?: string;
+    /**
+     * Optional filter — only entries with at least one `targets[]` entry of kind `iosApp` whose `bundleId` exactly equals this value. The typical iOS Companion lookup.
+     */
+    targetIosBundleId?: string;
+    /**
+     * Optional filter — only entries with at least one `targets[]` entry of kind `androidApp` whose `packageName` exactly equals this value. The typical Android Companion lookup.
+     */
+    targetAndroidPackage?: string;
+    /**
+     * Optional filter — only entries of this secret kind are returned.
+     */
+    secretKind?: SecretKind;
+    /**
+     * Optional filter — only entries whose `tags` array contains this tag.
+     */
+    tag?: string;
+    /**
+     * Optional filter — only entries whose `lastUsedAt` is greater than or equal to this timestamp are returned. Entries that have never been used are excluded when this filter is present.
+     */
+    usedSince?: string;
+    /**
+     * Optional filter — when true, only entries with no `lastUsedAt` are returned. Mutually exclusive with `usedSince`; maintainers MUST reject documents that supply both.
+     */
+    neverUsed?: boolean;
+    /**
+     * Optional filter — only entries whose `expiresAt` is less than this timestamp are returned. Useful for "what's about to expire" panels.
+     */
+    expiresBefore?: string;
+    /**
+     * Optional filter — when true, only entries with `breachedAt` set are returned; when false, only entries with `breachedAt` absent are returned.
+     */
+    breached?: boolean;
+    /**
+     * An opaque continuation token from a previous response's `nextCursor`; a responder MUST NOT accept a cursor it did not issue. Consumers MUST treat the cursor as opaque and re-send it verbatim.
+     */
+    cursor?: string;
+    /**
+     * The most entries to return; the responder chooses a default and MAY return fewer. The maintainer MAY impose a lower ceiling.
+     */
+    limit?: number;
+    /**
+     * Ecosystem-defined extension members per SPEC.md §4.5.1.
+     */
+    ext?: Ext;
+    /**
+     * Archival-lifecycle view selector. Omitted or `active` lists only live entries; `archived` and `deleted` list those respectively (a `deleted` entry is a tombstone still inside its grace window); `all` lists every entry regardless of lifecycle state.
+     */
+    status?: "active" | "archived" | "deleted" | "all";
+}
+/**
+ * The success response to a vault/list request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/vault/list/0.4#response.
+ */
+export interface VaultListResponsePayload {
+    /**
+     * Matching VaultEntry items in metadata-only view, in maintainer-defined order (RECOMMENDED: most-recently-used first when no other order is implied by the filters). May be empty.
+     */
+    entries: VaultEntry[];
+    /**
+     * Opaque continuation token to fetch the next page, sent back as the request's `cursor`. Present when more matching entries exist beyond `entries`; absent on the last page, which is how a consumer knows the result is complete.
+     */
+    nextCursor?: string;
+    /**
+     * Names of VaultEntry fields the maintainer redacted from every returned entry (for example, ['lastUsedAt'] when releasing to a consumer whose policy does not permit timing-data exposure).
+     */
+    redactedFields?: string[];
+    /**
+     * 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 { AndroidApp, AttachmentRef, Did, DigestMultibase, Ext, IosApp, SecretKind, SiteTarget, VaultEntry, WebOrigin };
+/** Trust Task type URI. */
+export declare const TYPE_URI: "https://trusttasks.org/spec/vault/list/0.4";
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VaultListPayload;
+/** Trust Task response type URI (request type URI + "#response"). */
+export declare const RESPONSE_TYPE_URI: "https://trusttasks.org/spec/vault/list/0.4#response";
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VaultListResponsePayload;
+/**
+ * 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 declare const PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $id: "https://trusttasks.org/spec/vault/list/0.4";
+    readonly title: "Vault List — payload";
+    readonly description: "Query a vault maintainer for the metadata view of stored entries. All filters are AND-combined. Pagination is opaque-cursor based; the maintainer chooses page size within the caller's bound and its own ceiling. Secret material is NEVER returned by this task — even when the requesting consumer has VaultRead capability for the entry, the secret is only released via vault/release/0.1.";
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly properties: {
+        readonly contextId: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "Optional filter — only entries belonging to this trust context (persona) are returned. Omit to query across all contexts the requesting consumer has VaultRead on.";
+        };
+        readonly targetOriginPrefix: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly format: "uri";
+            readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `webOrigin` whose origin starts with this prefix. Useful for \"all my github.* logins\". Maintainers MUST canonicalise (lowercase host) before comparison.";
+        };
+        readonly targetDid: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `did` exactly equal to this value.";
+        };
+        readonly targetIosBundleId: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly pattern: "^[A-Za-z0-9.-]+$";
+            readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `iosApp` whose `bundleId` exactly equals this value. The typical iOS Companion lookup.";
+        };
+        readonly targetAndroidPackage: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+            readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `androidApp` whose `packageName` exactly equals this value. The typical Android Companion lookup.";
+        };
+        readonly secretKind: {
+            readonly $ref: "#/$defs/SecretKind";
+            readonly description: "Optional filter — only entries of this secret kind are returned.";
+        };
+        readonly tag: {
+            readonly type: "string";
+            readonly minLength: 1;
+            readonly maxLength: 64;
+            readonly description: "Optional filter — only entries whose `tags` array contains this tag.";
+        };
+        readonly usedSince: {
+            readonly type: "string";
+            readonly format: "date-time";
+            readonly description: "Optional filter — only entries whose `lastUsedAt` is greater than or equal to this timestamp are returned. Entries that have never been used are excluded when this filter is present.";
+        };
+        readonly neverUsed: {
+            readonly type: "boolean";
+            readonly description: "Optional filter — when true, only entries with no `lastUsedAt` are returned. Mutually exclusive with `usedSince`; maintainers MUST reject documents that supply both.";
+        };
+        readonly expiresBefore: {
+            readonly type: "string";
+            readonly format: "date-time";
+            readonly description: "Optional filter — only entries whose `expiresAt` is less than this timestamp are returned. Useful for \"what's about to expire\" panels.";
+        };
+        readonly breached: {
+            readonly type: "boolean";
+            readonly description: "Optional filter — when true, only entries with `breachedAt` set are returned; when false, only entries with `breachedAt` absent are returned.";
+        };
+        readonly cursor: {
+            readonly type: "string";
+            readonly description: "An opaque continuation token from a previous response's `nextCursor`; a responder MUST NOT accept a cursor it did not issue. Consumers MUST treat the cursor as opaque and re-send it verbatim.";
+        };
+        readonly limit: {
+            readonly type: "integer";
+            readonly minimum: 1;
+            readonly maximum: 1000;
+            readonly description: "The most entries to return; the responder chooses a default and MAY return fewer. The maintainer MAY impose a lower ceiling.";
+        };
+        readonly ext: {
+            readonly $ref: "#/$defs/Ext";
+            readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+        };
+        readonly status: {
+            readonly type: "string";
+            readonly enum: readonly ["active", "archived", "deleted", "all"];
+            readonly default: "active";
+            readonly description: "Archival-lifecycle view selector. Omitted or `active` lists only live entries; `archived` and `deleted` list those respectively (a `deleted` entry is a tombstone still inside its grace window); `all` lists every entry regardless of lifecycle state.";
+        };
+    };
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Vault List — response payload";
+            readonly description: "The success response to a vault/list request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/vault/list/0.4#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["entries"];
+            readonly properties: {
+                readonly entries: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/VaultEntry";
+                    };
+                    readonly description: "Matching VaultEntry items in metadata-only view, in maintainer-defined order (RECOMMENDED: most-recently-used first when no other order is implied by the filters). May be empty.";
+                };
+                readonly nextCursor: {
+                    readonly type: "string";
+                    readonly description: "Opaque continuation token to fetch the next page, sent back as the request's `cursor`. Present when more matching entries exist beyond `entries`; absent on the last page, which is how a consumer knows the result is complete.";
+                };
+                readonly redactedFields: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                    };
+                    readonly description: "Names of VaultEntry fields the maintainer redacted from every returned entry (for example, ['lastUsedAt'] when releasing to a consumer whose policy does not permit timing-data exposure).";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly 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.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly VaultEntry: {
+            readonly title: "VaultEntry";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["id", "contextId", "targets", "label", "secretKind", "createdAt", "updatedAt", "version"];
+            readonly properties: {
+                readonly id: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.";
+                };
+                readonly contextId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "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.";
+                };
+                readonly targets: {
+                    readonly type: "array";
+                    readonly minItems: 1;
+                    readonly items: {
+                        readonly $ref: "#/$defs/SiteTarget";
+                    };
+                    readonly description: "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).";
+                };
+                readonly label: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly 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.";
+                };
+                readonly secretKind: {
+                    readonly $ref: "#/$defs/SecretKind";
+                    readonly description: "Discriminator for the kind of secret this entry holds. The secret material itself is NEVER returned in metadata views; the kind is exposed so consumers can render an appropriate UI affordance and so policy decisions can route by kind.";
+                };
+                readonly tags: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "User-defined tags for organisation and filtering (e.g. [\"family\", \"finance\"]). Maintainers MAY enforce a maximum count; the wire spec does not.";
+                };
+                readonly notes: {
+                    readonly type: "string";
+                    readonly maxLength: 4096;
+                    readonly description: "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.";
+                };
+                readonly favicon: {
+                    readonly type: "string";
+                    readonly format: "uri";
+                    readonly description: "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.";
+                };
+                readonly selectors: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "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.";
+                };
+                readonly customFieldNames: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 128;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "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.";
+                };
+                readonly attachments: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/AttachmentRef";
+                    };
+                    readonly description: "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.";
+                };
+                readonly expiresAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly breachedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly passwordChangedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly createdBy: {
+                    readonly type: "string";
+                    readonly description: "VID of the consumer that originally created the entry.";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly updatedBy: {
+                    readonly type: "string";
+                    readonly description: "VID of the consumer that last modified the entry.";
+                };
+                readonly lastUsedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly version: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "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.";
+                };
+                readonly principalDid: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "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.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1. Reverse-DNS-namespaced; consumers MUST ignore unrecognized namespaces.";
+                };
+            };
+        };
+        readonly AttachmentRef: {
+            readonly title: "AttachmentRef";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["id", "name", "sizeBytes", "digestMultibase"];
+            readonly properties: {
+                readonly id: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.";
+                };
+                readonly name: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly description: "User-supplied filename (e.g. \"recovery-codes.txt\").";
+                };
+                readonly sizeBytes: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.";
+                };
+                readonly digestMultibase: {
+                    readonly $ref: "#/$defs/DigestMultibase";
+                    readonly description: "Digest over the encrypted blob bytes (post-encryption), so the consumer can verify integrity after fetch. Taken over the bytes as stored, not over a canonicalization: the blob is an opaque artifact, not a JSON document.";
+                };
+                readonly contentType: {
+                    readonly type: "string";
+                    readonly description: "Optional MIME type hint for the consumer UI (e.g. \"text/plain\", \"application/x-pem-file\").";
+                };
+            };
+        };
+        readonly DigestMultibase: {
+            readonly title: "DigestMultibase";
+            readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+            readonly type: "string";
+            readonly minLength: 16;
+            readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+            readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+        };
+        readonly SecretKind: {
+            readonly title: "SecretKind";
+            readonly type: "string";
+            readonly enum: readonly ["password", "passkey", "oauthTokens", "didSelfIssued", "didcommPeer", "bearerToken", "sshKey", "custom"];
+            readonly description: "Discriminator for the secret type stored in the entry. Definitions:\n- `password` — username + password (+ optional TOTP seed).\n- `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).\n- `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.\n- `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.\n- `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.\n- `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).\n- `sshKey` — SSH private key + comment.\n- `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.";
+        };
+        readonly SiteTarget: {
+            readonly title: "SiteTarget";
+            readonly description: "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.";
+            readonly oneOf: readonly [{
+                readonly title: "WebOrigin";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "origin"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "webOrigin";
+                    };
+                    readonly origin: {
+                        readonly type: "string";
+                        readonly format: "uri";
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "Did";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "did"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "did";
+                    };
+                    readonly did: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "IosApp";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "bundleId"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "iosApp";
+                    };
+                    readonly bundleId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Za-z0-9.-]+$";
+                        readonly description: "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).";
+                    };
+                    readonly teamId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Z0-9]+$";
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "AndroidApp";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "packageName", "sha256CertFingerprints"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "androidApp";
+                    };
+                    readonly packageName: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+                        readonly description: "Android package name in reverse-DNS form (e.g. \"com.github.android\").";
+                    };
+                    readonly sha256CertFingerprints: {
+                        readonly type: "array";
+                        readonly minItems: 1;
+                        readonly items: {
+                            readonly type: "string";
+                            readonly pattern: "^[0-9A-F]{2}(:[0-9A-F]{2}){31}$";
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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).";
+                    };
+                };
+            }];
+        };
+    };
+};
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export declare const RESPONSE_PAYLOAD_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly $ref: "#/$defs/Response";
+    readonly $defs: {
+        readonly Response: {
+            readonly $anchor: "response";
+            readonly title: "Vault List — response payload";
+            readonly description: "The success response to a vault/list request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/vault/list/0.4#response.";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["entries"];
+            readonly properties: {
+                readonly entries: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/VaultEntry";
+                    };
+                    readonly description: "Matching VaultEntry items in metadata-only view, in maintainer-defined order (RECOMMENDED: most-recently-used first when no other order is implied by the filters). May be empty.";
+                };
+                readonly nextCursor: {
+                    readonly type: "string";
+                    readonly description: "Opaque continuation token to fetch the next page, sent back as the request's `cursor`. Present when more matching entries exist beyond `entries`; absent on the last page, which is how a consumer knows the result is complete.";
+                };
+                readonly redactedFields: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                    };
+                    readonly description: "Names of VaultEntry fields the maintainer redacted from every returned entry (for example, ['lastUsedAt'] when releasing to a consumer whose policy does not permit timing-data exposure).";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                };
+            };
+        };
+        readonly Ext: {
+            readonly title: "Ext";
+            readonly 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.";
+            readonly type: "object";
+            readonly minProperties: 1;
+            readonly additionalProperties: true;
+            readonly propertyNames: {
+                readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+            };
+        };
+        readonly VaultEntry: {
+            readonly title: "VaultEntry";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["id", "contextId", "targets", "label", "secretKind", "createdAt", "updatedAt", "version"];
+            readonly properties: {
+                readonly id: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.";
+                };
+                readonly contextId: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "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.";
+                };
+                readonly targets: {
+                    readonly type: "array";
+                    readonly minItems: 1;
+                    readonly items: {
+                        readonly $ref: "#/$defs/SiteTarget";
+                    };
+                    readonly description: "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).";
+                };
+                readonly label: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly 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.";
+                };
+                readonly secretKind: {
+                    readonly $ref: "#/$defs/SecretKind";
+                    readonly description: "Discriminator for the kind of secret this entry holds. The secret material itself is NEVER returned in metadata views; the kind is exposed so consumers can render an appropriate UI affordance and so policy decisions can route by kind.";
+                };
+                readonly tags: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 64;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "User-defined tags for organisation and filtering (e.g. [\"family\", \"finance\"]). Maintainers MAY enforce a maximum count; the wire spec does not.";
+                };
+                readonly notes: {
+                    readonly type: "string";
+                    readonly maxLength: 4096;
+                    readonly description: "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.";
+                };
+                readonly favicon: {
+                    readonly type: "string";
+                    readonly format: "uri";
+                    readonly description: "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.";
+                };
+                readonly selectors: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "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.";
+                };
+                readonly customFieldNames: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 128;
+                    };
+                    readonly uniqueItems: true;
+                    readonly description: "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.";
+                };
+                readonly attachments: {
+                    readonly type: "array";
+                    readonly items: {
+                        readonly $ref: "#/$defs/AttachmentRef";
+                    };
+                    readonly description: "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.";
+                };
+                readonly expiresAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly breachedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly passwordChangedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly createdAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly createdBy: {
+                    readonly type: "string";
+                    readonly description: "VID of the consumer that originally created the entry.";
+                };
+                readonly updatedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                };
+                readonly updatedBy: {
+                    readonly type: "string";
+                    readonly description: "VID of the consumer that last modified the entry.";
+                };
+                readonly lastUsedAt: {
+                    readonly type: "string";
+                    readonly format: "date-time";
+                    readonly description: "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.";
+                };
+                readonly version: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "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.";
+                };
+                readonly principalDid: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "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.";
+                };
+                readonly ext: {
+                    readonly $ref: "#/$defs/Ext";
+                    readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1. Reverse-DNS-namespaced; consumers MUST ignore unrecognized namespaces.";
+                };
+            };
+        };
+        readonly AttachmentRef: {
+            readonly title: "AttachmentRef";
+            readonly type: "object";
+            readonly additionalProperties: false;
+            readonly required: readonly ["id", "name", "sizeBytes", "digestMultibase"];
+            readonly properties: {
+                readonly id: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly description: "Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.";
+                };
+                readonly name: {
+                    readonly type: "string";
+                    readonly minLength: 1;
+                    readonly maxLength: 256;
+                    readonly description: "User-supplied filename (e.g. \"recovery-codes.txt\").";
+                };
+                readonly sizeBytes: {
+                    readonly type: "integer";
+                    readonly minimum: 0;
+                    readonly description: "Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.";
+                };
+                readonly digestMultibase: {
+                    readonly $ref: "#/$defs/DigestMultibase";
+                    readonly description: "Digest over the encrypted blob bytes (post-encryption), so the consumer can verify integrity after fetch. Taken over the bytes as stored, not over a canonicalization: the blob is an opaque artifact, not a JSON document.";
+                };
+                readonly contentType: {
+                    readonly type: "string";
+                    readonly description: "Optional MIME type hint for the consumer UI (e.g. \"text/plain\", \"application/x-pem-file\").";
+                };
+            };
+        };
+        readonly DigestMultibase: {
+            readonly title: "DigestMultibase";
+            readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+            readonly type: "string";
+            readonly minLength: 16;
+            readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+            readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+        };
+        readonly SecretKind: {
+            readonly title: "SecretKind";
+            readonly type: "string";
+            readonly enum: readonly ["password", "passkey", "oauthTokens", "didSelfIssued", "didcommPeer", "bearerToken", "sshKey", "custom"];
+            readonly description: "Discriminator for the secret type stored in the entry. Definitions:\n- `password` — username + password (+ optional TOTP seed).\n- `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).\n- `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.\n- `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.\n- `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.\n- `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).\n- `sshKey` — SSH private key + comment.\n- `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.";
+        };
+        readonly SiteTarget: {
+            readonly title: "SiteTarget";
+            readonly description: "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.";
+            readonly oneOf: readonly [{
+                readonly title: "WebOrigin";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "origin"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "webOrigin";
+                    };
+                    readonly origin: {
+                        readonly type: "string";
+                        readonly format: "uri";
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "Did";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "did"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "did";
+                    };
+                    readonly did: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "IosApp";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "bundleId"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "iosApp";
+                    };
+                    readonly bundleId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Za-z0-9.-]+$";
+                        readonly description: "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).";
+                    };
+                    readonly teamId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Z0-9]+$";
+                        readonly description: "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.";
+                    };
+                };
+            }, {
+                readonly title: "AndroidApp";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["kind", "packageName", "sha256CertFingerprints"];
+                readonly properties: {
+                    readonly kind: {
+                        readonly const: "androidApp";
+                    };
+                    readonly packageName: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+                        readonly description: "Android package name in reverse-DNS form (e.g. \"com.github.android\").";
+                    };
+                    readonly sha256CertFingerprints: {
+                        readonly type: "array";
+                        readonly minItems: 1;
+                        readonly items: {
+                            readonly type: "string";
+                            readonly pattern: "^[0-9A-F]{2}(:[0-9A-F]{2}){31}$";
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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).";
+                    };
+                };
+            }];
+        };
+    };
+};
+/**
+ * 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 declare const SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vault/list/0.4";
+    readonly isBearer: false;
+    readonly isProofRequired: false;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: false;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $id: "https://trusttasks.org/spec/vault/list/0.4";
+        readonly title: "Vault List — payload";
+        readonly description: "Query a vault maintainer for the metadata view of stored entries. All filters are AND-combined. Pagination is opaque-cursor based; the maintainer chooses page size within the caller's bound and its own ceiling. Secret material is NEVER returned by this task — even when the requesting consumer has VaultRead capability for the entry, the secret is only released via vault/release/0.1.";
+        readonly type: "object";
+        readonly additionalProperties: false;
+        readonly properties: {
+            readonly contextId: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "Optional filter — only entries belonging to this trust context (persona) are returned. Omit to query across all contexts the requesting consumer has VaultRead on.";
+            };
+            readonly targetOriginPrefix: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly format: "uri";
+                readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `webOrigin` whose origin starts with this prefix. Useful for \"all my github.* logins\". Maintainers MUST canonicalise (lowercase host) before comparison.";
+            };
+            readonly targetDid: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `did` exactly equal to this value.";
+            };
+            readonly targetIosBundleId: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly pattern: "^[A-Za-z0-9.-]+$";
+                readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `iosApp` whose `bundleId` exactly equals this value. The typical iOS Companion lookup.";
+            };
+            readonly targetAndroidPackage: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+                readonly description: "Optional filter — only entries with at least one `targets[]` entry of kind `androidApp` whose `packageName` exactly equals this value. The typical Android Companion lookup.";
+            };
+            readonly secretKind: {
+                readonly $ref: "#/$defs/SecretKind";
+                readonly description: "Optional filter — only entries of this secret kind are returned.";
+            };
+            readonly tag: {
+                readonly type: "string";
+                readonly minLength: 1;
+                readonly maxLength: 64;
+                readonly description: "Optional filter — only entries whose `tags` array contains this tag.";
+            };
+            readonly usedSince: {
+                readonly type: "string";
+                readonly format: "date-time";
+                readonly description: "Optional filter — only entries whose `lastUsedAt` is greater than or equal to this timestamp are returned. Entries that have never been used are excluded when this filter is present.";
+            };
+            readonly neverUsed: {
+                readonly type: "boolean";
+                readonly description: "Optional filter — when true, only entries with no `lastUsedAt` are returned. Mutually exclusive with `usedSince`; maintainers MUST reject documents that supply both.";
+            };
+            readonly expiresBefore: {
+                readonly type: "string";
+                readonly format: "date-time";
+                readonly description: "Optional filter — only entries whose `expiresAt` is less than this timestamp are returned. Useful for \"what's about to expire\" panels.";
+            };
+            readonly breached: {
+                readonly type: "boolean";
+                readonly description: "Optional filter — when true, only entries with `breachedAt` set are returned; when false, only entries with `breachedAt` absent are returned.";
+            };
+            readonly cursor: {
+                readonly type: "string";
+                readonly description: "An opaque continuation token from a previous response's `nextCursor`; a responder MUST NOT accept a cursor it did not issue. Consumers MUST treat the cursor as opaque and re-send it verbatim.";
+            };
+            readonly limit: {
+                readonly type: "integer";
+                readonly minimum: 1;
+                readonly maximum: 1000;
+                readonly description: "The most entries to return; the responder chooses a default and MAY return fewer. The maintainer MAY impose a lower ceiling.";
+            };
+            readonly ext: {
+                readonly $ref: "#/$defs/Ext";
+                readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+            };
+            readonly status: {
+                readonly type: "string";
+                readonly enum: readonly ["active", "archived", "deleted", "all"];
+                readonly default: "active";
+                readonly description: "Archival-lifecycle view selector. Omitted or `active` lists only live entries; `archived` and `deleted` list those respectively (a `deleted` entry is a tombstone still inside its grace window); `all` lists every entry regardless of lifecycle state.";
+            };
+        };
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "Vault List — response payload";
+                readonly description: "The success response to a vault/list request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/vault/list/0.4#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["entries"];
+                readonly properties: {
+                    readonly entries: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/VaultEntry";
+                        };
+                        readonly description: "Matching VaultEntry items in metadata-only view, in maintainer-defined order (RECOMMENDED: most-recently-used first when no other order is implied by the filters). May be empty.";
+                    };
+                    readonly nextCursor: {
+                        readonly type: "string";
+                        readonly description: "Opaque continuation token to fetch the next page, sent back as the request's `cursor`. Present when more matching entries exist beyond `entries`; absent on the last page, which is how a consumer knows the result is complete.";
+                    };
+                    readonly redactedFields: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                        };
+                        readonly description: "Names of VaultEntry fields the maintainer redacted from every returned entry (for example, ['lastUsedAt'] when releasing to a consumer whose policy does not permit timing-data exposure).";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly 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.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly VaultEntry: {
+                readonly title: "VaultEntry";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["id", "contextId", "targets", "label", "secretKind", "createdAt", "updatedAt", "version"];
+                readonly properties: {
+                    readonly id: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.";
+                    };
+                    readonly contextId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                    readonly targets: {
+                        readonly type: "array";
+                        readonly minItems: 1;
+                        readonly items: {
+                            readonly $ref: "#/$defs/SiteTarget";
+                        };
+                        readonly description: "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).";
+                    };
+                    readonly label: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly 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.";
+                    };
+                    readonly secretKind: {
+                        readonly $ref: "#/$defs/SecretKind";
+                        readonly description: "Discriminator for the kind of secret this entry holds. The secret material itself is NEVER returned in metadata views; the kind is exposed so consumers can render an appropriate UI affordance and so policy decisions can route by kind.";
+                    };
+                    readonly tags: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "User-defined tags for organisation and filtering (e.g. [\"family\", \"finance\"]). Maintainers MAY enforce a maximum count; the wire spec does not.";
+                    };
+                    readonly notes: {
+                        readonly type: "string";
+                        readonly maxLength: 4096;
+                        readonly description: "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.";
+                    };
+                    readonly favicon: {
+                        readonly type: "string";
+                        readonly format: "uri";
+                        readonly description: "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.";
+                    };
+                    readonly selectors: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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.";
+                    };
+                    readonly customFieldNames: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 128;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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.";
+                    };
+                    readonly attachments: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/AttachmentRef";
+                        };
+                        readonly description: "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.";
+                    };
+                    readonly expiresAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly breachedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly passwordChangedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly createdBy: {
+                        readonly type: "string";
+                        readonly description: "VID of the consumer that originally created the entry.";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly updatedBy: {
+                        readonly type: "string";
+                        readonly description: "VID of the consumer that last modified the entry.";
+                    };
+                    readonly lastUsedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly version: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "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.";
+                    };
+                    readonly principalDid: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1. Reverse-DNS-namespaced; consumers MUST ignore unrecognized namespaces.";
+                    };
+                };
+            };
+            readonly AttachmentRef: {
+                readonly title: "AttachmentRef";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["id", "name", "sizeBytes", "digestMultibase"];
+                readonly properties: {
+                    readonly id: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.";
+                    };
+                    readonly name: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly description: "User-supplied filename (e.g. \"recovery-codes.txt\").";
+                    };
+                    readonly sizeBytes: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.";
+                    };
+                    readonly digestMultibase: {
+                        readonly $ref: "#/$defs/DigestMultibase";
+                        readonly description: "Digest over the encrypted blob bytes (post-encryption), so the consumer can verify integrity after fetch. Taken over the bytes as stored, not over a canonicalization: the blob is an opaque artifact, not a JSON document.";
+                    };
+                    readonly contentType: {
+                        readonly type: "string";
+                        readonly description: "Optional MIME type hint for the consumer UI (e.g. \"text/plain\", \"application/x-pem-file\").";
+                    };
+                };
+            };
+            readonly DigestMultibase: {
+                readonly title: "DigestMultibase";
+                readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+                readonly type: "string";
+                readonly minLength: 16;
+                readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+                readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+            };
+            readonly SecretKind: {
+                readonly title: "SecretKind";
+                readonly type: "string";
+                readonly enum: readonly ["password", "passkey", "oauthTokens", "didSelfIssued", "didcommPeer", "bearerToken", "sshKey", "custom"];
+                readonly description: "Discriminator for the secret type stored in the entry. Definitions:\n- `password` — username + password (+ optional TOTP seed).\n- `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).\n- `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.\n- `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.\n- `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.\n- `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).\n- `sshKey` — SSH private key + comment.\n- `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.";
+            };
+            readonly SiteTarget: {
+                readonly title: "SiteTarget";
+                readonly description: "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.";
+                readonly oneOf: readonly [{
+                    readonly title: "WebOrigin";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "origin"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "webOrigin";
+                        };
+                        readonly origin: {
+                            readonly type: "string";
+                            readonly format: "uri";
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "Did";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "did"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "did";
+                        };
+                        readonly did: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "IosApp";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "bundleId"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "iosApp";
+                        };
+                        readonly bundleId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Za-z0-9.-]+$";
+                            readonly description: "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).";
+                        };
+                        readonly teamId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Z0-9]+$";
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "AndroidApp";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "packageName", "sha256CertFingerprints"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "androidApp";
+                        };
+                        readonly packageName: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+                            readonly description: "Android package name in reverse-DNS form (e.g. \"com.github.android\").";
+                        };
+                        readonly sha256CertFingerprints: {
+                            readonly type: "array";
+                            readonly minItems: 1;
+                            readonly items: {
+                                readonly type: "string";
+                                readonly pattern: "^[0-9A-F]{2}(:[0-9A-F]{2}){31}$";
+                            };
+                            readonly uniqueItems: true;
+                            readonly description: "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).";
+                        };
+                    };
+                }];
+            };
+        };
+    };
+};
+/**
+ * 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 declare const RESPONSE_SPEC: {
+    readonly typeUri: "https://trusttasks.org/spec/vault/list/0.4#response";
+    readonly isBearer: false;
+    readonly isProofRequired: false;
+    readonly isRecipientRequired: true;
+    readonly isIssuedAtRequired: false;
+    readonly payloadSchema: {
+        readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+        readonly $ref: "#/$defs/Response";
+        readonly $defs: {
+            readonly Response: {
+                readonly $anchor: "response";
+                readonly title: "Vault List — response payload";
+                readonly description: "The success response to a vault/list request. Carried in a Trust Task document whose type is https://trusttasks.org/spec/vault/list/0.4#response.";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["entries"];
+                readonly properties: {
+                    readonly entries: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/VaultEntry";
+                        };
+                        readonly description: "Matching VaultEntry items in metadata-only view, in maintainer-defined order (RECOMMENDED: most-recently-used first when no other order is implied by the filters). May be empty.";
+                    };
+                    readonly nextCursor: {
+                        readonly type: "string";
+                        readonly description: "Opaque continuation token to fetch the next page, sent back as the request's `cursor`. Present when more matching entries exist beyond `entries`; absent on the last page, which is how a consumer knows the result is complete.";
+                    };
+                    readonly redactedFields: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                        };
+                        readonly description: "Names of VaultEntry fields the maintainer redacted from every returned entry (for example, ['lastUsedAt'] when releasing to a consumer whose policy does not permit timing-data exposure).";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1.";
+                    };
+                };
+            };
+            readonly Ext: {
+                readonly title: "Ext";
+                readonly 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.";
+                readonly type: "object";
+                readonly minProperties: 1;
+                readonly additionalProperties: true;
+                readonly propertyNames: {
+                    readonly pattern: "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$";
+                };
+            };
+            readonly VaultEntry: {
+                readonly title: "VaultEntry";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["id", "contextId", "targets", "label", "secretKind", "createdAt", "updatedAt", "version"];
+                readonly properties: {
+                    readonly id: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Opaque vault-maintainer-assigned identifier for the entry. ULID/UUID/base32 are common; the wire spec only requires non-empty string equality.";
+                    };
+                    readonly contextId: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                    readonly targets: {
+                        readonly type: "array";
+                        readonly minItems: 1;
+                        readonly items: {
+                            readonly $ref: "#/$defs/SiteTarget";
+                        };
+                        readonly description: "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).";
+                    };
+                    readonly label: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly 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.";
+                    };
+                    readonly secretKind: {
+                        readonly $ref: "#/$defs/SecretKind";
+                        readonly description: "Discriminator for the kind of secret this entry holds. The secret material itself is NEVER returned in metadata views; the kind is exposed so consumers can render an appropriate UI affordance and so policy decisions can route by kind.";
+                    };
+                    readonly tags: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 64;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "User-defined tags for organisation and filtering (e.g. [\"family\", \"finance\"]). Maintainers MAY enforce a maximum count; the wire spec does not.";
+                    };
+                    readonly notes: {
+                        readonly type: "string";
+                        readonly maxLength: 4096;
+                        readonly description: "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.";
+                    };
+                    readonly favicon: {
+                        readonly type: "string";
+                        readonly format: "uri";
+                        readonly description: "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.";
+                    };
+                    readonly selectors: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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.";
+                    };
+                    readonly customFieldNames: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly maxLength: 128;
+                        };
+                        readonly uniqueItems: true;
+                        readonly description: "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.";
+                    };
+                    readonly attachments: {
+                        readonly type: "array";
+                        readonly items: {
+                            readonly $ref: "#/$defs/AttachmentRef";
+                        };
+                        readonly description: "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.";
+                    };
+                    readonly expiresAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly breachedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly passwordChangedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly createdAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly createdBy: {
+                        readonly type: "string";
+                        readonly description: "VID of the consumer that originally created the entry.";
+                    };
+                    readonly updatedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                    };
+                    readonly updatedBy: {
+                        readonly type: "string";
+                        readonly description: "VID of the consumer that last modified the entry.";
+                    };
+                    readonly lastUsedAt: {
+                        readonly type: "string";
+                        readonly format: "date-time";
+                        readonly description: "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.";
+                    };
+                    readonly version: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "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.";
+                    };
+                    readonly principalDid: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "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.";
+                    };
+                    readonly ext: {
+                        readonly $ref: "#/$defs/Ext";
+                        readonly description: "Ecosystem-defined extension members per SPEC.md §4.5.1. Reverse-DNS-namespaced; consumers MUST ignore unrecognized namespaces.";
+                    };
+                };
+            };
+            readonly AttachmentRef: {
+                readonly title: "AttachmentRef";
+                readonly type: "object";
+                readonly additionalProperties: false;
+                readonly required: readonly ["id", "name", "sizeBytes", "digestMultibase"];
+                readonly properties: {
+                    readonly id: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly description: "Opaque maintainer-assigned id for this attachment; used to fetch the blob via a separate mechanism.";
+                    };
+                    readonly name: {
+                        readonly type: "string";
+                        readonly minLength: 1;
+                        readonly maxLength: 256;
+                        readonly description: "User-supplied filename (e.g. \"recovery-codes.txt\").";
+                    };
+                    readonly sizeBytes: {
+                        readonly type: "integer";
+                        readonly minimum: 0;
+                        readonly description: "Size of the encrypted blob in bytes. Maintainers MAY enforce a maximum per attachment and per entry.";
+                    };
+                    readonly digestMultibase: {
+                        readonly $ref: "#/$defs/DigestMultibase";
+                        readonly description: "Digest over the encrypted blob bytes (post-encryption), so the consumer can verify integrity after fetch. Taken over the bytes as stored, not over a canonicalization: the blob is an opaque artifact, not a JSON document.";
+                    };
+                    readonly contentType: {
+                        readonly type: "string";
+                        readonly description: "Optional MIME type hint for the consumer UI (e.g. \"text/plain\", \"application/x-pem-file\").";
+                    };
+                };
+            };
+            readonly DigestMultibase: {
+                readonly title: "DigestMultibase";
+                readonly description: "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.";
+                readonly type: "string";
+                readonly minLength: 16;
+                readonly pattern: "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$";
+                readonly examples: readonly ["zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"];
+            };
+            readonly SecretKind: {
+                readonly title: "SecretKind";
+                readonly type: "string";
+                readonly enum: readonly ["password", "passkey", "oauthTokens", "didSelfIssued", "didcommPeer", "bearerToken", "sshKey", "custom"];
+                readonly description: "Discriminator for the secret type stored in the entry. Definitions:\n- `password` — username + password (+ optional TOTP seed).\n- `passkey` — WebAuthn discoverable credential (private key + rpId + userHandle).\n- `oauthTokens` — OAuth 2.0 refresh + access token bundle for a specific provider.\n- `didSelfIssued` — Self-Issued OpenID Provider v2 (SIOP) credential: the entry points at a DID + signing key already managed by the VTA.\n- `didcommPeer` — DIDComm peer identity used to authenticate against a DIDComm-speaking relying party.\n- `bearerToken` — opaque bearer token carried in a maintainer-named header (covers API tokens, long-lived JWTs, personal-access tokens).\n- `sshKey` — SSH private key + comment.\n- `custom` — arbitrary structured fields; release-time consumer responsible for interpretation.";
+            };
+            readonly SiteTarget: {
+                readonly title: "SiteTarget";
+                readonly description: "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.";
+                readonly oneOf: readonly [{
+                    readonly title: "WebOrigin";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "origin"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "webOrigin";
+                        };
+                        readonly origin: {
+                            readonly type: "string";
+                            readonly format: "uri";
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "Did";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "did"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "did";
+                        };
+                        readonly did: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "IosApp";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "bundleId"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "iosApp";
+                        };
+                        readonly bundleId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Za-z0-9.-]+$";
+                            readonly description: "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).";
+                        };
+                        readonly teamId: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Z0-9]+$";
+                            readonly description: "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.";
+                        };
+                    };
+                }, {
+                    readonly title: "AndroidApp";
+                    readonly type: "object";
+                    readonly additionalProperties: false;
+                    readonly required: readonly ["kind", "packageName", "sha256CertFingerprints"];
+                    readonly properties: {
+                        readonly kind: {
+                            readonly const: "androidApp";
+                        };
+                        readonly packageName: {
+                            readonly type: "string";
+                            readonly minLength: 1;
+                            readonly pattern: "^[A-Za-z][A-Za-z0-9_]*(\\.[A-Za-z][A-Za-z0-9_]*)+$";
+                            readonly description: "Android package name in reverse-DNS form (e.g. \"com.github.android\").";
+                        };
+                        readonly sha256CertFingerprints: {
+                            readonly type: "array";
+                            readonly minItems: 1;
+                            readonly items: {
+                                readonly type: "string";
+                                readonly pattern: "^[0-9A-F]{2}(:[0-9A-F]{2}){31}$";
+                            };
+                            readonly uniqueItems: true;
+                            readonly description: "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).";
+                        };
+                    };
+                }];
+            };
+        };
+    };
+};
+//# sourceMappingURL=payload.d.ts.map