@agentcomms/whatsapp 0.13.0 → 0.13.1

package/dist/index.d.mts

@@ -1,1298 +1,203 @@
 import { createRequire } from "node:module";
+import { styleText } from "node:util";
 //#endregion
 //#region src/version.d.ts
 /** The package version, read from package.json at build time. */
 export declare const VERSION: string;
-//#endregion
-//#region ../../node_modules/.pnpm/@modelcontextprotocol+server@2.0.0/node_modules/@modelcontextprotocol/server/dist/types-DUs7mGBv.d.mts
-//#region ../../node_modules/.pnpm/json-schema-typed@8.0.2/node_modules/json-schema-typed/draft_2020_12.d.ts
-type MaybeReadonlyArray<T> = Array<T> | ReadonlyArray<T>;
-type ValueOf<T> = T[keyof T];
-/**
- * JSON Schema [Draft 2020-12](https://json-schema.org/draft/2020-12/json-schema-validation.html)
- */
-type JSONSchema$1<Value = any, SchemaType = (Value extends boolean ? "boolean" : Value extends null ? "null" : Value extends number ? "number" | "integer" : Value extends string ? "string" : Value extends unknown[] ? "array" : Value extends Record<string | number, unknown> ? "object" : JSONSchema$1.TypeValue)> = boolean | {
-  /**
-   * Using JSON Pointer fragments requires knowledge of the structure of the
-   * schema. When writing schema documents with the intention to provide
-   * re-usable schemas, it may be preferable to use a plain name fragment
-   * that is not tied to any particular structural location.  This allows a
-   * subschema to be relocated without requiring JSON Pointer references to
-   * be updated.
-   *
-   * The `$anchor` keyword is used to specify such a fragment.  It is an
-   * identifier keyword that can only be used to create plain name fragments.
-   *
-   * If present, the value of this keyword MUST be a string, which MUST start
-   * with a letter `[A-Za-z]`, followed by any number of letters, digits
-   * `[0-9]`, hyphens `-`, underscores `_`, colons `:`,
-   * or periods `.`.
-   *
-   * Note that the anchor string does not include the `#` character,
-   * as it is not a URI-reference.  An `{"$anchor": "foo"}` becomes the
-   * fragment `#foo` when used in a URI.
-   *
-   * The base URI to which the resulting fragment is appended is determined
-   * by the `$id` keyword as explained in the previous section.
-   * Two `$anchor` keywords in the same schema document MAY have the same
-   * value if they apply to different base URIs, as the resulting full URIs
-   * will be distinct.  However, the effect of two `$anchor` keywords
-   * with the same value and the same base URI is undefined.  Implementations
-   * MAY raise an error if such usage is detected.
-   */
+declare namespace json_schema_d_exports {
+  export { ArraySchema, BaseSchema, BooleanSchema, IntegerSchema, JSONSchema$1 as JSONSchema, NullSchema, NumberSchema, ObjectSchema, Schema$1 as Schema, SchemaType, StringSchema, _JSONSchema };
+}
+type Schema$1 = ObjectSchema | ArraySchema | StringSchema | NumberSchema | IntegerSchema | BooleanSchema | NullSchema;
+type _JSONSchema = boolean | JSONSchema$1;
+type SchemaType = "object" | "array" | "string" | "number" | "boolean" | "null" | "integer";
+type JSONSchema$1 = {
+  [k: string]: unknown;
+  $schema?: "https://json-schema.org/draft/2020-12/schema" | "http://json-schema.org/draft-07/schema#" | "http://json-schema.org/draft-04/schema#";
+  $id?: string;
   $anchor?: string;
-  /**
-   * This keyword reserves a location for comments from schema authors to
-   * readers or maintainers of the schema.
-   *
-   * The value of this keyword MUST be a string. Implementations MUST NOT
-   * present this string to end users.  Tools for editing schemas SHOULD
-   * support displaying and editing this keyword.  The value of this keyword
-   * MAY be used in debug or error output which is intended for developers
-   * making use of schemas.
-   *
-   * Schema vocabularies SHOULD allow `$comment` within any object
-   * containing vocabulary keywords.  Implementations MAY assume `$comment`
-   * is allowed unless the vocabulary specifically forbids it.  Vocabularies
-   * MUST NOT specify any effect of `$comment` beyond what is described in
-   * this specification.
-   *
-   * Tools that translate other media types or programming languages
-   * to and from `application/schema+json` MAY choose to convert that media
-   * type or programming language's native comments to or from `$comment`
-   * values. The behavior of such translation when both native comments and
-   * `$comment` properties are present is implementation-dependent.
-   *
-   * Implementations MAY strip `$comment` values at any point during
-   * processing. In particular, this allows for shortening schemas when the
-   * size of deployed schemas is a concern.
-   *
-   * Implementations MUST NOT take any other action based on the presence,
-   * absence, or contents of `$comment` properties.  In particular, the
-   * value of `$comment` MUST NOT be collected as an annotation result.
-   */
+  $ref?: string;
+  $dynamicRef?: string;
+  $dynamicAnchor?: string;
+  $vocabulary?: Record<string, boolean>;
   $comment?: string;
-  /**
-   * The `$defs` keyword reserves a location for schema authors to inline
-   * re-usable JSON Schemas into a more general schema. The keyword does not
-   * directly affect the validation result.
-   *
-   * This keyword's value MUST be an object. Each member value of this object
-   * MUST be a valid JSON Schema.
-   */
   $defs?: Record<string, JSONSchema$1>;
-  /**
-   * "The `$dynamicAnchor` indicates that the fragment is an extension
-   * point when used with the `$dynamicRef` keyword. This low-level,
-   * advanced feature makes it easier to extend recursive schemas such as the
-   * meta-schemas, without imposing any particular semantics on that
-   * extension. See `$dynamicRef` for more details.
-   */
-  $dynamicAnchor?: string;
-  /**
-   * The `$dynamicRef` keyword is an applicator that allows for deferring
-   * the full resolution until runtime, at which point it is resolved each
-   * time it is encountered while evaluating an instance.
-   *
-   * Together with `$dynamicAnchor`, `$dynamicRef` implements a
-   * cooperative extension mechanism that is primarily useful with recursive
-   * schemas (schemas that reference themselves).  Both the extension point
-   * and the runtime-determined extension target are defined with
-   * `$dynamicAnchor`, and only exhibit runtime dynamic behavior when
-   * referenced with `$dynamicRef`.
-   *
-   * The value of the `$dynamicRef` property MUST be a string which is
-   * a URI-Reference.  Resolved against the current URI base, it produces
-   * the URI used as the starting point for runtime resolution.  This initial
-   * resolution is safe to perform on schema load.
-   *
-   * If the initially resolved starting point URI includes a fragment that
-   * was created by the `$dynamicAnchor` keyword, the initial URI MUST be
-   * replaced by the URI (including the fragment) for the outermost schema
-   * resource in the [dynamic scope][scopes] that defines
-   * an identically named fragment with `$dynamicAnchor`.
-   *
-   * Otherwise, its behavior is identical to `$ref`, and no runtime
-   * resolution is needed.
-   *
-   * [scopes]: https://json-schema.org/draft/2020-12/json-schema-core.html#scopes
-   *
-   * @format "uri-reference"
-   */
-  $dynamicRef?: string;
-  /**
-   * The `$id` keyword identifies a schema resource with its
-   * [canonical][[RFC6596]] URI.
-   *
-   * Note that this URI is an identifier and not necessarily a network
-   * locator. In the case of a network-addressable URL, a schema need not be
-   * downloadable from its canonical URI.
-   *
-   * If present, the value for this keyword MUST be a string, and MUST
-   * represent a valid [URI-reference][RFC3986].  This URI-reference SHOULD
-   * be normalized, and MUST resolve to an [absolute-URI][RFC3986] (without a
-   * fragment).  Therefore, `$id` MUST NOT contain a non-empty fragment,
-   * and SHOULD NOT contain an empty fragment.
-   *
-   * Since an empty fragment in the context of the
-   * `application/schema+json` media type refers to the same resource as
-   * the base URI without a fragment, an implementation MAY normalize a URI
-   * ending with an empty fragment by removing the fragment.  However, schema
-   * authors SHOULD NOT rely on this behavior across implementations.
-   *
-   * This URI also serves as the base URI for relative URI-references in
-   * keywords within the schema resource, in accordance with
-   * [RFC 3986][RFC3986] section 5.1.1 regarding base URIs embedded in
-   * content.
-   *
-   * The presence of `$id` in a subschema indicates that the subschema
-   * constitutes a distinct schema resource within a single schema document.
-   * Furthermore, in accordance with [RFC 3986][RFC3986] section 5.1.2
-   * regarding encapsulating entities, if an `$id` in a subschema is a
-   * relative URI-reference, the base URI for resolving that reference is the
-   * URI of the parent schema resource.
-   *
-   * If no parent schema object explicitly identifies itself as a resource
-   * with `$id`, the base URI is that of the entire document.
-   *
-   * The root schema of a JSON Schema document SHOULD contain an `$id`
-   * keyword with an [absolute-URI][RFC3986] (containing a scheme, but no
-   * fragment).
-   *
-   * [RFC6596]: https://datatracker.ietf.org/doc/html/rfc6596
-   * [RFC3986]: https://datatracker.ietf.org/doc/html/rfc3986
-   *
-   * @format "uri-reference"
-   */
-  $id?: string;
-  /**
-   * The `$ref` keyword is an applicator that is used to reference a
-   * statically identified schema. Its results are the results of the
-   * referenced schema. Other keywords can appear alongside of `$ref` in
-   * the same schema object.
-   *
-   * The value of the `$ref` property MUST be a string which is a
-   * URI-Reference. Resolved against the current URI base, it produces the
-   * URI of the schema to apply.
-   *
-   * @format "uri-reference"
-   */
-  $ref?: string;
-  /**
-   * The `$schema` keyword is both used as a JSON Schema dialect identifier
-   * and as the identifier of a resource which is itself a JSON Schema, which
-   * describes the set of valid schemas written for this particular dialect.
-   *
-   * The value of this keyword MUST be a [URI][RFC3986] (containing a scheme)
-   * and this URI MUST be normalized. The current schema MUST be valid
-   * against the meta-schema identified by this URI.
-   *
-   * If this URI identifies a retrievable resource, that resource SHOULD be
-   * of media type `application/schema+json`.
-   *
-   * The `$schema` keyword SHOULD be used in the document root schema
-   * object, and MAY be used in the root schema objects of embedded schema
-   * resources. It MUST NOT appear in non-resource root schema objects.  If
-   * absent from the document root schema, the resulting behavior is
-   * implementation-defined.
-   *
-   * Values for this property are defined elsewhere in this and other
-   * documents, and by other parties.
-   *
-   * [RFC3986]: https://datatracker.ietf.org/doc/html/rfc3986
-   *
-   * @format "uri"
-   */
-  $schema?: string;
-  /**
-   * The `$vocabulary` keyword is used in meta-schemas to identify the
-   * vocabularies available for use in schemas described by that meta-schema.
-   * It is also used to indicate whether each vocabulary is required or
-   * optional, in the sense that an implementation MUST understand the
-   * required vocabularies in order to successfully process the schema.
-   * Together, this information forms a dialect. Any vocabulary that is
-   * understood by the implementation MUST be processed in a manner
-   * consistent with the semantic definitions contained within the
-   * vocabulary.
-   *
-   * The value of this keyword MUST be an object.  The property names in the
-   * object MUST be URIs (containing a scheme) and this URI MUST be
-   * normalized. Each URI that appears as a property name identifies a
-   * specific set of keywords and their semantics.
-   *
-   * The URI MAY be a URL, but the nature of the retrievable resource is
-   * currently undefined, and reserved for future use.  Vocabulary authors
-   * MAY use the URL of the vocabulary specification, in a human-readable
-   * media type such as `text/html` or `text/plain`, as the vocabulary
-   * URI.
-   *
-   * The values of the object properties MUST be booleans. If the value is
-   * `true`, then implementations that do not recognize the vocabulary MUST
-   * refuse to process any schemas that declare this meta-schema with
-   * `$schema`.  If the value is `false`, implementations that do not
-   * recognize the vocabulary SHOULD proceed with processing such schemas.
-   * The value has no impact if the implementation understands the
-   * vocabulary.
-   *
-   * Unrecognized keywords SHOULD be ignored.  This remains the case for
-   * keywords defined by unrecognized vocabularies.  It is not currently
-   * possible to distinguish between unrecognized keywords that are defined
-   * in vocabularies from those that are not part of any vocabulary.
-   *
-   * The `$vocabulary` keyword SHOULD be used in the root schema of any
-   * schema document intended for use as a meta-schema.  It MUST NOT appear
-   * in subschemas.
-   *
-   * The `$vocabulary` keyword MUST be ignored in schema documents that are
-   * not being processed as a meta-schema.
-   */
-  $vocabulary?: Record<string, string>;
-  /**
-   * @deprecated `additionalItems` has been deprecated in favor of `prefixItems`
-   * paired with `items`.
-   */
-  additionalItems?: JSONSchema$1;
-  /**
-   * The value of `additionalProperties` MUST be a valid JSON Schema.
-   *
-   * The behavior of this keyword depends on the presence and annotation
-   * results of `properties` and `patternProperties` within the same
-   * schema object. Validation with `additionalProperties` applies only to
-   * the child values of instance names that do not appear in the annotation
-   * results of either `properties` or `patternProperties`.
-   *
-   * For all such properties, validation succeeds if the child instance
-   * validates against the `additionalProperties` schema.
-   *
-   * The annotation result of this keyword is the set of instance property
-   * names validated by this keyword's subschema. Annotation results for
-   * `additionalProperties` keywords from multiple schemas applied to the
-   * same instance location are combined by taking the union of the sets.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty
-   * schema.
-   *
-   * Implementations MAY choose to implement or optimize this keyword in
-   * another way that produces the same effect, such as by directly checking
-   * the names in `properties` and the patterns in `patternProperties`
-   * against the instance property set.
-   */
-  additionalProperties?: JSONSchema$1;
-  /**
-   * This keyword's value MUST be a non-empty array. Each item of the array
-   * MUST be a valid JSON Schema.
-   *
-   * An instance validates successfully against this keyword if it validates
-   * successfully against all schemas defined by this keyword's value.
-   */
-  allOf?: MaybeReadonlyArray<JSONSchema$1<Value, SchemaType>>;
-  /**
-   * This keyword's value MUST be a non-empty array. Each item of the array
-   * MUST be a valid JSON Schema.
-   *
-   * An instance validates successfully against this keyword if it validates
-   * successfully against at least one schema defined by this keyword's
-   * value.
-   */
-  anyOf?: MaybeReadonlyArray<JSONSchema$1<Value, SchemaType>>;
-  /**
-   * An instance validates successfully against this keyword if its value is
-   * equal to the value of the keyword.
-   *
-   * Use of this keyword is functionally equivalent to the `enum` keyword
-   * with a single value.
-   */
-  const?: Value;
-  /**
-   * The value of this keyword MUST be a valid JSON Schema.
-   *
-   * An array instance is valid against `contains` if at least one of its
-   * elements is valid against the given schema. The subschema MUST be
-   * applied to every array element even after the first match has been
-   * found, in order to collect annotations for use by other keywords.
-   * This is to ensure that all possible annotations are collected.
-   *
-   * Logically, the validation result of applying the value subschema to each
-   * item in the array MUST be OR'ed with `false`, resulting in an overall
-   * validation result.
-   *
-   * This keyword produces an annotation value which is an array of the
-   * indexes to which this keyword validates successfully when applying its
-   * subschema, in ascending order. The value MAY be a boolean `true` if
-   * the subschema validates successfully when applied to every index of the
-   * instance. The annotation MUST be present if the instance array to which
-   * this keyword's schema applies is empty.
-   */
-  contains?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * If the instance value is a string, this property defines that the
-   * string SHOULD be interpreted as binary data and decoded using the
-   * encoding named by this property. [RFC 2045, Sec 6.1][RFC2045] lists the
-   * possible values for this property.
-   *
-   * The value of this property SHOULD be ignored if the instance described
-   * is not a string.
-   *
-   * If this keyword is absent, but `contentMediaType` is present, this
-   * indicates that the media type could be encoded into `UTF-8` like any
-   * other JSON string value, and does not require additional decoding.
-   *
-   * The value of this property MUST be a string.
-   *
-   * [RFC2045]: https://datatracker.ietf.org/doc/html/rfc2045#section-6.1
-   */
-  contentEncoding?: "7bit" | "8bit" | "base64" | "binary" | "ietf-token" | "quoted-printable" | "x-token";
-  /**
-   * If the instance is a string, this property indicates the media type
-   * of the contents of the string.  If `contentEncoding` is present,
-   * this property describes the decoded string.
-   *
-   * The value of this property must be a media type, as defined by
-   * [RFC 2046][RFC2046]. This property defines the media type of instances
-   * which this schema defines.
-   *
-   * The value of this property SHOULD be ignored if the instance described
-   * is not a string.
-   *
-   * If the `contentEncoding` property is not present, but the instance
-   * value is a string, then the value of this property SHOULD specify a text
-   * document type, and the character set SHOULD be the character set into
-   * which the JSON string value was decoded (for which the default is
-   * Unicode).
-   *
-   * [RFC2046]: https://datatracker.ietf.org/doc/html/rfc2046
-   */
-  contentMediaType?: string;
-  /**
-   * If the instance is a string, and if `contentMediaType` is present,
-   * this property contains a schema which describes the structure of the
-   * string.
-   *
-   * This keyword MAY be used with any media type that can be mapped into
-   * JSON Schema's data model.
-   *
-   * The value of this property MUST be a valid JSON schema. It SHOULD be
-   * ignored if `contentMediaType` is not present.
-   */
-  contentSchema?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * This keyword can be used to supply a default JSON value associated with
-   * a particular schema. It is RECOMMENDED that a `default` value be valid
-   * against the associated schema.
-   */
-  default?: Value;
-  /**
-   * @deprecated `definitions` has been renamed to `$defs`.
-   */
-  definitions?: Record<string, JSONSchema$1>;
-  /**
-   * @deprecated `dependencies` has been split into two keywords:
-   * `dependentSchemas` and `dependentRequired`.
-   */
-  dependencies?: Record<string, MaybeReadonlyArray<string> | JSONSchema$1>;
-  /**
-   * The value of this keyword MUST be an object.  Properties in
-   * this object, if any, MUST be arrays.  Elements in each array,
-   * if any, MUST be strings, and MUST be unique.
-   *
-   * This keyword specifies properties that are required if a specific
-   * other property is present.  Their requirement is dependent on the
-   * presence of the other property.
-   *
-   * Validation succeeds if, for each name that appears in both
-   * the instance and as a name within this keyword's value, every
-   * item in the corresponding array is also the name of a property
-   * in the instance.
-   *
-   * Omitting this keyword has the same behavior as an empty object.
-   */
-  dependentRequired?: Record<string, MaybeReadonlyArray<string>>;
-  /**
-   * This keyword specifies subschemas that are evaluated if the instance is
-   * an object and contains a certain property.
-   *
-   * This keyword's value MUST be an object. Each value in the object MUST be
-   * a valid JSON Schema.
-   *
-   * If the object key is a property in the instance, the entire instance
-   * must validate against the subschema. Its use is dependent on the
-   * presence of the property.
-   *
-   * Omitting this keyword has the same behavior as an empty object.
-   */
-  dependentSchemas?: Record<string, JSONSchema$1>;
-  /**
-   * The value of this keyword MUST be a boolean.  When multiple occurrences
-   * of this keyword are applicable to a single sub-instance, applications
-   * SHOULD consider the instance location to be deprecated if any occurrence
-   * specifies a `true` value.
-   *
-   * If `deprecated` has a value of boolean `true`, it indicates that
-   * applications SHOULD refrain from usage of the declared property. It MAY
-   * mean the property is going to be removed in the future.
-   *
-   * A root schema containing `deprecated` with a value of `true`
-   * indicates that the entire resource being described MAY be removed in the
-   * future.
-   *
-   * The `deprecated` keyword applies to each instance location to which
-   * the schema object containing the keyword successfully applies.  This can
-   * result in scenarios where every array item or object property is
-   * deprecated even though the containing array or object is not.
-   *
-   * Omitting this keyword has the same behavior as a value of `false`.
-   */
-  deprecated?: boolean;
-  /**
-   * Can be used to decorate a user interface with explanation or information
-   * about the data produced.
-   */
-  description?: string;
-  /**
-   * This keyword's value MUST be a valid JSON Schema.
-   *
-   * When `if` is present, and the instance fails to validate against its
-   * subschema, then validation succeeds against this keyword if the instance
-   * successfully validates against this keyword's subschema.
-   *
-   * This keyword has no effect when `if` is absent, or when the instance
-   * successfully validates against its subschema. Implementations MUST NOT
-   * evaluate the instance against this keyword, for either validation or
-   * annotation collection purposes, in such cases.
-   */
-  else?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * The value of this keyword MUST be an array. This array SHOULD have at
-   * least one element. Elements in the array SHOULD be unique.
-   *
-   * An instance validates successfully against this keyword if its value is
-   * equal to one of the elements in this keyword's array value.
-   *
-   * Elements in the array might be of any type, including `null`.
-   */
-  enum?: MaybeReadonlyArray<Value>;
-  /**
-   * The value of this keyword MUST be an array. When multiple occurrences of
-   * this keyword are applicable to a single sub-instance, implementations
-   * MUST provide a flat array of all values rather than an array of arrays.
-   *
-   * This keyword can be used to provide sample JSON values associated with a
-   * particular schema, for the purpose of illustrating usage. It is
-   * RECOMMENDED that these values be valid against the associated schema.
-   *
-   * Implementations MAY use the value(s) of `default`, if present, as an
-   * additional example. If `examples` is absent, `default` MAY still be
-   * used in this manner.
-   */
-  examples?: MaybeReadonlyArray<Value>;
-  /**
-   * The value of `exclusiveMaximum` MUST be a number, representing an
-   * exclusive upper limit for a numeric instance.
-   *
-   * If the instance is a number, then the instance is valid only if it has a
-   * value strictly less than (not equal to) `exclusiveMaximum`.
-   */
-  exclusiveMaximum?: number;
-  /**
-   * The value of `exclusiveMinimum` MUST be a number, representing an
-   * exclusive lower limit for a numeric instance.
-   *
-   * If the instance is a number, then the instance is valid only if it has a
-   * value strictly greater than (not equal to) `exclusiveMinimum`.
-   */
-  exclusiveMinimum?: number;
-  /**
-   * Implementations MAY treat `format` as an assertion in addition to an
-   * annotation, and attempt to validate the value's conformance to the
-   * specified semantics.
-   *
-   * The value of this keyword is called a format attribute. It MUST be a
-   * string. A format attribute can generally only validate a given set
-   * of instance types. If the type of the instance to validate is not in
-   * this set, validation for this format attribute and instance SHOULD
-   * succeed. Format attributes are most often applied to strings, but can
-   * be specified to apply to any type.
-   *
-   * Implementations MAY support custom format attributes. Save for agreement
-   * between parties, schema authors SHALL NOT expect a peer implementation
-   * to support such custom format attributes.  An implementation MUST NOT
-   * fail validation or cease processing due to an unknown format attribute.
-   * When treating `format` as an annotation, implementations SHOULD
-   * collect both known and unknown format attribute values.
-   */
-  format?: string;
-  /**
-   * This keyword's value MUST be a valid JSON Schema.
-   *
-   * This validation outcome of this keyword's subschema has no direct effect
-   * on the overall validation result. Rather, it controls which of the
-   * `then` or `else` keywords are evaluated.
-   *
-   * Instances that successfully validate against this keyword's subschema
-   * MUST also be valid against the subschema value of the `then` keyword,
-   * if present.
-   *
-   * Instances that fail to validate against this keyword's subschema MUST
-   * also be valid against the subschema value of the `else` keyword, if
-   * present.
-   *
-   * If annotations are being collected, they are collected
-   * from this keyword's subschema in the usual way, including when the
-   * keyword is present without either `then` or `else`.
-   */
-  if?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * The value of `items` MUST be a valid JSON Schema.
-   *
-   * This keyword applies its subschema to all instance elements at indexes
-   * greater than the length of the `prefixItems` array in the same schema
-   * object, as reported by the annotation result of that `prefixItems`
-   * keyword.  If no such annotation result exists, `items` applies its
-   * subschema to all instance array elements.
-   *
-   * Note that the behavior of `items` without `prefixItems` is identical
-   * to that of the schema form of `items` in prior drafts.
-   *
-   * When `prefixItems` is present, the behavior of `items` is identical
-   * to the former `additionalItems` keyword.
-   *
-   * If the `items` subschema is applied to any positions within the
-   * instance array, it produces an annotation result of boolean `true`,
-   * indicating that all remaining array elements have been evaluated against
-   * this keyword's subschema.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty
-   * schema.
-   *
-   * Implementations MAY choose to implement or optimize this keyword
-   * in another way that produces the same effect, such as by directly
-   * checking for the presence and size of a `prefixItems` array.
-   */
-  items?: JSONSchema$1;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * If `contains` is not present within the same schema object, then this
-   * keyword has no effect.
-   *
-   * An instance array is valid against `maxContains` in two ways,
-   * depending on the form of the annotation result of an adjacent
-   * `contains` keyword. The first way is if the annotation result is an
-   * array and the length of that array is less than or equal to the
-   * `maxContains` value. The second way is if the annotation result is a
-   * boolean `true` and the instance array length is less than or equal to
-   * the `maxContains` value.
-   */
-  maxContains?: number;
-  /**
-   * The value of `maximum` MUST be a number, representing an inclusive
-   * upper limit for a numeric instance.
-   *
-   * If the instance is a number, then this keyword validates only if the
-   * instance is less than or exactly equal to `maximum`.
-   */
-  maximum?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * An array instance is valid against `maxItems` if its size is less
-   * than, or equal to, the value of this keyword.
-   *
-   * @minimum 0
-   */
-  maxItems?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * A string instance is valid against this keyword if its length is less
-   * than, or equal to, the value of this keyword.
-   *
-   * The length of a string instance is defined as the number of its
-   * characters as defined by [RFC 8259][RFC8259].
-   *
-   * [RFC8259]: https://datatracker.ietf.org/doc/html/rfc8259
-   *
-   * @minimum 0
-   */
-  maxLength?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * An object instance is valid against `maxProperties` if its number of
-   * `properties` is less than, or equal to, the value of this keyword.
-   *
-   * @minimum 0
-   */
-  maxProperties?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * If `contains` is not present within the same schema object, then this
-   * keyword has no effect.
-   *
-   * An instance array is valid against `minContains` in two ways,
-   * depending on the form of the annotation result of an adjacent
-   * `contains` keyword. The first way is if the annotation result is an
-   * array and the length of that array is greater than or equal to the
-   * `minContains` value. The second way is if the annotation result is a
-   * boolean `true` and the instance array length is greater than or equal
-   * to the `minContains` value.
-   *
-   * A value of `0` is allowed, but is only useful for setting a range
-   * of occurrences from `0` to the value of `maxContains`.  A value of
-   * `0` with no `maxContains` causes `contains` to always pass
-   * validation.
-   *
-   * Omitting this keyword has the same behavior as a value of `1`.
-   *
-   * @default 1
-   */
-  minContains?: number;
-  /**
-   * The value of `minimum` MUST be a number, representing an inclusive
-   * lower limit for a numeric instance.
-   *
-   * If the instance is a number, then this keyword validates only if the
-   * instance is greater than or exactly equal to `minimum`.
-   */
-  minimum?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * An array instance is valid against `minItems` if its size is greater
-   * than, or equal to, the value of this keyword.
-   *
-   * Omitting this keyword has the same behavior as a value of `0`.
-   *
-   * @default 0
-   * @minimum 0
-   */
-  minItems?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * A string instance is valid against this keyword if its length is greater
-   * than, or equal to, the value of this keyword.
-   *
-   * The length of a string instance is defined as the number of its
-   * characters as defined by [RFC 8259][RFC8259].
-   *
-   * Omitting this keyword has the same behavior as a value of `0`.
-   *
-   * [RFC8259]: https://datatracker.ietf.org/doc/html/rfc8259
-   *
-   * @default 0
-   * @minimum 0
-   */
-  minLength?: number;
-  /**
-   * The value of this keyword MUST be a non-negative integer.
-   *
-   * An object instance is valid against `minProperties` if its number of
-   * `properties` is greater than, or equal to, the value of this keyword.
-   *
-   * Omitting this keyword has the same behavior as a value of `0`.
-   *
-   * @default 0
-   * @minimum 0
-   */
-  minProperties?: number;
-  /**
-   * The value of `multipleOf` MUST be a number, strictly greater than
-   * `0`.
-   *
-   * A numeric instance is valid only if division by this keyword's value
-   * results in an integer.
-   *
-   * @exclusiveMinimum 0
-   */
-  multipleOf?: number;
-  /**
-   * This keyword's value MUST be a valid JSON Schema.
-   *
-   * An instance is valid against this keyword if it fails to validate
-   * successfully against the schema defined by this keyword.
-   */
-  not?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * This keyword's value MUST be a non-empty array. Each item of the array
-   * MUST be a valid JSON Schema.
-   *
-   * An instance validates successfully against this keyword if it validates
-   * successfully against exactly one schema defined by this keyword's value.
-   */
-  oneOf?: MaybeReadonlyArray<JSONSchema$1<Value, SchemaType>>;
-  /**
-   * The value of this keyword MUST be a string. This string SHOULD be a
-   * valid regular expression, according to the [ECMA-262][ecma262] regular
-   * expression dialect.
-   *
-   * A string instance is considered valid if the regular expression matches
-   * the instance successfully. Recall: regular expressions are not
-   * implicitly anchored.
-   *
-   * [ecma262]: https://www.ecma-international.org/publications-and-standards/standards/ecma-262/
-   *
-   * @format "regex"
-   */
-  pattern?: string;
-  /**
-   * The value of `patternProperties` MUST be an object. Each property name
-   * of this object SHOULD be a valid regular expression, according to the
-   * [ECMA-262][ecma262] regular expression dialect. Each property value of
-   * this object MUST be a valid JSON Schema.
-   *
-   * Validation succeeds if, for each instance name that matches any regular
-   * expressions that appear as a property name in this keyword's value,
-   * the child instance for that name successfully validates against each
-   * schema that corresponds to a matching regular expression.
-   *
-   * The annotation result of this keyword is the set of instance property
-   * names matched by this keyword. Omitting this keyword has the same
-   * assertion behavior as an empty object.
-   *
-   * [ecma262]: https://www.ecma-international.org/publications-and-standards/standards/ecma-262/
-   */
-  patternProperties?: Record<string, JSONSchema$1>;
-  /**
-   * The value of `prefixItems` MUST be a non-empty array of valid JSON
-   * Schemas.
-   *
-   * Validation succeeds if each element of the instance validates against
-   * the schema at the same position, if any.  This keyword does not
-   * constrain the length of the array.  If the array is longer than this
-   * keyword's value, this keyword validates only the prefix of matching
-   * length.
-   *
-   * This keyword produces an annotation value which is the largest index to
-   * which this keyword applied a subschema.  The value MAY be a boolean
-   * `true` if a subschema was applied to every index of the instance, such
-   * as is produced by the `items` keyword.
-   * This annotation affects the behavior of `items` and
-   * `unevaluatedItems`.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty array.
-   */
-  prefixItems?: MaybeReadonlyArray<JSONSchema$1> | JSONSchema$1;
-  /**
-   * The value of `properties` MUST be an object. Each value of this object
-   * MUST be a valid JSON Schema.
-   *
-   * Validation succeeds if, for each name that appears in both the instance
-   * and as a name within this keyword's value, the child instance for that
-   * name successfully validates against the corresponding schema.
-   *
-   * The annotation result of this keyword is the set of instance property
-   * names matched by this keyword.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty
-   * object.
-   */
-  properties?: Record<string, JSONSchema$1>;
-  /**
-   * The value of `propertyNames` MUST be a valid JSON Schema.
-   *
-   * If the instance is an object, this keyword validates if every property
-   * name in the instance validates against the provided schema.
-   * Note the property name that the schema is testing will always be a
-   * string.
-   *
-   * Omitting this keyword has the same behavior as an empty schema.
-   */
-  propertyNames?: JSONSchema$1;
-  /**
-   * The value of this keyword MUST be a boolean. When multiple occurrences
-   * of this keyword are applicable to a single sub-instance, the resulting
-   * value MUST be `true` if any occurrence specifies a `true` value, and
-   * MUST be `false` otherwise.
-   *
-   * If `readOnly` has a value of boolean `true`, it indicates that the
-   * value of the instance is managed exclusively by the owning authority,
-   * and attempts by an application to modify the value of this property are
-   * expected to be ignored or rejected by that owning authority.
-   *
-   * An instance document that is marked as `readOnly` for the entire
-   * document MAY be ignored if sent to the owning authority, or MAY result
-   * in an error, at the authority's discretion.
-   *
-   * For example, `readOnly` would be used to mark a database-generated
-   * serial number as read-only.
-   *
-   * This keyword can be used to assist in user interface instance
-   * generation.
-   *
-   * @default false
-   */
-  readOnly?: boolean;
-  /**
-   * The value of this keyword MUST be an array. Elements of this array, if
-   * any, MUST be strings, and MUST be unique.
-   *
-   * An object instance is valid against this keyword if every item in the
-   * array is the name of a property in the instance.
-   *
-   * Omitting this keyword has the same behavior as an empty array.
-   */
-  required?: MaybeReadonlyArray<string>;
-  /**
-   * This keyword's value MUST be a valid JSON Schema.
-   *
-   * When `if` is present, and the instance successfully validates against
-   * its subschema, then validation succeeds against this keyword if the
-   * instance also successfully validates against this keyword's subschema.
-   *
-   * This keyword has no effect when `if` is absent, or when the instance
-   * fails to validate against its subschema. Implementations MUST NOT
-   * evaluate the instance against this keyword, for either validation or
-   * annotation collection purposes, in such cases.
-   */
-  then?: JSONSchema$1<Value, SchemaType>;
-  /**
-   * Can be used to decorate a user interface with a short label about the
-   * data produced.
-   */
-  title?: string;
-  /**
-   * The value of this keyword MUST be either a string or an array. If it is
-   * an array, elements of the array MUST be strings and MUST be unique.
-   *
-   * String values MUST be one of the six primitive types (`"null"`,
-   * `"boolean"`, `"object"`, `"array"`, `"number"`, or
-   * `"string"`), or `"integer"` which matches any number with a zero
-   * fractional part.
-   *
-   * An instance validates if and only if the instance is in any of the sets
-   * listed for this keyword.
-   */
-  type?: SchemaType;
-  /**
-   * The value of `unevaluatedItems` MUST be a valid JSON Schema.
-   *
-   * The behavior of this keyword depends on the annotation results of
-   * adjacent keywords that apply to the instance location being validated.
-   * Specifically, the annotations from `prefixItems`, `items`, and
-   * `contains`, which can come from those keywords when they are adjacent
-   * to the `unevaluatedItems` keyword. Those three annotations, as well as
-   * `unevaluatedItems`, can also result from any and all adjacent
-   * [in-place applicator][in-place-applicator] keywords.
-   *
-   * If no relevant annotations are present, the `unevaluatedItems`
-   * subschema MUST be applied to all locations in the array.
-   * If a boolean `true` value is present from any of the relevant
-   * annotations, `unevaluatedItems` MUST be ignored.  Otherwise, the
-   * subschema MUST be applied to any index greater than the largest
-   * annotation value for `prefixItems`, which does not appear in any
-   * annotation value for `contains`.
-   *
-   * This means that `prefixItems`, `items`, `contains`, and all
-   * in-place applicators MUST be evaluated before this keyword can be
-   * evaluated. Authors of extension keywords MUST NOT define an in-place
-   * applicator that would need to be evaluated after this keyword.
-   *
-   * If the `unevaluatedItems` subschema is applied to any positions within
-   * the instance array, it produces an annotation result of boolean
-   * `true`, analogous to the behavior of `items`.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty
-   * schema.
-   *
-   * [in-place-applicator]: https://json-schema.org/draft/2020-12/json-schema-core.html#in-place
-   */
-  unevaluatedItems?: JSONSchema$1;
-  /**
-   * The value of `unevaluatedProperties` MUST be a valid JSON Schema.
-   *
-   * The behavior of this keyword depends on the annotation results of
-   * adjacent keywords that apply to the instance location being validated.
-   * Specifically, the annotations from `properties`,
-   * `patternProperties`, and `additionalProperties`, which can come from
-   * those keywords when they are adjacent to the `unevaluatedProperties`
-   * keyword.  Those three annotations, as well as `unevaluatedProperties`,
-   * can also result from any and all adjacent
-   * [in-place applicator][in-place-applicator] keywords.
-   *
-   * Validation with `unevaluatedProperties` applies only to the child
-   * values of instance names that do not appear in the `properties`,
-   * `patternProperties`, `additionalProperties`, or
-   * `unevaluatedProperties` annotation results that apply to the
-   * instance location being validated.
-   *
-   * For all such properties, validation succeeds if the child instance
-   * validates against the "unevaluatedProperties" schema.
-   *
-   * This means that `properties`, `patternProperties`,
-   * `additionalProperties`, and all in-place applicators MUST be evaluated
-   * before this keyword can be evaluated.  Authors of extension keywords
-   * MUST NOT define an in-place applicator that would need to be evaluated
-   * after this keyword.
-   *
-   * The annotation result of this keyword is the set of instance property
-   * names validated by this keyword's subschema.
-   *
-   * Omitting this keyword has the same assertion behavior as an empty
-   * schema.
-   *
-   * [in-place-applicator]: https://json-schema.org/draft/2020-12/json-schema-core.html#in-place
-   */
-  unevaluatedProperties?: JSONSchema$1;
-  /**
-   * The value of this keyword MUST be a boolean.
-   *
-   * If this keyword has boolean value `false`, the instance validates
-   * successfully. If it has boolean value `true`, the instance validates
-   * successfully if all of its elements are unique.
-   *
-   * Omitting this keyword has the same behavior as a value of `false`.
-   *
-   * @default false
-   */
-  uniqueItems?: boolean;
-  /**
-   * The value of this keyword MUST be a boolean. When multiple occurrences
-   * of this keyword is applicable to a single sub-instance, the resulting
-   * value MUST be `true` if any occurrence specifies a `true` value, and
-   * MUST be `false` otherwise.
-   *
-   * If `writeOnly` has a value of boolean `true`, it indicates that the
-   * value is never present when the instance is retrieved from the owning
-   * authority. It can be present when sent to the owning authority to update
-   * or create the document (or the resource it represents), but it will not
-   * be included in any updated or newly created version of the instance.
-   *
-   * An instance document that is marked as `writeOnly` for the entire
-   * document MAY be returned as a blank document of some sort, or MAY
-   * produce an error upon retrieval, or have the retrieval request ignored,
-   * at the authority's discretion.
-   *
-   * For example, `writeOnly` would be used to mark a password input field.
-   *
-   * These keywords can be used to assist in user interface instance
-   * generation. In particular, an application MAY choose to use a widget
-   * that hides input values as they are typed for write-only fields.
-   *
-   * @default false
-   */
-  writeOnly?: boolean;
-};
-declare namespace JSONSchema$1 {
-  type TypeValue = ValueOf<TypeName> | TypeName | Array<ValueOf<TypeName> | TypeName> | ReadonlyArray<ValueOf<TypeName> | TypeName>;
-  /**
-   * JSON Schema interface
-   */
-  type Interface<Value = any, SchemaType extends TypeValue = TypeValue> = Exclude<JSONSchema$1<Value, SchemaType>, boolean>;
-  type Array<T = any> = Pick<Interface<T, "array">, KeywordByType.Any | KeywordByType.Array>;
-  type Boolean = Pick<Interface<boolean, "boolean">, KeywordByType.Any>;
-  type Integer = Pick<Interface<number, "integer">, KeywordByType.Any | KeywordByType.Number>;
-  type Number = Pick<Interface<number, "number">, KeywordByType.Any | KeywordByType.Number>;
-  type Null = Pick<Interface<null, "null">, KeywordByType.Any>;
-  type Object<T = any> = Pick<Interface<T, "object">, KeywordByType.Any | KeywordByType.Object>;
-  type String = Pick<Interface<string, "string">, KeywordByType.Any | KeywordByType.String>;
-}
-declare namespace KeywordByType {
-  type Any = "$anchor" | "$comment" | "$defs" | "$dynamicAnchor" | "$dynamicRef" | "$id" | "$ref" | "$schema" | "$vocabulary" | "allOf" | "anyOf" | "const" | "default" | "definitions" | "deprecated" | "description" | "else" | "enum" | "examples" | "format" | "if" | "not" | "oneOf" | "readOnly" | "then" | "title" | "type" | "writeOnly";
-  type Array = "additionalItems" | "contains" | "items" | "maxContains" | "maxItems" | "minContains" | "minItems" | "prefixItems" | "unevaluatedItems" | "uniqueItems";
-  type Number = "exclusiveMaximum" | "exclusiveMinimum" | "maximum" | "minimum" | "multipleOf";
-  type Object = "additionalProperties" | "dependencies" | "dependentRequired" | "dependentSchemas" | "maxProperties" | "minProperties" | "patternProperties" | "properties" | "propertyNames" | "required" | "unevaluatedProperties";
-  type String = "contentEncoding" | "contentMediaType" | "contentSchema" | "maxLength" | "minLength" | "pattern";
-}
-/**
- * Content encoding strategy enum.
- *
- * - [Content-Transfer-Encoding Syntax](https://datatracker.ietf.org/doc/html/rfc2045#section-6.1)
- * - [7bit vs 8bit encoding](https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit/28531705#28531705)
- */
-/**
- * Enum consisting of simple type names for the `type` keyword
- */
-declare enum TypeName {
-  /**
-   * Value MUST be an array.
-   */
-  Array = "array",
-  /**
-   * Value MUST be a boolean.
-   */
-  Boolean = "boolean",
-  /**
-   * Value MUST be an integer, no floating point numbers are allowed. This is a
-   * subset of the number type.
-   */
-  Integer = "integer",
-  /**
-   * Value MUST be null. Note this is mainly for purpose of being able use union
-   * types to define nullability. If this type is not included in a union, null
-   * values are not allowed (the primitives listed above do not allow nulls on
-   * their own).
-   */
-  Null = "null",
-  /**
-   * Value MUST be a number, floating point numbers are allowed.
-   */
-  Number = "number",
-  /**
-   * Value MUST be an object.
-   */
-  Object = "object",
-  /**
-   * Value MUST be a string.
-   */
-  String = "string"
-}
-//#endregion
-//#region ../core-internal/src/validators/types.d.ts
-/**
- * JSON Schema type definition (JSON Schema Draft 2020-12)
- *
- * This uses the object form of JSON Schema (excluding boolean schemas).
- * While `true` and `false` are valid JSON Schemas, this SDK uses the
- * object form for practical type safety.
- *
- * Re-exported from json-schema-typed for convenience.
- * @see https://json-schema.org/draft/2020-12/json-schema-core.html
- */
-type JsonSchemaType = JSONSchema$1.Interface;
-/**
- * Result of a JSON Schema validation operation
- */
-type JsonSchemaValidatorResult<T> = {
-  valid: true;
-  data: T;
-  errorMessage: undefined;
-} | {
-  valid: false;
-  data: undefined;
-  errorMessage: string;
-};
-/**
- * A validator function that validates data against a JSON Schema
- */
-type JsonSchemaValidator<T> = (input: unknown) => JsonSchemaValidatorResult<T>;
-/**
- * Provider interface for creating validators from JSON Schemas
- *
- * This is the main extension point for custom validator implementations.
- * Implementations should:
- * - Support JSON Schema Draft 2020-12 (or be compatible with it)
- * - Return validator functions that can be called multiple times
- * - Handle schema compilation/caching internally
- * - Provide clear error messages on validation failure
- *
- * @example
- * ```ts source="./types.examples.ts#jsonSchemaValidator_implementation"
- * class MyValidatorProvider implements jsonSchemaValidator {
- *     getValidator<T>(schema: JsonSchemaType): JsonSchemaValidator<T> {
- *         // Compile/cache validator from schema
- *         return (input: unknown) =>
- *             isValid(schema, input)
- *                 ? { valid: true, data: input as T, errorMessage: undefined }
- *                 : { valid: false, data: undefined, errorMessage: 'Error details' };
- *     }
- * }
- * ```
- */
-interface jsonSchemaValidator {
-  /**
-   * Create a validator for the given JSON Schema
-   *
-   * @param schema - Standard JSON Schema object
-   * @returns A validator function that can be called multiple times
-   */
-  getValidator<T>(schema: JsonSchemaType): JsonSchemaValidator<T>;
-}
-declare namespace json_schema_d_exports {
-  export { ArraySchema, BaseSchema, BooleanSchema, IntegerSchema, JSONSchema, NullSchema, NumberSchema, ObjectSchema, Schema$1 as Schema, SchemaType, StringSchema, _JSONSchema };
-}
-type Schema$1 = ObjectSchema | ArraySchema | StringSchema | NumberSchema | IntegerSchema | BooleanSchema | NullSchema;
-type _JSONSchema = boolean | JSONSchema;
-type SchemaType = "object" | "array" | "string" | "number" | "boolean" | "null" | "integer";
-type JSONSchema = {
-  [k: string]: unknown;
-  $schema?: "https://json-schema.org/draft/2020-12/schema" | "http://json-schema.org/draft-07/schema#" | "http://json-schema.org/draft-04/schema#";
-  $id?: string;
-  $anchor?: string;
-  $ref?: string;
-  $dynamicRef?: string;
-  $dynamicAnchor?: string;
-  $vocabulary?: Record<string, boolean>;
-  $comment?: string;
-  $defs?: Record<string, JSONSchema>;
-  type?: SchemaType | SchemaType[];
-  additionalItems?: _JSONSchema;
-  unevaluatedItems?: _JSONSchema;
-  prefixItems?: _JSONSchema[];
-  items?: _JSONSchema | _JSONSchema[];
-  contains?: _JSONSchema;
-  additionalProperties?: _JSONSchema;
-  unevaluatedProperties?: _JSONSchema;
-  properties?: Record<string, _JSONSchema>;
-  patternProperties?: Record<string, _JSONSchema>;
-  dependentSchemas?: Record<string, _JSONSchema>;
-  propertyNames?: _JSONSchema;
-  if?: _JSONSchema;
-  then?: _JSONSchema;
-  else?: _JSONSchema;
-  allOf?: JSONSchema[];
-  anyOf?: JSONSchema[];
-  oneOf?: JSONSchema[];
-  not?: _JSONSchema;
-  multipleOf?: number;
-  maximum?: number;
-  exclusiveMaximum?: number | boolean;
-  minimum?: number;
-  exclusiveMinimum?: number | boolean;
-  maxLength?: number;
-  minLength?: number;
-  pattern?: string;
-  maxItems?: number;
-  minItems?: number;
-  uniqueItems?: boolean;
-  maxContains?: number;
-  minContains?: number;
-  maxProperties?: number;
-  minProperties?: number;
-  required?: string[];
-  dependentRequired?: Record<string, string[]>;
-  enum?: Array<string | number | boolean | null>;
-  const?: string | number | boolean | null;
-  id?: string;
-  title?: string;
-  description?: string;
-  default?: unknown;
-  deprecated?: boolean;
-  readOnly?: boolean;
-  writeOnly?: boolean;
-  nullable?: boolean;
-  examples?: unknown[];
-  format?: string;
-  contentMediaType?: string;
-  contentEncoding?: string;
-  contentSchema?: JSONSchema;
-  _prefault?: unknown;
-};
-type BaseSchema = JSONSchema;
-interface ObjectSchema extends JSONSchema {
-  type: "object";
-}
-interface ArraySchema extends JSONSchema {
-  type: "array";
-}
-interface StringSchema extends JSONSchema {
-  type: "string";
-}
-interface NumberSchema extends JSONSchema {
-  type: "number";
-}
-interface IntegerSchema extends JSONSchema {
-  type: "integer";
-}
-interface BooleanSchema extends JSONSchema {
-  type: "boolean";
-}
-interface NullSchema extends JSONSchema {
-  type: "null";
-}
-//#endregion
-//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/core/standard-schema.d.cts
-/** The Standard interface. */
-interface StandardTypedV1$1<Input = unknown, Output = Input> {
-  /** The Standard properties. */
-  readonly "~standard": StandardTypedV1$1.Props<Input, Output>;
-}
-declare namespace StandardTypedV1$1 {
-  /** The Standard properties interface. */
-  interface Props<Input = unknown, Output = Input> {
-    /** The version number of the standard. */
-    readonly version: 1;
-    /** The vendor name of the schema library. */
-    readonly vendor: string;
-    /** Inferred types associated with the schema. */
-    readonly types?: Types<Input, Output> | undefined;
-  }
-  /** The Standard types interface. */
-  interface Types<Input = unknown, Output = Input> {
-    /** The input type of the schema. */
-    readonly input: Input;
-    /** The output type of the schema. */
-    readonly output: Output;
-  }
-  /** Infers the input type of a Standard. */
-  type InferInput<Schema extends StandardTypedV1$1> = NonNullable<Schema["~standard"]["types"]>["input"];
-  /** Infers the output type of a Standard. */
-  type InferOutput<Schema extends StandardTypedV1$1> = NonNullable<Schema["~standard"]["types"]>["output"];
-}
-/** The Standard Schema interface. */
-interface StandardSchemaV1$1<Input = unknown, Output = Input> {
-  /** The Standard Schema properties. */
-  readonly "~standard": StandardSchemaV1$1.Props<Input, Output>;
-}
-declare namespace StandardSchemaV1$1 {
-  /** The Standard Schema properties interface. */
-  interface Props<Input = unknown, Output = Input> extends StandardTypedV1$1.Props<Input, Output> {
-    /** Validates unknown input values. */
-    readonly validate: (value: unknown, options?: StandardSchemaV1$1.Options | undefined) => Result<Output> | Promise<Result<Output>>;
-  }
-  /** The result interface of the validate function. */
-  type Result<Output> = SuccessResult<Output> | FailureResult;
-  /** The result interface if validation succeeds. */
-  interface SuccessResult<Output> {
-    /** The typed output value. */
-    readonly value: Output;
-    /** The absence of issues indicates success. */
-    readonly issues?: undefined;
-  }
-  interface Options {
-    /** Implicit support for additional vendor-specific parameters, if needed. */
-    readonly libraryOptions?: Record<string, unknown> | undefined;
-  }
-  /** The result interface if validation fails. */
-  interface FailureResult {
-    /** The issues of failed validation. */
-    readonly issues: ReadonlyArray<Issue>;
-  }
-  /** The issue interface of the failure output. */
-  interface Issue {
-    /** The error message of the issue. */
-    readonly message: string;
-    /** The path of the issue, if any. */
-    readonly path?: ReadonlyArray<PropertyKey | PathSegment> | undefined;
-  }
-  /** The path segment interface of the issue. */
-  interface PathSegment {
-    /** The key representing a path segment. */
-    readonly key: PropertyKey;
-  }
-  /** The Standard types interface. */
-  interface Types<Input = unknown, Output = Input> extends StandardTypedV1$1.Types<Input, Output> {}
-  /** Infers the input type of a Standard. */
-  type InferInput<Schema extends StandardTypedV1$1> = StandardTypedV1$1.InferInput<Schema>;
-  /** Infers the output type of a Standard. */
-  type InferOutput<Schema extends StandardTypedV1$1> = StandardTypedV1$1.InferOutput<Schema>;
-}
-/** The Standard JSON Schema interface. */
-interface StandardJSONSchemaV1$1<Input = unknown, Output = Input> {
-  /** The Standard JSON Schema properties. */
-  readonly "~standard": StandardJSONSchemaV1$1.Props<Input, Output>;
-}
-declare namespace StandardJSONSchemaV1$1 {
-  /** The Standard JSON Schema properties interface. */
-  interface Props<Input = unknown, Output = Input> extends StandardTypedV1$1.Props<Input, Output> {
-    /** Methods for generating the input/output JSON Schema. */
-    readonly jsonSchema: Converter;
-  }
-  /** The Standard JSON Schema converter interface. */
-  interface Converter {
-    /** Converts the input type to JSON Schema. May throw if conversion is not supported. */
-    readonly input: (options: StandardJSONSchemaV1$1.Options) => Record<string, unknown>;
-    /** Converts the output type to JSON Schema. May throw if conversion is not supported. */
-    readonly output: (options: StandardJSONSchemaV1$1.Options) => Record<string, unknown>;
-  }
-  /** The target version of the generated JSON Schema.
-   *
-   * It is *strongly recommended* that implementers support `"draft-2020-12"` and `"draft-07"`, as they are both in wide use.
-   *
-   * The `"openapi-3.0"` target is intended as a standardized specifier for OpenAPI 3.0 which is a superset of JSON Schema `"draft-04"`.
-   *
-   * All other targets can be implemented on a best-effort basis. Libraries should throw if they don't support a specified target.
+  type?: SchemaType | SchemaType[];
+  additionalItems?: _JSONSchema;
+  unevaluatedItems?: _JSONSchema;
+  prefixItems?: _JSONSchema[];
+  items?: _JSONSchema | _JSONSchema[];
+  contains?: _JSONSchema;
+  additionalProperties?: _JSONSchema;
+  unevaluatedProperties?: _JSONSchema;
+  properties?: Record<string, _JSONSchema>;
+  patternProperties?: Record<string, _JSONSchema>;
+  dependentSchemas?: Record<string, _JSONSchema>;
+  propertyNames?: _JSONSchema;
+  if?: _JSONSchema;
+  then?: _JSONSchema;
+  else?: _JSONSchema;
+  allOf?: JSONSchema$1[];
+  anyOf?: JSONSchema$1[];
+  oneOf?: JSONSchema$1[];
+  not?: _JSONSchema;
+  multipleOf?: number;
+  maximum?: number;
+  exclusiveMaximum?: number | boolean;
+  minimum?: number;
+  exclusiveMinimum?: number | boolean;
+  maxLength?: number;
+  minLength?: number;
+  pattern?: string;
+  maxItems?: number;
+  minItems?: number;
+  uniqueItems?: boolean;
+  maxContains?: number;
+  minContains?: number;
+  maxProperties?: number;
+  minProperties?: number;
+  required?: string[];
+  dependentRequired?: Record<string, string[]>;
+  enum?: Array<string | number | boolean | null>;
+  const?: string | number | boolean | null;
+  id?: string;
+  title?: string;
+  description?: string;
+  default?: unknown;
+  deprecated?: boolean;
+  readOnly?: boolean;
+  writeOnly?: boolean;
+  nullable?: boolean;
+  examples?: unknown[];
+  format?: string;
+  contentMediaType?: string;
+  contentEncoding?: string;
+  contentSchema?: JSONSchema$1;
+  _prefault?: unknown;
+};
+type BaseSchema = JSONSchema$1;
+interface ObjectSchema extends JSONSchema$1 {
+  type: "object";
+}
+interface ArraySchema extends JSONSchema$1 {
+  type: "array";
+}
+interface StringSchema extends JSONSchema$1 {
+  type: "string";
+}
+interface NumberSchema extends JSONSchema$1 {
+  type: "number";
+}
+interface IntegerSchema extends JSONSchema$1 {
+  type: "integer";
+}
+interface BooleanSchema extends JSONSchema$1 {
+  type: "boolean";
+}
+interface NullSchema extends JSONSchema$1 {
+  type: "null";
+}
+//#endregion
+//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/core/standard-schema.d.cts
+/** The Standard interface. */
+interface StandardTypedV1$1<Input = unknown, Output = Input> {
+  /** The Standard properties. */
+  readonly "~standard": StandardTypedV1$1.Props<Input, Output>;
+}
+declare namespace StandardTypedV1$1 {
+  /** The Standard properties interface. */
+  interface Props<Input = unknown, Output = Input> {
+    /** The version number of the standard. */
+    readonly version: 1;
+    /** The vendor name of the schema library. */
+    readonly vendor: string;
+    /** Inferred types associated with the schema. */
+    readonly types?: Types<Input, Output> | undefined;
+  }
+  /** The Standard types interface. */
+  interface Types<Input = unknown, Output = Input> {
+    /** The input type of the schema. */
+    readonly input: Input;
+    /** The output type of the schema. */
+    readonly output: Output;
+  }
+  /** Infers the input type of a Standard. */
+  type InferInput<Schema extends StandardTypedV1$1> = NonNullable<Schema["~standard"]["types"]>["input"];
+  /** Infers the output type of a Standard. */
+  type InferOutput<Schema extends StandardTypedV1$1> = NonNullable<Schema["~standard"]["types"]>["output"];
+}
+/** The Standard Schema interface. */
+interface StandardSchemaV1$1<Input = unknown, Output = Input> {
+  /** The Standard Schema properties. */
+  readonly "~standard": StandardSchemaV1$1.Props<Input, Output>;
+}
+declare namespace StandardSchemaV1$1 {
+  /** The Standard Schema properties interface. */
+  interface Props<Input = unknown, Output = Input> extends StandardTypedV1$1.Props<Input, Output> {
+    /** Validates unknown input values. */
+    readonly validate: (value: unknown, options?: StandardSchemaV1$1.Options | undefined) => Result<Output> | Promise<Result<Output>>;
+  }
+  /** The result interface of the validate function. */
+  type Result<Output> = SuccessResult<Output> | FailureResult;
+  /** The result interface if validation succeeds. */
+  interface SuccessResult<Output> {
+    /** The typed output value. */
+    readonly value: Output;
+    /** The absence of issues indicates success. */
+    readonly issues?: undefined;
+  }
+  interface Options {
+    /** Implicit support for additional vendor-specific parameters, if needed. */
+    readonly libraryOptions?: Record<string, unknown> | undefined;
+  }
+  /** The result interface if validation fails. */
+  interface FailureResult {
+    /** The issues of failed validation. */
+    readonly issues: ReadonlyArray<Issue>;
+  }
+  /** The issue interface of the failure output. */
+  interface Issue {
+    /** The error message of the issue. */
+    readonly message: string;
+    /** The path of the issue, if any. */
+    readonly path?: ReadonlyArray<PropertyKey | PathSegment> | undefined;
+  }
+  /** The path segment interface of the issue. */
+  interface PathSegment {
+    /** The key representing a path segment. */
+    readonly key: PropertyKey;
+  }
+  /** The Standard types interface. */
+  interface Types<Input = unknown, Output = Input> extends StandardTypedV1$1.Types<Input, Output> {}
+  /** Infers the input type of a Standard. */
+  type InferInput<Schema extends StandardTypedV1$1> = StandardTypedV1$1.InferInput<Schema>;
+  /** Infers the output type of a Standard. */
+  type InferOutput<Schema extends StandardTypedV1$1> = StandardTypedV1$1.InferOutput<Schema>;
+}
+/** The Standard JSON Schema interface. */
+interface StandardJSONSchemaV1$1<Input = unknown, Output = Input> {
+  /** The Standard JSON Schema properties. */
+  readonly "~standard": StandardJSONSchemaV1$1.Props<Input, Output>;
+}
+declare namespace StandardJSONSchemaV1$1 {
+  /** The Standard JSON Schema properties interface. */
+  interface Props<Input = unknown, Output = Input> extends StandardTypedV1$1.Props<Input, Output> {
+    /** Methods for generating the input/output JSON Schema. */
+    readonly jsonSchema: Converter;
+  }
+  /** The Standard JSON Schema converter interface. */
+  interface Converter {
+    /** Converts the input type to JSON Schema. May throw if conversion is not supported. */
+    readonly input: (options: StandardJSONSchemaV1$1.Options) => Record<string, unknown>;
+    /** Converts the output type to JSON Schema. May throw if conversion is not supported. */
+    readonly output: (options: StandardJSONSchemaV1$1.Options) => Record<string, unknown>;
+  }
+  /** The target version of the generated JSON Schema.
+   *
+   * It is *strongly recommended* that implementers support `"draft-2020-12"` and `"draft-07"`, as they are both in wide use.
+   *
+   * The `"openapi-3.0"` target is intended as a standardized specifier for OpenAPI 3.0 which is a superset of JSON Schema `"draft-04"`.
+   *
+   * All other targets can be implemented on a best-effort basis. Libraries should throw if they don't support a specified target.
    */
   type Target = "draft-2020-12" | "draft-07" | "openapi-3.0" | ({} & string);
   /** The options for the input/output methods. */
@@ -4960,416 +3865,2743 @@ interface _ZodDate<T extends $ZodDateInternals = $ZodDateInternals> extends _Zod
   /** @deprecated Not recommended. */
   maxDate: Date | null;
 }
-interface ZodDate extends _ZodDate<$ZodDateInternals<Date>> {}
-declare const ZodDate: $constructor<ZodDate>;
-declare function date$2(params?: string | $ZodDateParams): ZodDate;
-interface ZodArray<T extends SomeType = $ZodType> extends _ZodType<$ZodArrayInternals<T>>, $ZodArray<T> {
-  element: T;
-  min(minLength: number, params?: string | $ZodCheckMinLengthParams): this;
-  nonempty(params?: string | $ZodCheckMinLengthParams): this;
-  max(maxLength: number, params?: string | $ZodCheckMaxLengthParams): this;
-  length(len: number, params?: string | $ZodCheckLengthEqualsParams): this;
-  unwrap(): T;
+interface ZodDate extends _ZodDate<$ZodDateInternals<Date>> {}
+declare const ZodDate: $constructor<ZodDate>;
+declare function date$2(params?: string | $ZodDateParams): ZodDate;
+interface ZodArray<T extends SomeType = $ZodType> extends _ZodType<$ZodArrayInternals<T>>, $ZodArray<T> {
+  element: T;
+  min(minLength: number, params?: string | $ZodCheckMinLengthParams): this;
+  nonempty(params?: string | $ZodCheckMinLengthParams): this;
+  max(maxLength: number, params?: string | $ZodCheckMaxLengthParams): this;
+  length(len: number, params?: string | $ZodCheckLengthEqualsParams): this;
+  unwrap(): T;
+  "~standard": ZodStandardSchemaWithJSON<this>;
+}
+declare const ZodArray: $constructor<ZodArray>;
+declare function array<T extends SomeType>(element: T, params?: string | $ZodArrayParams): ZodArray<T>;
+declare function keyof<T extends ZodObject>(schema: T): ZodEnum<KeysEnum<T["_zod"]["output"]>>;
+type SafeExtendShape<Base extends $ZodShape, Ext extends $ZodLooseShape> = { [K in keyof Ext]: K extends keyof Base ? output$1<Ext[K]> extends output$1<Base[K]> ? input$1<Ext[K]> extends input$1<Base[K]> ? Ext[K] : never : never : Ext[K]; };
+interface ZodObject<
+/** @ts-ignore Cast variance */
+out Shape extends $ZodShape = $ZodLooseShape, out Config extends $ZodObjectConfig = $strip> extends _ZodType<$ZodObjectInternals<Shape, Config>>, $ZodObject<Shape, Config> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  shape: Shape;
+  keyof(): ZodEnum<ToEnum<keyof Shape & string>>;
+  /** Define a schema to validate all unrecognized keys. This overrides the existing strict/loose behavior. */
+  catchall<T extends SomeType>(schema: T): ZodObject<Shape, $catchall<T>>;
+  /** @deprecated Use `z.looseObject()` or `.loose()` instead. */
+  passthrough(): ZodObject<Shape, $loose>;
+  /** Consider `z.looseObject(A.shape)` instead */
+  loose(): ZodObject<Shape, $loose>;
+  /** Consider `z.strictObject(A.shape)` instead */
+  strict(): ZodObject<Shape, $strict>;
+  /** This is the default behavior. This method call is likely unnecessary. */
+  strip(): ZodObject<Shape, $strip>;
+  extend<U extends $ZodLooseShape>(shape: U): ZodObject<Extend<Shape, Writeable<U>>, Config>;
+  safeExtend<U extends $ZodLooseShape>(shape: SafeExtendShape<Shape, U> & Partial<Record<keyof Shape, SomeType>>): ZodObject<Extend<Shape, Writeable<U>>, Config>;
+  /**
+   * @deprecated Use [`A.extend(B.shape)`](https://zod.dev/api?id=extend) instead.
+   */
+  merge<U extends ZodObject>(other: U): ZodObject<Extend<Shape, U["shape"]>, U["_zod"]["config"]>;
+  pick<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<Flatten$1<Pick<Shape, Extract<keyof Shape, keyof M>>>, Config>;
+  omit<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<Flatten$1<Omit<Shape, Extract<keyof Shape, keyof M>>>, Config>;
+  partial(): ZodObject<{ -readonly [k in keyof Shape]: ZodOptional<Shape[k]>; }, Config>;
+  partial<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodOptional<Shape[k]> : Shape[k]; }, Config>;
+  exactPartial(): ZodObject<{ -readonly [k in keyof Shape]: ZodExactOptional<Shape[k]>; }, Config>;
+  exactPartial<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodExactOptional<Shape[k]> : Shape[k]; }, Config>;
+  required(): ZodObject<{ -readonly [k in keyof Shape]: ZodNonOptional<Shape[k]>; }, Config>;
+  required<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodNonOptional<Shape[k]> : Shape[k]; }, Config>;
+}
+declare const ZodObject: $constructor<ZodObject>;
+declare function object<T extends $ZodLooseShape = Partial<Record<never, SomeType>>>(shape?: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $strip>;
+declare function strictObject<T extends $ZodLooseShape>(shape: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $strict>;
+declare function looseObject<T extends $ZodLooseShape>(shape: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $loose>;
+interface ZodUnion<T extends readonly SomeType[] = readonly $ZodType[]> extends _ZodType<$ZodUnionInternals<T>>, $ZodUnion<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  options: T;
+}
+declare const ZodUnion: $constructor<ZodUnion>;
+declare function union<const T extends readonly SomeType[]>(options: T, params?: string | $ZodUnionParams): ZodUnion<T>;
+interface ZodXor<T extends readonly SomeType[] = readonly $ZodType[]> extends _ZodType<$ZodXorInternals<T>>, $ZodXor<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  options: T;
+}
+declare const ZodXor: $constructor<ZodXor>;
+/** Creates an exclusive union (XOR) where exactly one option must match.
+ * Unlike regular unions that succeed when any option matches, xor fails if
+ * zero or more than one option matches the input. */
+declare function xor<const T extends readonly SomeType[]>(options: T, params?: string | $ZodXorParams): ZodXor<T>;
+interface ZodDiscriminatedUnion<Options extends readonly SomeType[] = readonly $ZodType[], Disc extends string = string> extends ZodUnion<Options>, $ZodDiscriminatedUnion<Options, Disc> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  _zod: $ZodDiscriminatedUnionInternals<Options, Disc>;
+  def: $ZodDiscriminatedUnionDef<Options, Disc>;
+}
+declare const ZodDiscriminatedUnion: $constructor<ZodDiscriminatedUnion>;
+declare function discriminatedUnion<Types extends readonly [$ZodTypeDiscriminable, ...$ZodTypeDiscriminable[]], Disc extends string>(discriminator: Disc, options: Types, params?: string | $ZodDiscriminatedUnionParams): ZodDiscriminatedUnion<Types, Disc>;
+interface ZodIntersection<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends _ZodType<$ZodIntersectionInternals<A, B>>, $ZodIntersection<A, B> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+}
+declare const ZodIntersection: $constructor<ZodIntersection>;
+declare function intersection<T extends SomeType, U extends SomeType>(left: T, right: U): ZodIntersection<T, U>;
+interface ZodTuple<T extends TupleItems = readonly $ZodType[], Rest extends SomeType | null = $ZodType | null> extends _ZodType<$ZodTupleInternals<T, Rest>>, $ZodTuple<T, Rest> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  rest<Rest extends SomeType = $ZodType>(rest: Rest): ZodTuple<T, Rest>;
+  partial(): ZodTuple<{ -readonly [k in keyof T]: ZodOptional<T[k]>; }, Rest>;
+}
+declare const ZodTuple: $constructor<ZodTuple>;
+declare function tuple<T extends readonly [SomeType, ...SomeType[]]>(items: T, params?: string | $ZodTupleParams): ZodTuple<T, null>;
+declare function tuple<T extends readonly [SomeType, ...SomeType[]], Rest extends SomeType>(items: T, rest: Rest, params?: string | $ZodTupleParams): ZodTuple<T, Rest>;
+declare function tuple(items: [], params?: string | $ZodTupleParams): ZodTuple<[], null>;
+interface ZodRecord<Key extends $ZodRecordKey = $ZodRecordKey, Value extends SomeType = $ZodType> extends _ZodType<$ZodRecordInternals<Key, Value>>, $ZodRecord<Key, Value> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  keyType: Key;
+  valueType: Value;
+}
+declare const ZodRecord: $constructor<ZodRecord>;
+declare function record<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key, Value>;
+declare function partialRecord<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key & $partial, Value>;
+declare function looseRecord<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key, Value>;
+interface ZodMap<Key extends SomeType = $ZodType, Value extends SomeType = $ZodType> extends _ZodType<$ZodMapInternals<Key, Value>>, $ZodMap<Key, Value> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  keyType: Key;
+  valueType: Value;
+  min(minSize: number, params?: string | $ZodCheckMinSizeParams): this;
+  nonempty(params?: string | $ZodCheckMinSizeParams): this;
+  max(maxSize: number, params?: string | $ZodCheckMaxSizeParams): this;
+  size(size: number, params?: string | $ZodCheckSizeEqualsParams): this;
+}
+declare const ZodMap: $constructor<ZodMap>;
+declare function map<Key extends SomeType, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodMapParams): ZodMap<Key, Value>;
+interface ZodSet<T extends SomeType = $ZodType> extends _ZodType<$ZodSetInternals<T>>, $ZodSet<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  min(minSize: number, params?: string | $ZodCheckMinSizeParams): this;
+  nonempty(params?: string | $ZodCheckMinSizeParams): this;
+  max(maxSize: number, params?: string | $ZodCheckMaxSizeParams): this;
+  size(size: number, params?: string | $ZodCheckSizeEqualsParams): this;
+}
+declare const ZodSet: $constructor<ZodSet>;
+declare function set<Value extends SomeType>(valueType: Value, params?: string | $ZodSetParams): ZodSet<Value>;
+interface ZodEnum<
+/** @ts-ignore Cast variance */
+out T extends EnumLike = EnumLike> extends _ZodType<$ZodEnumInternals<T>>, $ZodEnum<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  enum: T;
+  options: Array<T[keyof T]>;
+  extract<const U extends readonly (keyof T)[]>(values: U, params?: string | $ZodEnumParams): ZodEnum<Flatten$1<Pick<T, U[number]>>>;
+  exclude<const U extends readonly (keyof T)[]>(values: U, params?: string | $ZodEnumParams): ZodEnum<Flatten$1<Omit<T, U[number]>>>;
+}
+declare const ZodEnum: $constructor<ZodEnum>;
+declare function _enum<const T extends readonly string[]>(values: T, params?: string | $ZodEnumParams): ZodEnum<ToEnum<T[number]>>;
+declare function _enum<const T extends EnumLike>(entries: T, params?: string | $ZodEnumParams): ZodEnum<T>;
+/** @deprecated This API has been merged into `z.enum()`. Use `z.enum()` instead.
+ *
+ * ```ts
+ * enum Colors { red, green, blue }
+ * z.enum(Colors);
+ * ```
+ */
+declare function nativeEnum<T extends EnumLike>(entries: T, params?: string | $ZodEnumParams): ZodEnum<T>;
+interface ZodLiteral<T extends Literal = Literal> extends _ZodType<$ZodLiteralInternals<T>>, $ZodLiteral<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  values: Set<T>;
+  /** @legacy Use `.values` instead. Accessing this property will throw an error if the literal accepts multiple values. */
+  value: T;
+}
+declare const ZodLiteral: $constructor<ZodLiteral>;
+declare function literal<const T extends ReadonlyArray<Literal>>(value: T, params?: string | $ZodLiteralParams): ZodLiteral<T[number]>;
+declare function literal<const T extends Literal>(value: T, params?: string | $ZodLiteralParams): ZodLiteral<T>;
+interface ZodFile extends _ZodType<$ZodFileInternals>, $ZodFile {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  min(size: number, params?: string | $ZodCheckMinSizeParams): this;
+  max(size: number, params?: string | $ZodCheckMaxSizeParams): this;
+  mime(types: MimeTypes | Array<MimeTypes>, params?: string | $ZodCheckMimeTypeParams): this;
+}
+declare const ZodFile: $constructor<ZodFile>;
+declare function file(params?: string | $ZodFileParams): ZodFile;
+interface ZodTransform<O = unknown, I = unknown> extends _ZodType<$ZodTransformInternals<O, I>>, $ZodTransform<O, I> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+}
+declare const ZodTransform: $constructor<ZodTransform>;
+declare function transform<I = unknown, O = I>(fn: (input: I, ctx: $RefinementCtx) => O): ZodTransform<Awaited<O>, I>;
+interface ZodOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodOptionalInternals<T>>, $ZodOptional<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodOptional: $constructor<ZodOptional>;
+declare function optional<T extends SomeType>(innerType: T): ZodOptional<T>;
+interface ZodExactOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodExactOptionalInternals<T>>, $ZodExactOptional<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodExactOptional: $constructor<ZodExactOptional>;
+declare function exactOptional<T extends SomeType>(innerType: T): ZodExactOptional<T>;
+interface ZodNullable<T extends SomeType = $ZodType> extends _ZodType<$ZodNullableInternals<T>>, $ZodNullable<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodNullable: $constructor<ZodNullable>;
+declare function nullable<T extends SomeType>(innerType: T): ZodNullable<T>;
+declare function nullish<T extends SomeType>(innerType: T): ZodOptional<ZodNullable<T>>;
+interface ZodDefault<T extends SomeType = $ZodType> extends _ZodType<$ZodDefaultInternals<T>>, $ZodDefault<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+  /** @deprecated Use `.unwrap()` instead. */
+  removeDefault(): T;
+}
+declare const ZodDefault: $constructor<ZodDefault>;
+declare function _default<T extends SomeType>(innerType: T, defaultValue: NoUndefined<output$1<T>> | (() => NoUndefined<output$1<T>>)): ZodDefault<T>;
+interface ZodPrefault<T extends SomeType = $ZodType> extends _ZodType<$ZodPrefaultInternals<T>>, $ZodPrefault<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodPrefault: $constructor<ZodPrefault>;
+declare function prefault<T extends SomeType>(innerType: T, defaultValue: input$1<T> | (() => input$1<T>)): ZodPrefault<T>;
+interface ZodNonOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodNonOptionalInternals<T>>, $ZodNonOptional<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodNonOptional: $constructor<ZodNonOptional>;
+declare function nonoptional<T extends SomeType>(innerType: T, params?: string | $ZodNonOptionalParams): ZodNonOptional<T>;
+interface ZodSuccess<T extends SomeType = $ZodType> extends _ZodType<$ZodSuccessInternals<T>>, $ZodSuccess<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+}
+declare const ZodSuccess: $constructor<ZodSuccess>;
+declare function success<T extends SomeType>(innerType: T): ZodSuccess<T>;
+interface ZodCatch<T extends SomeType = $ZodType> extends _ZodType<$ZodCatchInternals<T>>, $ZodCatch<T> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  unwrap(): T;
+  /** @deprecated Use `.unwrap()` instead. */
+  removeCatch(): T;
+}
+declare const ZodCatch: $constructor<ZodCatch>;
+declare function _catch<T extends SomeType>(innerType: T, catchValue: output$1<T> | ((ctx: $ZodCatchCtx) => output$1<T>)): ZodCatch<T>;
+interface ZodNaN extends _ZodType<$ZodNaNInternals>, $ZodNaN {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+}
+declare const ZodNaN: $constructor<ZodNaN>;
+declare function nan(params?: string | $ZodNaNParams): ZodNaN;
+interface ZodPipe<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends _ZodType<$ZodPipeInternals<A, B>>, $ZodPipe<A, B> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  in: A;
+  out: B;
+}
+declare const ZodPipe: $constructor<ZodPipe>;
+declare function pipe<const A extends SomeType, B extends $ZodType<unknown, output$1<A>> = $ZodType<unknown, output$1<A>>>(in_: A, out: B | $ZodType<unknown, output$1<A>>): ZodPipe<A, B>;
+interface ZodCodec<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends ZodPipe<A, B>, $ZodCodec<A, B> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  _zod: $ZodCodecInternals<A, B>;
+  def: $ZodCodecDef<A, B>;
+}
+declare const ZodCodec: $constructor<ZodCodec>;
+declare function codec<const A extends SomeType, B extends SomeType = $ZodType>(in_: A, out: B, params: {
+  decode: (value: output$1<A>, payload: ParsePayload<output$1<A>>) => MaybeAsync<input$1<B>>;
+  encode: (value: input$1<B>, payload: ParsePayload<input$1<B>>) => MaybeAsync<output$1<A>>;
+}): ZodCodec<A, B>;
+declare function invertCodec<A extends SomeType, B extends SomeType>(codec: ZodCodec<A, B>): ZodCodec<B, A>;
+interface ZodPreprocess<B extends SomeType = $ZodType, I = unknown> extends ZodPipe<$ZodTransform<unknown, I>, B>, $ZodPreprocess<B, I> {
   "~standard": ZodStandardSchemaWithJSON<this>;
+  _zod: $ZodPreprocessInternals<B, I>;
+  def: $ZodPreprocessDef<B, I>;
 }
-declare const ZodArray: $constructor<ZodArray>;
-declare function array<T extends SomeType>(element: T, params?: string | $ZodArrayParams): ZodArray<T>;
-declare function keyof<T extends ZodObject>(schema: T): ZodEnum<KeysEnum<T["_zod"]["output"]>>;
-type SafeExtendShape<Base extends $ZodShape, Ext extends $ZodLooseShape> = { [K in keyof Ext]: K extends keyof Base ? output$1<Ext[K]> extends output$1<Base[K]> ? input$1<Ext[K]> extends input$1<Base[K]> ? Ext[K] : never : never : Ext[K]; };
-interface ZodObject<
-/** @ts-ignore Cast variance */
-out Shape extends $ZodShape = $ZodLooseShape, out Config extends $ZodObjectConfig = $strip> extends _ZodType<$ZodObjectInternals<Shape, Config>>, $ZodObject<Shape, Config> {
+declare const ZodPreprocess: $constructor<ZodPreprocess>;
+interface ZodReadonly<T extends SomeType = $ZodType> extends _ZodType<$ZodReadonlyInternals<T>>, $ZodReadonly<T> {
   "~standard": ZodStandardSchemaWithJSON<this>;
-  shape: Shape;
-  keyof(): ZodEnum<ToEnum<keyof Shape & string>>;
-  /** Define a schema to validate all unrecognized keys. This overrides the existing strict/loose behavior. */
-  catchall<T extends SomeType>(schema: T): ZodObject<Shape, $catchall<T>>;
-  /** @deprecated Use `z.looseObject()` or `.loose()` instead. */
-  passthrough(): ZodObject<Shape, $loose>;
-  /** Consider `z.looseObject(A.shape)` instead */
-  loose(): ZodObject<Shape, $loose>;
-  /** Consider `z.strictObject(A.shape)` instead */
-  strict(): ZodObject<Shape, $strict>;
-  /** This is the default behavior. This method call is likely unnecessary. */
-  strip(): ZodObject<Shape, $strip>;
-  extend<U extends $ZodLooseShape>(shape: U): ZodObject<Extend<Shape, Writeable<U>>, Config>;
-  safeExtend<U extends $ZodLooseShape>(shape: SafeExtendShape<Shape, U> & Partial<Record<keyof Shape, SomeType>>): ZodObject<Extend<Shape, Writeable<U>>, Config>;
-  /**
-   * @deprecated Use [`A.extend(B.shape)`](https://zod.dev/api?id=extend) instead.
-   */
-  merge<U extends ZodObject>(other: U): ZodObject<Extend<Shape, U["shape"]>, U["_zod"]["config"]>;
-  pick<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<Flatten$1<Pick<Shape, Extract<keyof Shape, keyof M>>>, Config>;
-  omit<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<Flatten$1<Omit<Shape, Extract<keyof Shape, keyof M>>>, Config>;
-  partial(): ZodObject<{ -readonly [k in keyof Shape]: ZodOptional<Shape[k]>; }, Config>;
-  partial<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodOptional<Shape[k]> : Shape[k]; }, Config>;
-  exactPartial(): ZodObject<{ -readonly [k in keyof Shape]: ZodExactOptional<Shape[k]>; }, Config>;
-  exactPartial<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodExactOptional<Shape[k]> : Shape[k]; }, Config>;
-  required(): ZodObject<{ -readonly [k in keyof Shape]: ZodNonOptional<Shape[k]>; }, Config>;
-  required<M extends Mask<keyof Shape>>(mask: M & Record<Exclude<keyof M, keyof Shape>, never>): ZodObject<{ -readonly [k in keyof Shape]: k extends keyof M ? ZodNonOptional<Shape[k]> : Shape[k]; }, Config>;
+  unwrap(): T;
 }
-declare const ZodObject: $constructor<ZodObject>;
-declare function object<T extends $ZodLooseShape = Partial<Record<never, SomeType>>>(shape?: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $strip>;
-declare function strictObject<T extends $ZodLooseShape>(shape: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $strict>;
-declare function looseObject<T extends $ZodLooseShape>(shape: T, params?: string | $ZodObjectParams): ZodObject<Writeable<T>, $loose>;
-interface ZodUnion<T extends readonly SomeType[] = readonly $ZodType[]> extends _ZodType<$ZodUnionInternals<T>>, $ZodUnion<T> {
+declare const ZodReadonly: $constructor<ZodReadonly>;
+declare function readonly<T extends SomeType>(innerType: T): ZodReadonly<T>;
+interface ZodTemplateLiteral<Template extends string = string> extends _ZodType<$ZodTemplateLiteralInternals<Template>>, $ZodTemplateLiteral<Template> {
   "~standard": ZodStandardSchemaWithJSON<this>;
-  options: T;
 }
-declare const ZodUnion: $constructor<ZodUnion>;
-declare function union<const T extends readonly SomeType[]>(options: T, params?: string | $ZodUnionParams): ZodUnion<T>;
-interface ZodXor<T extends readonly SomeType[] = readonly $ZodType[]> extends _ZodType<$ZodXorInternals<T>>, $ZodXor<T> {
+declare const ZodTemplateLiteral: $constructor<ZodTemplateLiteral>;
+declare function templateLiteral<const Parts extends $ZodTemplateLiteralPart[]>(parts: Parts, params?: string | $ZodTemplateLiteralParams): ZodTemplateLiteral<$PartsToTemplateLiteral<Parts>>;
+interface ZodLazy<T extends SomeType = $ZodType> extends _ZodType<$ZodLazyInternals<T>>, $ZodLazy<T> {
   "~standard": ZodStandardSchemaWithJSON<this>;
-  options: T;
+  unwrap(): T;
 }
-declare const ZodXor: $constructor<ZodXor>;
-/** Creates an exclusive union (XOR) where exactly one option must match.
- * Unlike regular unions that succeed when any option matches, xor fails if
- * zero or more than one option matches the input. */
-declare function xor<const T extends readonly SomeType[]>(options: T, params?: string | $ZodXorParams): ZodXor<T>;
-interface ZodDiscriminatedUnion<Options extends readonly SomeType[] = readonly $ZodType[], Disc extends string = string> extends ZodUnion<Options>, $ZodDiscriminatedUnion<Options, Disc> {
+declare const ZodLazy: $constructor<ZodLazy>;
+declare function lazy<T extends SomeType>(getter: () => T): ZodLazy<T>;
+interface ZodPromise<T extends SomeType = $ZodType> extends _ZodType<$ZodPromiseInternals<T>>, $ZodPromise<T> {
   "~standard": ZodStandardSchemaWithJSON<this>;
-  _zod: $ZodDiscriminatedUnionInternals<Options, Disc>;
-  def: $ZodDiscriminatedUnionDef<Options, Disc>;
+  unwrap(): T;
 }
-declare const ZodDiscriminatedUnion: $constructor<ZodDiscriminatedUnion>;
-declare function discriminatedUnion<Types extends readonly [$ZodTypeDiscriminable, ...$ZodTypeDiscriminable[]], Disc extends string>(discriminator: Disc, options: Types, params?: string | $ZodDiscriminatedUnionParams): ZodDiscriminatedUnion<Types, Disc>;
-interface ZodIntersection<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends _ZodType<$ZodIntersectionInternals<A, B>>, $ZodIntersection<A, B> {
+declare const ZodPromise: $constructor<ZodPromise>;
+declare function promise<T extends SomeType>(innerType: T): ZodPromise<T>;
+interface ZodFunction<Args extends $ZodFunctionIn = $ZodFunctionIn, Returns extends $ZodFunctionOut = $ZodFunctionOut> extends _ZodType<$ZodFunctionInternals<Args, Returns>>, $ZodFunction<Args, Returns> {
+  "~standard": ZodStandardSchemaWithJSON<this>;
+  _def: $ZodFunctionDef<Args, Returns>;
+  _input: $InferInnerFunctionType<Args, Returns>;
+  _output: $InferOuterFunctionType<Args, Returns>;
+  input<const Items extends TupleItems, const Rest extends $ZodFunctionOut = $ZodFunctionOut>(args: Items, rest?: Rest): ZodFunction<$ZodTuple<Items, Rest>, Returns>;
+  input<NewArgs extends $ZodFunctionIn>(args: NewArgs): ZodFunction<NewArgs, Returns>;
+  input(...args: any[]): ZodFunction<any, Returns>;
+  output<NewReturns extends $ZodType>(output: NewReturns): ZodFunction<Args, NewReturns>;
+}
+declare const ZodFunction: $constructor<ZodFunction>;
+declare function _function(): ZodFunction;
+declare function _function<const In extends ReadonlyArray<$ZodType>>(params: {
+  input: In;
+}): ZodFunction<ZodTuple<In, null>, $ZodFunctionOut>;
+declare function _function<const In extends ReadonlyArray<$ZodType>, const Out extends $ZodFunctionOut = $ZodFunctionOut>(params: {
+  input: In;
+  output: Out;
+}): ZodFunction<ZodTuple<In, null>, Out>;
+declare function _function<const In extends $ZodFunctionIn = $ZodFunctionIn>(params: {
+  input: In;
+}): ZodFunction<In, $ZodFunctionOut>;
+declare function _function<const Out extends $ZodFunctionOut = $ZodFunctionOut>(params: {
+  output: Out;
+}): ZodFunction<$ZodFunctionIn, Out>;
+declare function _function<In extends $ZodFunctionIn = $ZodFunctionIn, Out extends $ZodType = $ZodType>(params?: {
+  input: In;
+  output: Out;
+}): ZodFunction<In, Out>;
+interface ZodCustom<O = unknown, I = unknown> extends _ZodType<$ZodCustomInternals<O, I>>, $ZodCustom<O, I> {
   "~standard": ZodStandardSchemaWithJSON<this>;
 }
-declare const ZodIntersection: $constructor<ZodIntersection>;
-declare function intersection<T extends SomeType, U extends SomeType>(left: T, right: U): ZodIntersection<T, U>;
-interface ZodTuple<T extends TupleItems = readonly $ZodType[], Rest extends SomeType | null = $ZodType | null> extends _ZodType<$ZodTupleInternals<T, Rest>>, $ZodTuple<T, Rest> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  rest<Rest extends SomeType = $ZodType>(rest: Rest): ZodTuple<T, Rest>;
-  partial(): ZodTuple<{ -readonly [k in keyof T]: ZodOptional<T[k]>; }, Rest>;
+declare const ZodCustom: $constructor<ZodCustom>;
+declare function check<O = unknown>(fn: CheckFn<O>): $ZodCheck<O>;
+declare function custom<O>(fn?: (data: unknown) => unknown, _params?: string | $ZodCustomParams | undefined): ZodCustom<O, O>;
+declare function refine<T>(fn: (arg: NoInfer<T>) => MaybeAsync<unknown>, _params?: string | $ZodCustomParams): $ZodCheck<T>;
+declare function superRefine<T>(fn: (arg: T, payload: $RefinementCtx<T>) => void | Promise<void>, params?: $ZodSuperRefineParams): $ZodCheck<T>;
+declare const describe: typeof describe$1;
+declare const meta: typeof meta$1;
+type ZodInstanceOfParams = Params<ZodCustom, $ZodIssueCustom, "type" | "check" | "checks" | "fn" | "abort" | "error" | "params" | "path">;
+interface ZodInstanceOf<T = unknown> extends ZodCustom<T, T> {
+  properties<Shape extends { [k in keyof T as T[k] extends Function ? never : k]?: $ZodType<unknown, T[k]>; }>(shape: Shape, params?: string | $ZodCheckPropertiesParams): ZodInstanceOf<T & $InferObjectInput<Shape, {}>>;
+}
+declare const ZodInstanceOf: $constructor<ZodInstanceOf>;
+declare function _instanceof<T extends typeof Class>(cls: T, params?: ZodInstanceOfParams): ZodInstanceOf<InstanceType<T>>;
+declare const stringbool: (_params?: string | $ZodStringBoolParams) => ZodCodec<ZodString, ZodBoolean>;
+type _ZodJSONSchema = ZodUnion<[ZodString, ZodNumber, ZodBoolean, ZodNull, ZodArray<ZodJSONSchema>, ZodRecord<ZodString, ZodJSONSchema>]>;
+type _ZodJSONSchemaInternals = _ZodJSONSchema["_zod"];
+interface ZodJSONSchemaInternals extends _ZodJSONSchemaInternals {
+  output: JSONType;
+  input: JSONType;
+}
+interface ZodJSONSchema extends _ZodJSONSchema {
+  _zod: ZodJSONSchemaInternals;
+}
+declare function json(params?: string | $ZodCustomParams): ZodJSONSchema;
+declare function preprocess<A, U extends SomeType, B = unknown>(fn: (arg: B, ctx: $RefinementCtx) => A, schema: U): ZodPreprocess<U, B>;
+//#endregion
+//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/compat.d.cts
+/** @deprecated Use `z.output<T>` instead. */
+type TypeOf<T> = output$1<T>;
+/** @deprecated Use `z.output<T>` instead. */
+type Infer$1<T> = output$1<T>;
+/** @deprecated Use `z.core.$ZodTypes` instead */
+type ZodFirstPartySchemaTypes = $ZodTypes;
+/** @deprecated Use the raw string literal codes instead, e.g. "invalid_type". */
+declare const ZodIssueCode: {
+  readonly invalid_type: "invalid_type";
+  readonly too_big: "too_big";
+  readonly too_small: "too_small";
+  readonly invalid_format: "invalid_format";
+  readonly not_multiple_of: "not_multiple_of";
+  readonly unrecognized_keys: "unrecognized_keys";
+  readonly invalid_union: "invalid_union";
+  readonly invalid_key: "invalid_key";
+  readonly invalid_element: "invalid_element";
+  readonly invalid_value: "invalid_value";
+  readonly custom: "custom";
+};
+/** @deprecated Use `z.core.$ZodFlattenedError<z.output<T>>` instead; it takes an inferred type, not a schema. */
+type inferFlattenedErrors<T extends $ZodType, U = string> = $ZodFlattenedError<output$1<T>, U>;
+/** @deprecated Use `z.core.$ZodFormattedError<z.output<T>>` instead; it takes an inferred type, not a schema. */
+type inferFormattedError<T extends $ZodType<any, any>, U = string> = $ZodFormattedError<output$1<T>, U>;
+/** Use `z.$brand` instead */
+type BRAND<T extends string | number | symbol = string | number | symbol> = {
+  [$brand]: { [k in T]: true; };
+};
+/** @deprecated Use `z.config(params)` instead. */
+declare function setErrorMap(map: $ZodErrorMap): void;
+/** @deprecated Use `z.config()` instead. */
+declare function getErrorMap(): $ZodErrorMap<$ZodIssue> | undefined;
+/** @deprecated Use z.ZodType (without generics) instead. */
+type ZodTypeAny<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
+/** @deprecated Use `z.ZodType` */
+type ZodSchema<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
+/** @deprecated Use `z.ZodType` */
+type Schema<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
+/** Included for Zod 3 compatibility */
+type ZodRawShape$1 = $ZodShape;
+/** @deprecated Do not use. Stub definition, only included for zod-to-json-schema compatibility. */
+declare enum ZodFirstPartyTypeKind {}
+//#endregion
+//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/from-json-schema.d.cts
+type JSONSchemaVersion = "draft-2020-12" | "draft-7" | "draft-4" | "openapi-3.0";
+interface FromJSONSchemaParams {
+  defaultTarget?: JSONSchemaVersion;
+  registry?: $ZodRegistry<any>;
+}
+/**
+ * Converts a JSON Schema to a Zod schema. This function should be considered semi-experimental. It's behavior is liable to change. */
+declare function fromJSONSchema(schema: JSONSchema$1 | boolean, params?: FromJSONSchemaParams): ZodType;
+//#endregion
+//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/deep-partial.d.cts
+/** Distributes `.partial()` through every object in a schema type, preserving the wrappers around them. */
+type DeepPartial<T extends SomeType> = T extends ZodObject<infer Shape, infer Config> ? ZodObject<{ -readonly [K in keyof Shape]: ZodOptional<DeepPartial<Shape[K]>>; }, Config> : T extends ZodDiscriminatedUnion<infer Options, any> ? ZodUnion<{ -readonly [I in keyof Options]: Options[I] extends SomeType ? DeepPartial<Options[I]> : Options[I]; }> : T extends ZodUnion<infer Options> ? ZodUnion<{ -readonly [I in keyof Options]: Options[I] extends SomeType ? DeepPartial<Options[I]> : Options[I]; }> : T extends ZodArray<infer El> ? ZodArray<DeepPartial<El>> : T extends ZodTuple<infer Items, infer Rest> ? ZodTuple<{ -readonly [K in keyof Items]: Items[K] extends SomeType ? DeepPartial<Items[K]> : Items[K]; }, Rest extends SomeType ? DeepPartial<Rest> : Rest> : T extends ZodIntersection<infer A, infer B> ? ZodIntersection<DeepPartial<A>, DeepPartial<B>> : T extends ZodRecord<infer K, infer V> ? ZodRecord<K, DeepPartial<V>> : T extends ZodMap<infer K, infer V> ? ZodMap<K, DeepPartial<V>> : T extends ZodSet<infer El> ? ZodSet<DeepPartial<El>> : T extends ZodOptional<infer Inner> ? ZodOptional<DeepPartial<Inner>> : T extends ZodNullable<infer Inner> ? ZodNullable<DeepPartial<Inner>> : T extends ZodDefault<infer Inner> ? ZodDefault<DeepPartial<Inner>> : T extends ZodPrefault<infer Inner> ? ZodPrefault<DeepPartial<Inner>> : T extends ZodNonOptional<infer Inner> ? ZodNonOptional<DeepPartial<Inner>> : T extends ZodCatch<infer Inner> ? ZodCatch<DeepPartial<Inner>> : T extends ZodReadonly<infer Inner> ? ZodReadonly<DeepPartial<Inner>> : T extends ZodSuccess<infer Inner> ? ZodSuccess<DeepPartial<Inner>> : T extends ZodPromise<infer Inner> ? ZodPromise<DeepPartial<Inner>> : T extends ZodCodec<infer A, infer B> ? ZodCodec<DeepPartial<A>, DeepPartial<B>> : T extends ZodPreprocess<infer B> ? ZodPreprocess<DeepPartial<B>> : T extends ZodPipe<infer A, infer B> ? ZodPipe<DeepPartial<A>, DeepPartial<B>> : T extends ZodLazy<infer Inner> ? ZodLazy<DeepPartial<Inner>> : T;
+/** Returns a copy of the schema with every nested object's properties made optional. */
+declare function deepPartial<T extends SomeType>(schema: T): DeepPartial<T>;
+//#endregion
+//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/in-out.d.cts
+type input<T> = input$1<T>;
+type output<T> = output$1<T>;
+/** Returns a copy of the schema with every pipe replaced by its input side. A codec's checks are dropped: they constrain the decoded value the input side never produces. */
+declare function input<T extends $ZodType>(schema: T): ZodType<input$1<T>, input$1<T>>;
+/** Returns a copy of the schema with every pipe replaced by its output side, carrying over the pipe's own checks. */
+declare function output<T extends $ZodType>(schema: T): ZodType<output$1<T>, output$1<T>>;
+declare namespace iso_d_exports {
+  export { ZodISODate, ZodISODateTime, ZodISODuration, ZodISOTime, date$1 as date, datetime, duration, time };
+}
+declare function datetime(params?: string | $ZodISODateTimeParams): ZodISODateTime;
+declare function date$1(params?: string | $ZodISODateParams): ZodISODate;
+declare function time(params?: string | $ZodISOTimeParams): ZodISOTime;
+declare function duration(params?: string | $ZodISODurationParams): ZodISODuration;
+declare namespace coerce_d_exports {
+  export { ZodCoercedBigInt, ZodCoercedBoolean, ZodCoercedDate, ZodCoercedNumber, ZodCoercedString, bigint, boolean, date, number, string };
+}
+interface ZodCoercedString<T = unknown> extends _ZodString<$ZodStringInternals<T>> {}
+declare function string<T = unknown>(params?: string | $ZodStringParams): ZodCoercedString<T>;
+interface ZodCoercedNumber<T = unknown> extends _ZodNumber<$ZodNumberInternals<T>> {}
+declare function number<T = unknown>(params?: string | $ZodNumberParams): ZodCoercedNumber<T>;
+interface ZodCoercedBoolean<T = unknown> extends _ZodBoolean<$ZodBooleanInternals<T>> {}
+declare function boolean<T = unknown>(params?: string | $ZodBooleanParams): ZodCoercedBoolean<T>;
+interface ZodCoercedBigInt<T = unknown> extends _ZodBigInt<$ZodBigIntInternals<T>> {}
+declare function bigint<T = unknown>(params?: string | $ZodBigIntParams): ZodCoercedBigInt<T>;
+interface ZodCoercedDate<T = unknown> extends _ZodDate<$ZodDateInternals<T>> {}
+declare function date<T = unknown>(params?: string | $ZodDateParams): ZodCoercedDate<T>;
+declare namespace external_d_exports {
+  export { $brand, $input, $output, BRAND, CompileOptions, GlobalMeta, INVALID, Infer$1 as Infer, IssueData, JSONType, NEVER, $RefinementCtx as RefinementCtx, SafeExtendShape, Schema, TimePrecision, TypeOf, ZodAny, ZodArray, ZodBase64, ZodBase64URL, ZodBigInt, ZodBigIntFormat, ZodBoolean, ZodCIDRv4, ZodCIDRv6, ZodCUID, ZodCUID2, ZodCatch, ZodCodec, ZodCoercedBigInt, ZodCoercedBoolean, ZodCoercedDate, ZodCoercedNumber, ZodCoercedString, ZodCompileAsyncError, ZodCompileUnsupportedError, ZodCreditCard, ZodCustom, ZodCustomStringFormat, ZodDate, ZodDefault, ZodDiscriminatedUnion, ZodE164, ZodEmail, ZodEmoji, ZodEnum, ZodError, ZodErrorMap, ZodExactOptional, ZodFile, ZodFirstPartySchemaTypes, ZodFirstPartyTypeKind, ZodFlattenedError, ZodFloat32, ZodFloat64, ZodFormattedError, ZodFunction, ZodGUID, ZodIBAN, ZodIPv4, ZodIPv6, ZodISODate, ZodISODateTime, ZodISODuration, ZodISOTime, ZodInstanceOf, ZodInt, ZodInt32, ZodInt64, ZodIntersection, ZodIssue, ZodIssueCode, ZodJSONSchema, ZodJSONSchemaInternals, ZodJWT, ZodKSUID, ZodLazy, ZodLiteral, ZodMAC, ZodMap, ZodNaN, ZodNanoID, ZodNever, ZodNonOptional, ZodNull, ZodNullable, ZodNumber, ZodNumberFormat, ZodObject, ZodOptional, ZodPipe, ZodPrefault, ZodPreprocess, ZodPromise, ZodRawShape$1 as ZodRawShape, ZodReadonly, ZodRealError, ZodRecord, ZodSafeParseError, ZodSafeParseResult, ZodSafeParseSuccess, ZodSchema, ZodSet, ZodStandardSchemaWithJSON, ZodString, ZodStringFormat, ZodSuccess, ZodSymbol, ZodTemplateLiteral, ZodTransform, ZodTuple, ZodType, ZodTypeAny, ZodUInt32, ZodUInt64, ZodULID, ZodURL, ZodUUID, ZodUndefined, ZodUnion, ZodUnknown, ZodVoid, ZodXID, ZodXor, _ZodBigInt, _ZodBoolean, _ZodDate, _ZodNumber, _ZodString, _ZodType, _default, _function, any, array, base64, base64url, bigint$1 as bigint, boolean$1 as boolean, _catch as catch, check, cidrv4, cidrv6, clone, codec, coerce_d_exports as coerce, compile, config, index_d_exports$1 as core, creditCard, cuid, cuid2, currencyCode, custom, date$2 as date, decode, decodeAsync, deepPartial, describe, discriminatedUnion, e164, email, emoji, encode, encodeAsync, _endsWith as endsWith, _enum as enum, exactOptional, file, flattenError, float32, float64, formatError, fromJSONSchema, _function as function, getDiscriminatedOption, getErrorMap, globalRegistry, _gt as gt, _gte as gte, guid, hash, hex, hostname, httpUrl, iban, _includes as includes, output$1 as infer, inferFlattenedErrors, inferFormattedError, input, _instanceof as instanceof, int, int32, int64, intersection, invertCodec, ipv4, ipv6, iso_d_exports as iso, json, jwt, keyof, ksuid, lazy, _length as length, literal, index_d_exports$2 as locales, looseObject, looseRecord, _lowercase as lowercase, _lt as lt, _lte as lte, mac, map, _maxLength as maxLength, _maxSize as maxSize, memoizer, meta, _mime as mime, _minLength as minLength, _minSize as minSize, _multipleOf as multipleOf, nan, nanoid, nativeEnum, _negative as negative, never, _nonnegative as nonnegative, nonoptional, _nonpositive as nonpositive, _normalize as normalize, _null as null, nullable, nullish, number$1 as number, object, optional, output, _overwrite as overwrite, parse, parseAsync, partialRecord, pipe, _positive as positive, prefault, preprocess, prettifyError, promise, _properties as properties, _property as property, readonly, record, refine, _regex as regex, regexes_d_exports as regexes, registry, safeDecode, safeDecodeAsync, safeEncode, safeEncodeAsync, safeParse, safeParseAsync, set, setErrorMap, _size as size, _slugify as slugify, _startsWith as startsWith, strictObject, string$1 as string, stringFormat, stringbool, success, superRefine, symbol, templateLiteral, toJSONSchema, _toLowerCase as toLowerCase, _toUpperCase as toUpperCase, toZod, transform, treeifyError, _trim as trim, tuple, uint32, uint64, ulid, _undefined as undefined, union, unknown, _uppercase as uppercase, url, util_d_exports as util, uuid, uuidv4, uuidv6, uuidv7, validate, validateAsync, _void as void, withParser, xid, xor };
+}
+//#endregion
+//#region ../core/dist/change-flow-i6vGyxUm.d.mts
+interface RegisteredServer {
+  client: string;
+  path: string;
+  name: string;
+  command: string;
+  args: string[];
+  /**
+   * The address of a remote server, for an entry that has one instead of a command.
+   *
+   * Read because the official Slack server is exactly such an entry — `https://mcp.slack.com/mcp` — and a scan
+   * that looked only at `command` and `args` could not see the one other Slack server most people will have.
+   */
+  url?: string | undefined;
+  /** The entry's own `type` (`stdio`, `http`, `sse`), when it declares one. */
+  type?: string | undefined;
+  /** The npm package the entry launches, when one can be read from the command line. */
+  packageName?: string | undefined;
+  /**
+   * The entry's own environment, when it declares one.
+   *
+   * Carried because an entry cannot be put back without it: ours sets `AGENT_COMMS_CONFIG_DIR`, and a server
+   * restored without that looks in the wrong directory and reports no mailboxes — a silent wrong answer where the
+   * missing entry it replaced was at least an obvious one.
+   */
+  env?: Record<string, string> | undefined;
+  /**
+   * `project` for an entry Claude Code keeps under `projects`, `user` otherwise.
+   *
+   * Every command this package issues targets user scope. Without knowing the difference, a repair aimed at a
+   * project-scoped entry removes nothing, adds a second entry at user scope, and reports success — leaving the
+   * stale one still in force for that project.
+   */
+  scope?: "user" | "project" | undefined;
+}
+/** The five suite directories a CLI can pin independently. */
+declare const PATH_OPTIONS: readonly [{
+  readonly key: "configDir";
+  readonly option: "config-dir";
+  readonly flag: "--config-dir";
+}, {
+  readonly key: "stateDir";
+  readonly option: "state-dir";
+  readonly flag: "--state-dir";
+}, {
+  readonly key: "dataDir";
+  readonly option: "data-dir";
+  readonly flag: "--data-dir";
+}, {
+  readonly key: "secretsDir";
+  readonly option: "secrets-dir";
+  readonly flag: "--secrets-dir";
+}, {
+  readonly key: "downloadsDir";
+  readonly option: "downloads-dir";
+  readonly flag: "--downloads-dir";
+}];
+type PathName = (typeof PATH_OPTIONS)[number]["key"];
+type PathOverrides = Partial<Record<PathName, string>>;
+interface ResolvedPaths {
+  /** config.json and everything a user edits. */
+  configDir: string;
+  /** Approvals, pending OAuth flows, audit log, rate-cap counters, taint set. */
+  stateDir: string;
+  /** The file secret store: refresh tokens, client secrets, the approval key. */
+  secretsDir: string;
+  /** Managed runtime installs for MCP clients. */
+  dataDir: string;
+  /**
+   * Default root for exports and for the files Resend's received mail carries. A Gmail attachment or a Slack file is
+   * not saved here: those downloads ask the person where to save (`save-destination.ts`).
+   */
+  downloadsDir: string;
+}
+//#endregion
+//#region src/cli-command.d.ts
+/**
+ * The command a person is told to run for one of this suite's own CLIs (design 2026-10-04, D1 and D5; CUE-403).
+ *
+ * A bare `agent-gmail approve …` is not runnable for most of the people it is printed for: a package run by npx, by a
+ * managed runtime or from a checkout puts nothing on their PATH. So every such command names this process's Node and
+ * a checked file of the product it runs, with the suite directories it uses pinned as options — and when no file can
+ * be checked, there is no command at all, only a sentence saying what is missing. The caller says which package it is
+ * and what to run; it never supplies the program or quotes the line.
+ *
+ * Three directions. A product's own CLI is found from the product itself, walking from one of its own modules to its
+ * manifest: no registration is ever asked. A channel's handoff to core is found the way the channel itself finds core,
+ * through its installed dependency, and only the same release. Another product's command is found among the servers
+ * registered with the person's MCP clients, which the caller scanned and passes in: only a file-backed registration of
+ * exactly the printing package's version, checked on disk. Nothing a registration names is run, or asked anything —
+ * not even its interpreter for a version: no installer wrote down where a scanned entry came from, so none is trusted
+ * to run (D1). This module never scans, spawns or probes.
+ *
+ * What is checked is checked when the command is printed, not for ever (D6): the file it names is real, readable and
+ * inside its package then, and a later change to that installation is a later fact.
+ */
+/** The gate a constructor call has to pass: only this module holds it. */
+declare const GATE$1: unique symbol;
+/**
+ * A command that runs one of this suite's own CLIs, made only by `locateCliCommand`. Rendered as every printed command
+ * is — a line to paste, or on Windows its words as JSON when no line is safe in every shell (`inlineCommand`,
+ * `commandText`).
+ *
+ * A class with a private field, so the type is nominal: an object literal with the same fields is not one, and nor is
+ * a spread copy of one with other words in it, as it would be with a symbol-keyed brand. Only the type is exported;
+ * the class and its gate are not.
+ */
+declare class PrintedCommand {
+  #private;
+  /** The words, as the program is to receive them: this Node, its flags, the entry, then the CLI's own words. */
+  readonly words: readonly string[];
+  /** The line to paste; null when one of the words has no printing that every Windows shell passes on alike. */
+  readonly line: string | null;
+  readonly platform: NodeJS.Platform;
+  constructor(gate: typeof GATE$1, words: readonly string[], platform: NodeJS.Platform, entry: string);
+  /**
+   * The real path of the file it runs, as it was checked when the command was located: a fact about then (D6). The
+   * command names this path and nothing else, so what runs is whatever is there when the person runs it.
+   */
+  get entry(): string;
+  /**
+   * As JSON — a result's field written out by `--json`, or returned to an MCP client — it is the text it always was:
+   * its line, or its words as JSON with what to do when no Windows line is safe (`commandText`). Rendered where it
+   * leaves the process, so a field can hold the command itself and the wire stays the same.
+   */
+  toJSON(): string;
+  /** Never interpolated: a sentence gives a command through `handoffSentence`, a value through `handoffText`. */
+  [Symbol.toPrimitive](): never;
+}
+/** The package asking: a module of its own (`import.meta.url`), and the package that module is expected to be in. */
+interface CliCommandCaller {
+  readonly url: string;
+  readonly packageName: string;
+}
+/** Why there is no command: the step that found nothing it could check. */
+type CliNotLocatedReason = "caller" | "manifest" | "core" | "version" | "engine" | "bin" | "entry" | "interpreter" | "arguments" | "direction" | "no-registrations" | "not-registered";
+/** Why one registration of the product was not used. */
+type RegistrationRejection = "npx" | "arguments" | "no-file" | "no-package" | "version" | "engine" | "bin" | "entry";
+interface RegistrationNotUsed {
+  readonly client: string;
+  readonly path: string;
+  readonly name: string;
+  readonly why: RegistrationRejection;
+}
+/**
+ * No command: nothing to run, and a sentence naming the product, its package and the exact version it needs. An
+ * installation that has gone or changed since is said so, never replaced by a suite command found by name on PATH.
+ */
+interface CliCommandNotLocated {
+  readonly ok: false;
+  readonly reason: CliNotLocatedReason;
+  /** How the product is named to a person: `Gmail`. */
+  readonly product: string;
+  readonly package: string;
+  /** The exact version needed: the printing package's own, since the suite is released together. */
+  readonly version: string;
+  /** For `engine`: the Node range the target declares. */
+  readonly nodeRange?: string | undefined;
+  /** For another product: each registration of it that was looked at, and why it was not used. */
+  readonly registrations?: readonly RegistrationNotUsed[] | undefined;
+  /** What was found, in a clause. */
+  readonly detail: string;
+  /** The whole sentence to show. */
+  readonly message: string;
+}
+//#endregion
+//#region src/handoff-text.d.ts
+/**
+ * A handoff as words a person reads, and what a core function that prints one is given (CUE-403; CONTRIBUTING.md,
+ * "Telling a person what to run"). `handoffs.ts` makes located handoffs and re-exports all of this.
+ *
+ * Kept apart from the locator on purpose: the configuration store, the secret stores and the attachment jail print
+ * handoffs too, and the locator's own imports reach the configuration store, so importing it from them would be a
+ * cycle. Nothing here locates anything or imports a module that does: a located command is made by `handoffs.ts` and
+ * handed in, and what is here only renders one. With none handed in, there is nothing to render: a package that did not
+ * give core its caller and is asked for a command has a programming error, not a bare name to fall back on.
+ */
+/** A command for a person to run, located, or the sentence saying why there is none here. */
+type Handoff = PrintedCommand | CliCommandNotLocated;
+interface HandoffUse {
+  /** The suite folders the command reads or writes; the four every command opens when left out. */
+  readonly uses?: readonly PathName[] | undefined;
+  /** It also reads or writes downloads, so the downloads folder is pinned too. */
+  readonly downloads?: boolean | undefined;
+}
+/**
+ * The commands a package tells a person to run, made once per printing process from its caller (`handoffs.ts`,
+ * `cliHandoffs`): `openCore({ caller })` puts them on `core.handoffs`. Each method takes the CLI's own words, never the
+ * program, and returns a `Handoff`.
+ */
+interface CliHandoffs {
+  /** The printing package: one of its own modules and its name. */
+  readonly caller: CliCommandCaller;
+  /** The shell the commands are quoted for. */
+  readonly platform: NodeJS.Platform;
+  /** The printing package's own CLI, with these words after the program. */
+  own(words: readonly string[], use?: HandoffUse): Handoff;
+  /** The core CLI: the printing package's own when that is core, the core it has installed otherwise. */
+  core(words: readonly string[], use?: HandoffUse): Handoff;
+  /** The CLI of `channel` — `core`, `gmail`, `slack` …: own, core, or another product found among its registrations. */
+  of(channel: string, words: readonly string[], use?: HandoffUse): Handoff;
+  /** The same commands, quoted for another shell. */
+  on(platform: NodeJS.Platform): CliHandoffs;
+  /**
+   * The same, able to find another product: with the servers registered with this machine's MCP clients read now, from
+   * the environment these were made with. Read once per call; nothing a registration names is run.
+   */
+  registered(): Promise<CliHandoffs>;
+  /** The same, finding another product among these registrations: a scan the caller has already read. */
+  withRegistrations(registrations: readonly RegisteredServer[]): CliHandoffs;
+}
+type SendPolicy = "chat" | "confirm" | "never";
+/**
+ * How a loosening of the configuration is approved: `chat` — the person says yes in the conversation and the agent
+ * claims the approval — or `confirm` — the person types a code at a terminal, as for a send under `confirm`.
+ *
+ * There is no `never`. A setting the software refused ever to loosen would leave editing the file by hand as the only
+ * way to change it, and that passes no gate at all.
+ */
+type ChangePolicy = "chat" | "confirm";
+/** Whether this machine checks for a newer release once a day, and stops until it is updated or put off. */
+type UpdateCheckSetting = "on" | "off";
+type StoreKind = "keychain" | "file";
+interface ClientConfig {
+  provider: string;
+  clientId: string;
+  projectId?: string | undefined;
+  secretRef: string;
+  addedAt: string;
+  /**
+   * The organisation profile that made this row and owns it (design 2026-10-02 §D4) — absent on a row a person
+   * registered, or one a profile adopted. A row carrying it is the profile's to change: `org update` and `org remove`
+   * change it, and `client add --replace` and `client remove` refuse it while its organisation has a record.
+   *
+   * Additive: client rows are loose, so a release that does not know the key keeps it through its writes.
+   */
+  organisation?: string | undefined;
+}
+interface InboxConfig {
+  /** Immutable id (`ibx_` + 16 base32 characters). Secrets and all state are keyed by it; the alias is a label. */
+  id: string;
+  provider: string;
+  email: string;
+  /** Stable account id (OIDC `sub`). Absent for inboxes imported from tools that never asked for it. */
+  sub?: string | undefined;
+  identity: "oidc" | "legacy";
+  client: string;
+  tier: string;
+  contacts: boolean;
+  grantedScopes: string[];
+  secretRef: string;
+  sendPolicy?: SendPolicy | undefined;
+  /** Overrides `defaults.changePolicy` for changes to this inbox. */
+  changePolicy?: ChangePolicy | undefined;
+  internalDomains: string[];
+  createdAt: string;
+}
+interface Defaults {
+  sendPolicy: SendPolicy;
+  /**
+   * How a loosening is approved wherever an inbox or account does not say otherwise. Absent reads as `chat`.
+   *
+   * Absent rather than filled in by the schema, unlike `sendPolicy`. A config written before this setting existed
+   * reads as `chat` from then on, and the release note says so; a default the schema supplied would be written into
+   * the file by the next unrelated change, where it would look like a choice somebody made.
+   */
+  changePolicy?: ChangePolicy | undefined;
+  riskEscalation: boolean;
+  sendCaps: {
+    perHour: number;
+    perDay: number;
+  };
+  attachRoots: string[];
+  /** Extra deny entries on top of the built-in list. */
+  attachDeny: string[];
+  downloadsDir?: string | undefined;
+  timezone: string;
+  confirm: {
+    /**
+     * Fail-closed allowlist of MCP `clientInfo.name` values whose form elicitation is trusted to reach a human.
+     * Empty by default; only the CLI adds entries, after a probe.
+     */
+    elicitationClients: string[];
+  };
+  /**
+   * The daily update check (design 2026-09-28): once a day this machine asks npm whether a newer release is out, and
+   * every server and command stops until it is updated or put off until tomorrow. Absent reads as `on`.
+   *
+   * Absent rather than filled in, as `changePolicy` is: a default the schema supplied would be written into the file
+   * by the next unrelated change, where it would look like a choice somebody made. Turning it off is a loosening —
+   * it is what keeps a machine from quietly falling behind a release — so it is approved like one; on applies at once.
+   */
+  updateCheck?: UpdateCheckSetting | undefined;
 }
-declare const ZodTuple: $constructor<ZodTuple>;
-declare function tuple<T extends readonly [SomeType, ...SomeType[]]>(items: T, params?: string | $ZodTupleParams): ZodTuple<T, null>;
-declare function tuple<T extends readonly [SomeType, ...SomeType[]], Rest extends SomeType>(items: T, rest: Rest, params?: string | $ZodTupleParams): ZodTuple<T, Rest>;
-declare function tuple(items: [], params?: string | $ZodTupleParams): ZodTuple<[], null>;
-interface ZodRecord<Key extends $ZodRecordKey = $ZodRecordKey, Value extends SomeType = $ZodType> extends _ZodType<$ZodRecordInternals<Key, Value>>, $ZodRecord<Key, Value> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  keyType: Key;
-  valueType: Value;
+/**
+ * A connected account on a platform that is not mail: a Slack workspace, and every channel after it (design
+ * 2026-09-26) — one generic record, whatever the platform.
+ *
+ * `id`, `platform`, `workspace` (the container: a Slack team, a Resend team, a WhatsApp store), `userId` (who it acts
+ * as), `tier`, `mode`, `grantedScopes`, `secretRef`, the two policies and `createdAt` are every channel's. A channel
+ * may keep keys of its own beside them — Slack's `appId`, `redirectPort` — and they are kept through every write. It
+ * may not add a safety setting: only `sendPolicy`, `changePolicy` and `mode` are judged by `classifyChange`, so a key
+ * of a channel's own that loosened something would loosen it unasked.
+ *
+ * `secretRef` stays required, although the 2026-09-26 contract made it optional for a channel with no credential:
+ * every earlier release requires it, and they share this file — an account without one would make the whole
+ * configuration unreadable to a server started last week. Such a channel records a reference that names no secret,
+ * `<platform>:none:<id>`, until a config version can say otherwise.
+ *
+ * It sits beside `inboxes` rather than replacing it. The spec asked for one `accounts` map holding everything, and
+ * that rename is the one change this file cannot take: `version: 1` is additive precisely because an MCP server
+ * started last week and a CLI run today share the file, and a release that moved every mailbox out of `inboxes`
+ * would read, to the older of the two, as a config with no mailboxes in it. What the rename was for — one list of
+ * everything connected, whatever the platform — is a question about the shape of the answer, not the shape of the
+ * file, so `connectedAccounts()` provides it and the file grows one key.
+ */
+interface AccountConfig {
+  id: string;
+  /** `slack`. */
+  platform: string;
+  /** The workspace or team id. Every other id this account sees is only meaningful inside it. */
+  workspace: string;
+  /** "Acme Corp" — shown to people, never matched on: a workspace can be renamed and stays the same workspace. */
+  workspaceName?: string | undefined;
+  /** This account's own user id in that workspace, so its own messages can be told from everyone else's. */
+  userId: string;
+  tier: string;
+  grantedScopes: string[];
+  /** Where its credential is in the secret store, `<platform>:…` — for a channel that stores none, `<platform>:none:<id>`. */
+  secretRef: string;
+  sendPolicy?: SendPolicy | undefined;
+  /** Overrides `defaults.changePolicy` for changes to this account. */
+  changePolicy?: ChangePolicy | undefined;
+  createdAt: string;
+  /**
+   * The OAuth client this account's token was issued by, and the app it belongs to.
+   *
+   * Recorded because the Gmail release found the opposite: a reauth used the first OAuth client in the config
+   * rather than the inbox's own, and then did not record which one it had used. Slack makes that worse — D8
+   * means **one app per workspace**, so "the first app" is wrong more often than it is right — and a reauth
+   * that silently moves an account onto a different app changes what it can do without saying so.
+   *
+   * Optional because the key is additive: a config written before these existed parses unchanged.
+   */
+  oauthClientId?: string | undefined;
+  appId?: string | undefined;
+  /**
+   * `read` or `send`, as installed.
+   *
+   * Kept beside `grantedScopes` rather than derived from them, because the two answer different questions: the
+   * scopes are what Slack granted, and this is what the person asked for. A disagreement between them is drift
+   * worth reporting, and a value derived from the scopes could never disagree.
+   */
+  mode?: string | undefined;
+  /**
+   * The loopback port the last sign-in used, which is the one in the app's redirect URL.
+   *
+   * Slack matches redirect URLs exactly, so every later sign-in and every set of steps that edits the app has to
+   * name this number. Without it the steps said `<port>`, or — from the MCP server — guessed 51234, and a person who
+   * had chosen another port followed them to a sign-in that failed on the way back.
+   */
+  redirectPort?: number | undefined;
+  /** The organisation profile whose Slack app created this account. Absent for a person's own app. */
+  organisation?: string | undefined;
+  /** Which app in that profile issued the account's current credential. */
+  profileApp?: "read" | "send" | undefined;
 }
-declare const ZodRecord: $constructor<ZodRecord>;
-declare function record<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key, Value>;
-declare function partialRecord<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key & $partial, Value>;
-declare function looseRecord<Key extends $ZodRecordKey, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodRecordParams): ZodRecord<Key, Value>;
-interface ZodMap<Key extends SomeType = $ZodType, Value extends SomeType = $ZodType> extends _ZodType<$ZodMapInternals<Key, Value>>, $ZodMap<Key, Value> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  keyType: Key;
-  valueType: Value;
-  min(minSize: number, params?: string | $ZodCheckMinSizeParams): this;
-  nonempty(params?: string | $ZodCheckMinSizeParams): this;
-  max(maxSize: number, params?: string | $ZodCheckMaxSizeParams): this;
-  size(size: number, params?: string | $ZodCheckSizeEqualsParams): this;
+type PendingRevocationStatus = "pending" | "revoked" | "expired";
+/** One bearer token in a superseded rotating bundle, tracked independently from its pair. */
+interface PendingRevocationTokenState {
+  status: PendingRevocationStatus;
+  /** The fixed absolute time after which the old token is known to be unusable. */
+  deadline: string;
 }
-declare const ZodMap: $constructor<ZodMap>;
-declare function map<Key extends SomeType, Value extends SomeType>(keyType: Key, valueType: Value, params?: string | $ZodMapParams): ZodMap<Key, Value>;
-interface ZodSet<T extends SomeType = $ZodType> extends _ZodType<$ZodSetInternals<T>>, $ZodSet<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  min(minSize: number, params?: string | $ZodCheckMinSizeParams): this;
-  nonempty(params?: string | $ZodCheckMinSizeParams): this;
-  max(maxSize: number, params?: string | $ZodCheckMaxSizeParams): this;
-  size(size: number, params?: string | $ZodCheckSizeEqualsParams): this;
+/**
+ * A superseded credential kept until each token in it is conclusively revoked or expired.
+ *
+ * `store` belongs to the entry rather than being inferred from `secrets.store`: an older release can move the root
+ * store without knowing to move this bundle, and cleanup must still find the only copy that exists.
+ */
+interface PendingRevocation {
+  ref: string;
+  store: StoreKind;
+  platform: string;
+  workspace: string;
+  createdAt: string;
+  tokens: {
+    access: PendingRevocationTokenState;
+    refresh?: PendingRevocationTokenState | undefined;
+  };
 }
-declare const ZodSet: $constructor<ZodSet>;
-declare function set<Value extends SomeType>(valueType: Value, params?: string | $ZodSetParams): ZodSet<Value>;
-interface ZodEnum<
-/** @ts-ignore Cast variance */
-out T extends EnumLike = EnumLike> extends _ZodType<$ZodEnumInternals<T>>, $ZodEnum<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  enum: T;
-  options: Array<T[keyof T]>;
-  extract<const U extends readonly (keyof T)[]>(values: U, params?: string | $ZodEnumParams): ZodEnum<Flatten$1<Pick<T, U[number]>>>;
-  exclude<const U extends readonly (keyof T)[]>(values: U, params?: string | $ZodEnumParams): ZodEnum<Flatten$1<Omit<T, U[number]>>>;
+interface ConfigBody {
+  /**
+   * The one secret backend for this config directory: client secrets, refresh tokens and the approval key. Absent
+   * until the first command that stores a secret chooses it.
+   */
+  secrets?: {
+    store: StoreKind;
+  } | undefined;
+  clients: Record<string, ClientConfig>;
+  inboxes: Record<string, InboxConfig>;
+  /** Non-mail accounts. Absent in every config written before this key existed, hence the default. */
+  accounts: Record<string, AccountConfig>;
+  /** Superseded rotating credentials which still need conclusive per-token cleanup. */
+  pendingRevocations?: PendingRevocation[] | undefined;
+  defaults: Defaults;
+}
+interface ConfigV1 extends ConfigBody {
+  version: 1;
+}
+/** A name an account used to have, and the account that had it. */
+interface FormerName {
+  /** What it was renamed to — at the time. The account's current name is found by `id`, so a later rename is followed. */
+  name: string;
+  id: string;
 }
-declare const ZodEnum: $constructor<ZodEnum>;
-declare function _enum<const T extends readonly string[]>(values: T, params?: string | $ZodEnumParams): ZodEnum<ToEnum<T[number]>>;
-declare function _enum<const T extends EnumLike>(entries: T, params?: string | $ZodEnumParams): ZodEnum<T>;
-/** @deprecated This API has been merged into `z.enum()`. Use `z.enum()` instead.
+/**
+ * Names that were replaced, per kind, and never reusable.
  *
- * ```ts
- * enum Colors { red, green, blue }
- * z.enum(Colors);
- * ```
+ * Per kind because version 1 lets a mailbox and a workspace share a word: `work` the mailbox and `work` the workspace
+ * become `work/gmail` and `work/slack`, and one flat record could not say which old `work` is which.
  */
-declare function nativeEnum<T extends EnumLike>(entries: T, params?: string | $ZodEnumParams): ZodEnum<T>;
-interface ZodLiteral<T extends Literal = Literal> extends _ZodType<$ZodLiteralInternals<T>>, $ZodLiteral<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  values: Set<T>;
-  /** @legacy Use `.values` instead. Accessing this property will throw an error if the literal accepts multiple values. */
-  value: T;
+interface FormerNames {
+  inboxes: Record<string, FormerName>;
+  accounts: Record<string, FormerName>;
 }
-declare const ZodLiteral: $constructor<ZodLiteral>;
-declare function literal<const T extends ReadonlyArray<Literal>>(value: T, params?: string | $ZodLiteralParams): ZodLiteral<T[number]>;
-declare function literal<const T extends Literal>(value: T, params?: string | $ZodLiteralParams): ZodLiteral<T>;
-interface ZodFile extends _ZodType<$ZodFileInternals>, $ZodFile {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  min(size: number, params?: string | $ZodCheckMinSizeParams): this;
-  max(size: number, params?: string | $ZodCheckMaxSizeParams): this;
-  mime(types: MimeTypes | Array<MimeTypes>, params?: string | $ZodCheckMimeTypeParams): this;
+/** Who an organisation's Google client is for, as its administrator states it (design 2026-10-02 §D2). */
+type OrganisationServes = "any" | {
+  domains: string[];
+};
+/**
+ * One Google client an organisation profile brought here: a *generation* (design 2026-10-02 §D4).
+ *
+ * `owned` — the profile made the client row `name` (`rgc-1`), which carries `organisation`, and its secret is the
+ * profile's to rewrite. `adopted` — the row was already here under a name a person chose (they ran `client add` with
+ * the organisation's file), and stays theirs: no `org` command changes or removes it. `serves` is per generation,
+ * because it is a fact about one client, not about the organisation.
+ */
+interface OrganisationGeneration {
+  name: string;
+  clientId: string;
+  projectId?: string | undefined;
+  ownership: "owned" | "adopted";
+  serves: OrganisationServes;
+  addedAt: string;
 }
-declare const ZodFile: $constructor<ZodFile>;
-declare function file(params?: string | $ZodFileParams): ZodFile;
-interface ZodTransform<O = unknown, I = unknown> extends _ZodType<$ZodTransformInternals<O, I>>, $ZodTransform<O, I> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
+interface OrganisationSlackApp {
+  clientId: string;
+  appId?: string | undefined;
 }
-declare const ZodTransform: $constructor<ZodTransform>;
-declare function transform<I = unknown, O = I>(fn: (input: I, ctx: $RefinementCtx) => O): ZodTransform<Awaited<O>, I>;
-interface ZodOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodOptionalInternals<T>>, $ZodOptional<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+/**
+ * What this machine records of one organisation profile: never its bytes and never its secret — where it was read
+ * from, the SHA-256 of what was read and when, the generations of its Google client, and its Slack apps.
+ */
+interface OrganisationRecord {
+  label: string;
+  /** Read again, from this absolute path, by every `org update`. `file` is the one kind version 1 knows (§D3). */
+  source: {
+    kind: string;
+    path: string;
+  };
+  sha256: string;
+  readAt: string;
+  addedAt: string;
+  /** Whether the member asked for this organisation's client to serve addresses outside it too (§D6). */
+  forOtherAddresses: boolean;
+  /** `active` names the generation new mailboxes get — none once a profile stops naming a Google client. */
+  gmail?: {
+    active: string | null;
+    generations: OrganisationGeneration[];
+  } | undefined;
+  slack?: {
+    workspace: string;
+    workspaceName: string;
+    redirectPort: number;
+    apps: {
+      read?: OrganisationSlackApp | undefined;
+      send?: OrganisationSlackApp | undefined;
+    };
+  } | undefined;
 }
-declare const ZodOptional: $constructor<ZodOptional>;
-declare function optional<T extends SomeType>(innerType: T): ZodOptional<T>;
-interface ZodExactOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodExactOptionalInternals<T>>, $ZodExactOptional<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+interface ConfigV2 extends ConfigBody {
+  version: 2;
+  formerNames: FormerNames;
+  /**
+   * The organisation profiles added here, by organisation word (design 2026-10-02 §D4). Absent reads as none, and
+   * stays absent until the first `org add`: a key the schema filled in would be written into every file by the next
+   * unrelated change.
+   */
+  organisations?: Record<string, OrganisationRecord> | undefined;
 }
-declare const ZodExactOptional: $constructor<ZodExactOptional>;
-declare function exactOptional<T extends SomeType>(innerType: T): ZodExactOptional<T>;
-interface ZodNullable<T extends SomeType = $ZodType> extends _ZodType<$ZodNullableInternals<T>>, $ZodNullable<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+type Config$1 = ConfigV1 | ConfigV2;
+/** The committed config returned by an update; process-only commit metadata is deliberately stored out of band. */
+type ConfigUpdateResult = Config$1;
+declare class ConfigStore {
+  #private;
+  readonly path: string;
+  /**
+   * @param options.handoffs the printing package's handoffs (`core.handoffs`, CUE-403), for the command a refusal
+   *   names; left out, a refusal that has to name one is a programming error (`requiredHandoffs`).
+   */
+  constructor(configDir: string, options?: {
+    readonly handoffs?: CliHandoffs | undefined;
+  });
+  /** The current config; an empty one when the file does not exist yet. */
+  load(): Promise<Config$1>;
+  /**
+   * Read-modify-write under a lock, so a CLI command and a running MCP server never lose each other's changes. The
+   * mutator receives a fresh copy read inside the lock and returns the new config, which is validated before writing.
+   */
+  update(mutator: (config: Config$1) => Config$1 | Promise<Config$1>, options?: {
+    consent?: LooseningConsent;
+    signal?: AbortSignal | undefined;
+  }): Promise<ConfigUpdateResult>;
+  /**
+   * The one way a version-1 config becomes version 2.
+   *
+   * Under the credentials lock and then the config lock — the order everything takes them in — so it cannot land
+   * between a removal's read and its write, or in the middle of moving secrets between backends.
+   *
+   * `expected` is the fingerprint of the config the caller previewed. The file is read again inside the locks, and
+   * if it is not that config any more the whole thing is refused: somebody confirmed a mapping computed from
+   * something else. Nothing waits for a person while holding a lock; the preview happens before this is called.
+   *
+   * `build` produces version 2 from the locked snapshot. What it may change is checked rather than trusted: the same
+   * accounts, byte for byte, under new keys — a rename grants nothing, so a build that changed anything else is a
+   * bug and is refused before it is written.
+   *
+   * Idempotent, but only for this plan. A retry after a write that committed — even one whose lock release then
+   * failed — finds version 2, recognises its own mapping in it, and says so. Version 2 that does *not* carry this
+   * mapping is somebody else's migration; saying "already migrated" there would report a mapping nobody applied,
+   * and a caller updating registrations from it would point them at names that do not exist.
+   *
+   * `rows` is the plan, and the question is asked of the mapping rather than of the whole file: between a
+   * committed write and its retry, something else may have changed a policy or a timezone, and a retry refused
+   * over that would be idempotency in name only. The rows are checked here rather than by whoever built them,
+   * for the same reason `build` is: a caller that could answer its own question could answer it wrongly.
+   *
+   * The file it replaces is copied beside it first — see `backUpBeforeMigration` — and the copy's path returned.
+   */
+  migrateNames(expected: string, rows: readonly RenamedAccount[], build: (current: ConfigV1) => ConfigV2): Promise<{
+    status: "migrated" | "already-migrated";
+    config: ConfigV2;
+    backup?: string;
+  }>;
 }
-declare const ZodNullable: $constructor<ZodNullable>;
-declare function nullable<T extends SomeType>(innerType: T): ZodNullable<T>;
-declare function nullish<T extends SomeType>(innerType: T): ZodOptional<ZodNullable<T>>;
-interface ZodDefault<T extends SomeType = $ZodType> extends _ZodType<$ZodDefaultInternals<T>>, $ZodDefault<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
-  /** @deprecated Use `.unwrap()` instead. */
-  removeDefault(): T;
+/** One account's rename, as the migration planned it. */
+interface RenamedAccount {
+  readonly kind: "inbox" | "account";
+  readonly from: string;
+  readonly to: string;
+  readonly id: string;
 }
-declare const ZodDefault: $constructor<ZodDefault>;
-declare function _default<T extends SomeType>(innerType: T, defaultValue: NoUndefined<output$1<T>> | (() => NoUndefined<output$1<T>>)): ZodDefault<T>;
-interface ZodPrefault<T extends SomeType = $ZodType> extends _ZodType<$ZodPrefaultInternals<T>>, $ZodPrefault<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+/** A value a loosened setting had or will have: a policy, a mode, a list, a pair of caps, a path, or nothing. */
+type SettingValue = string | number | boolean | readonly string[] | {
+  readonly [key: string]: unknown;
+} | null;
+/**
+ * One loosened setting, with the values the classifier compared.
+ *
+ * The values are the ones it judged, not the raw fields: an inbox that inherits a looser default reports the policy
+ * it inherits, and a new inbox reports the default it was measured against. A preview built from anything else could
+ * show a person one change while the classifier judged another.
+ */
+interface Loosening {
+  /** As `ConfigStore.update` names it in a refusal: `accounts.rgc/slack.mode`, `defaults.sendPolicy`. */
+  readonly path: string;
+  readonly before: SettingValue;
+  readonly after: SettingValue;
+  /**
+   * The inbox or account measured on the before side, by id. Absent for one new in this change and for a setting
+   * that belongs to the whole configuration. Carried so that an approval of this loosening cannot be spent on a
+   * different account that took the same name in the meantime.
+   */
+  readonly id?: string | undefined;
 }
-declare const ZodPrefault: $constructor<ZodPrefault>;
-declare function prefault<T extends SomeType>(innerType: T, defaultValue: input$1<T> | (() => input$1<T>)): ZodPrefault<T>;
-interface ZodNonOptional<T extends SomeType = $ZodType> extends _ZodType<$ZodNonOptionalInternals<T>>, $ZodNonOptional<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+/**
+ * One setting a change writes, from the value in the file before to the value after — whichever way it moves.
+ *
+ * Unlike a `Loosening`, these are the raw values, not the effective ones: `null` for a setting the file does not
+ * hold, so a mailbox set to `chat` itself is told apart from one inheriting `chat`, which only the first survives a
+ * later change to the default. `id` is the inbox or account measured on the before side, as for a loosening.
+ */
+interface SettingChange {
+  readonly path: string;
+  readonly before: SettingValue;
+  readonly after: SettingValue;
+  readonly id?: string | undefined;
 }
-declare const ZodNonOptional: $constructor<ZodNonOptional>;
-declare function nonoptional<T extends SomeType>(innerType: T, params?: string | $ZodNonOptionalParams): ZodNonOptional<T>;
-interface ZodSuccess<T extends SomeType = $ZodType> extends _ZodType<$ZodSuccessInternals<T>>, $ZodSuccess<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+/**
+ * Proof that exactly these paths may loosen: produced by a CLI after a person at a terminal typed a challenge, or by
+ * `claimChange` from a change approval a person gave.
+ */
+interface LooseningConsent {
+  kind: "loosening-consent";
+  paths: readonly string[];
+  /**
+   * What each path was approved to move between, when the consent came from a change approval.
+   *
+   * A terminal challenge is answered moments before the write it permits, so the paths are enough. An approval is
+   * prepared first and applied later — after a sign-in, possibly minutes later — and in between the configuration
+   * can move underneath it: the same path, loosened from a different value, or on a different account that took
+   * the name. With these, `ConfigStore.update` refuses any loosening that is not exactly one of them.
+   */
+  changes?: readonly Loosening[] | undefined;
 }
-declare const ZodSuccess: $constructor<ZodSuccess>;
-declare function success<T extends SomeType>(innerType: T): ZodSuccess<T>;
-interface ZodCatch<T extends SomeType = $ZodType> extends _ZodType<$ZodCatchInternals<T>>, $ZodCatch<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
-  /** @deprecated Use `.unwrap()` instead. */
-  removeCatch(): T;
+/**
+ * Why a saved name has {@link DOWNLOAD_SUFFIX} after it: a name tools read or run on their own (`auto-read`), an
+ * extension that is not one of the inert ones (`type`), or no extension at all (`no-extension`).
+ */
+type RenameReason = "auto-read" | "type" | "no-extension";
+//#endregion
+//#region src/approvals.d.ts
+/**
+ * Approval records bind a send to exactly one draft version. States:
+ *
+ *   pending ──approve──▶ approved ──claim──▶ sending ──▶ used | failed
+ *      └──claim (effective policy chat)──────┘      └──▶ unknown (the process died mid-send)
+ *   pending | approved ──▶ revoked ("voided": content changed, wrong inbox, too many wrong challenges, user revoked)
+ *   expired is derived: a pending or approved record past its deadline reads as expired.
+ *
+ * Every transition is a compare-and-swap under a per-record lock. Single use does not rest on the lock alone: a claim
+ * also creates `<id>.claim` with O_EXCL, which the file system guarantees only one process can do.
+ *
+ * A change approval (`kind: 'change'`) lives in the same store and goes through the same states, except that its
+ * claim goes straight to `used`: what it permits is a write to the configuration, which the claimant makes itself.
+ *
+ * So does a download's question (`kind: 'download'`): where to save the files a Gmail or Slack download names. It is
+ * held to the change policy of the mailbox or workspace it is about, as every other change there is. Under `chat` the
+ * person's answer, relayed from the chat, claims it straight from `pending`. Under `confirm` it has to be answered
+ * where an agent cannot answer for them — at their own terminal, or in a form a trusted client shows them — which
+ * records the answer and moves it to `approved`; only then is it claimed, straight to `used`, and the recorded answer
+ * is the one that saves. It gets the store's expiry, its single use and its binding for the reason a change does: an
+ * answer given for three invoices must not save the next conversation's files, nor be spent twice.
+ */
+type ApprovalState = "pending" | "approved" | "sending" | "used" | "failed" | "unknown" | "expired" | "revoked";
+type ApprovalChannel = "elicitation" | "terminal";
+/**
+ * What an approval permits: a send (a mail, a post, a reaction), a change to the configuration, or a download saved
+ * where the person said.
+ *
+ * One store for all three, so a change gets the machinery a send already has — expiry, single use, the typed code —
+ * and a kind on every record, so that none can be spent as another. Without it, a person who approved a post at a
+ * terminal would also have approved whatever change an agent claimed under the same id.
+ */
+type ApprovalKind = "send" | "change" | "download";
+/** The inbox or account a change is about. `id` is absent when the change connects it, and it does not exist yet. */
+interface ChangeTarget {
+  kind: "inbox" | "account";
+  name: string;
+  id?: string | undefined;
 }
-declare const ZodCatch: $constructor<ZodCatch>;
-declare function _catch<T extends SomeType>(innerType: T, catchValue: output$1<T> | ((ctx: $ZodCatchCtx) => output$1<T>)): ZodCatch<T>;
-interface ZodNaN extends _ZodType<$ZodNaNInternals>, $ZodNaN {
-  "~standard": ZodStandardSchemaWithJSON<this>;
+/**
+ * Exactly what a change approval permits, stored on the record so a terminal can show it again and prove it is what
+ * was prepared.
+ */
+interface ChangeBinding {
+  /** The caller's one line about the change, shown to the person. Not part of the digest: the lines below are. */
+  summary: string;
+  /** What it is about, or `null` for a change to the whole configuration. */
+  target: ChangeTarget | null;
+  /** Every safety setting it loosens, with the values `classifyChange` compared. Empty for a destructive change. */
+  loosened: Loosening[];
+  /**
+   * Every setting it writes, loosened or tightened, with the values in the file before and after (`changedSettings`).
+   *
+   * Bound as well as the loosenings, because a preview shows the whole change: a claim that loosened the same thing
+   * while dropping a tightening the person read would otherwise digest the same. Absent reads as none.
+   */
+  settings?: SettingChange[] | undefined;
+  /** What it does outside the configuration, in words: a sign-in, a registration, files removed. */
+  effects: string[];
+  /**
+   * What the call that prepared it already did at once, because it never waits for an approval — a narrowing beside
+   * the change (design 2026-10-02 §D8). Not what approving does: the preview lists these apart, and its header says
+   * the rest is what waits. A field of its own rather than words in `effects`, so no text a change carries — a label
+   * a profile chose, say — can make a preview claim something was done.
+   *
+   * Bound when present, so a record cannot gain one it was not prepared with; absent reads as none, and leaves the
+   * digest of every other change exactly what it was.
+   */
+  doneAtOnce?: string[] | undefined;
 }
-declare const ZodNaN: $constructor<ZodNaN>;
-declare function nan(params?: string | $ZodNaNParams): ZodNaN;
-interface ZodPipe<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends _ZodType<$ZodPipeInternals<A, B>>, $ZodPipe<A, B> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  in: A;
-  out: B;
+/**
+ * Exactly which download a question was asked for, stored on the record so the answer can be held to it.
+ *
+ * The files are the ones the question listed, by the platform's own ids — `<message id>/<part id>` for Gmail, the file
+ * id for Slack — in the order they were listed: a claim for any other set is a claim for a download the person was
+ * not asked about. So are the names they would be saved under, in the same order: a Slack file renamed between the
+ * question and the answer would otherwise be saved under a name the person was never shown. The folders are the two
+ * the question showed, as absolute paths. They are not part of the digest, because they are what the answer *means*
+ * rather than what it is for: `downloads` in the answer is the path the person read, even when an agent runs the
+ * download again from another folder.
+ */
+interface DownloadBinding {
+  /** One line about the download, for a listing: "where to save 2 files from acme/gmail". Not part of the digest. */
+  summary: string;
+  /** The mailbox or workspace the files come from, by the id it has now. */
+  target: {
+    kind: "inbox" | "account";
+    name: string;
+    id: string;
+  };
+  /** Which download asked: `attachments.download`, `files.download`. */
+  operation: string;
+  /** The request as the caller made it, in the words of its own arguments: the selection, and how many at most. */
+  request: Record<string, unknown>;
+  /** The files the question listed, by the platform's ids, in order. */
+  files: string[];
+  /** The names those files would be saved under, as the question listed them, in the same order. */
+  names: string[];
+  /** The two folders the question offered, as absolute paths. */
+  folders: {
+    downloads: string;
+    current: string;
+  };
+  /**
+   * The files as the question listed them to the person — the names they would be saved under, their sizes, why a
+   * name has `.download` after it, and their risk flags — so a terminal or a form can show the question, and its
+   * warnings, again. Not part of the digest: the ids and names above are.
+   */
+  listing?: ListedFile[] | undefined;
+  /** The person's answer, when they gave it where an agent cannot: at a terminal, or in a trusted client's form. */
+  answer?: RecordedSaveAnswer | undefined;
+}
+/** One file as a question lists it. */
+interface ListedFile {
+  /** The name it would be saved under: the sender's made safe, with `.download` after it unless it is inert. */
+  name: string;
+  size: number | null;
+  /** Why `.download` is after its name; absent when the name is the sender's, made safe. */
+  renamed?: RenameReason | undefined;
+  /** Its risk flags, as the file's own listing gives them. */
+  flags?: string[] | undefined;
+}
+/**
+ * An answer recorded on a question: one of the two folders it offered, or the folder the person named, as an absolute
+ * path — resolved where they typed it, so it means the folder they read.
+ */
+type RecordedSaveAnswer = {
+  readonly choice: "downloads" | "current";
+} | {
+  readonly choice: "other";
+  readonly folder: string;
+};
+/** What a claim of a download's question is held to: all of the binding but its summary and the folders it offered. */
+type DownloadRequest = Pick<DownloadBinding, "target" | "operation" | "request" | "files" | "names">;
+interface Expectation {
+  to: string[];
+  cc: string[];
+  bcc: string[];
+  subject: string;
+}
+interface ApprovalRecord {
+  approvalId: string;
+  /** Absent on a send, so a send's record is byte for byte what it was before change approvals existed. */
+  kind?: ApprovalKind | undefined;
+  digestVersion: number;
+  /** For a change: the id of the inbox or account it is about, or empty for one to the whole configuration. */
+  inboxId: string;
+  inboxSub?: string | undefined;
+  draftId: string;
+  /** Changes on every save of the draft; binding to it detects any edit, even one that restores identical content. */
+  draftMessageId: string;
+  digest: string;
+  /** The digest the human was actually shown when approving through a confirm channel. */
+  approvedDigest?: string | undefined;
+  approvedVia?: ApprovalChannel | undefined;
+  /** Live policy at prepare time, for display and audit. */
+  policy: SendPolicy;
+  /** `confirm` when risk escalation raised this send. The effective policy is the stricter of this and the live one. */
+  requiredPolicy: SendPolicy;
+  riskFlags: string[];
+  expect: Expectation;
+  /** Hash of the challenge currently issued to a human; the challenge itself is never stored or returned. */
+  challengeHash?: string | undefined;
+  challengeAttempts: number;
+  state: ApprovalState;
+  createdAt: string;
+  expiresAt: string;
+  updatedAt: string;
+  sentMessageId?: string | undefined;
+  reason?: string | undefined;
+  /** For a change: exactly what it permits. `digest` is `changeDigest` of this. */
+  change?: ChangeBinding | undefined;
+  /** For a download's question: what it asked about, and the folders it offered. `digest` is `downloadDigest`. */
+  download?: DownloadBinding | undefined;
+}
+interface CreateApprovalInput {
+  inboxId: string;
+  inboxSub?: string | undefined;
+  draftId: string;
+  draftMessageId: string;
+  digest: string;
+  policy: SendPolicy;
+  requiredPolicy: SendPolicy;
+  riskFlags: string[];
+  expect: Expectation;
+}
+interface CreateChangeApprovalInput {
+  change: ChangeBinding;
+  /** The change policy in force before the change: it decides how the change is approved. */
+  policy: ChangePolicy;
+}
+/** What a claimant of a change is about to write, and the change policy in force as it does. */
+interface LiveChange {
+  change: ChangeBinding;
+  policy: ChangePolicy;
+}
+/** What the caller observed in the live draft at the moment of a transition. */
+interface LiveDraft {
+  draftMessageId: string;
+  digest: string;
+}
+/** What the product making a claim tells the store about itself. */
+interface ClaimOptions {
+  /** The shell syntax used by any approval command this refusal prints. */
+  platform?: NodeJS.Platform | undefined;
+  /**
+   * The commands the printing package gives a person (`core.handoffs`), for a refusal that names one: the store's own
+   * when left out. With neither, a refusal that has to name one is a programming error (`requiredHandoffs`).
+   */
+  handoffs?: CliHandoffs | undefined;
+  /**
+   * What the caller is told when the send is waiting for a person: which command approves it, and what to run after.
+   *
+   * The product's to say, because the store is shared and the command that approves is not. The store used to say
+   * it itself, in Gmail's words, so a Slack post held for approval told the agent to hand the person
+   * `agent-gmail approve` — which cannot approve a Slack record — or to "send it from Gmail". Left out, the hint
+   * names no product at all rather than the wrong one.
+   */
+  pendingHint?: string | undefined;
+  /**
+   * The caller's cancellation — an MCP request's signal — asked under the record's lock, immediately before the claim
+   * would change the record.
+   *
+   * A claim can wait: for the lock, while another process holds it. A caller that looked at its signal before calling
+   * and found it clear could be cancelled during that wait, and the claim then went through all the same, spending an
+   * approval on a call nobody was waiting for any more — whose outcome its caller then had to record as a failure,
+   * since a claim cannot be put back. Asked here, a cancellation that lands before the record changes leaves it exactly
+   * as it was, for the same call made again; one that lands after is the caller's to handle, as it always was.
+   */
+  signal?: AbortSignal | undefined;
+}
+declare class ApprovalStore {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string, options?: {
+    now?: () => Date;
+    ttlMs?: number;
+    downloadTtlMs?: number;
+    handoffs?: CliHandoffs | undefined;
+  });
+  create(input: CreateApprovalInput): Promise<ApprovalRecord>;
+  get(approvalId: string): Promise<ApprovalRecord | null>;
+  /** Issues a new challenge to show a human; only its hash is kept. */
+  issueChallenge(approvalId: string, kind?: ApprovalKind, platform?: NodeJS.Platform): Promise<string>;
+  /**
+   * A human approved through a confirm channel by typing the issued challenge. The draft must still be exactly what the
+   * record was prepared for; otherwise the record is voided, because the human would be approving content the record
+   * does not describe. Three wrong answers void it too.
+   *
+   * A change is approved the same way, with `kind: 'change'` and its digest standing in for the draft (see
+   * `createChange`), so a person's typed code means one thing whichever kind of approval it is typed for.
+   */
+  approve(approvalId: string, via: ApprovalChannel, live: LiveDraft, answer: string, kind?: ApprovalKind, platform?: NodeJS.Platform): Promise<ApprovalRecord>;
+  /**
+   * Claims the record for sending, once. Non-consuming refusals (not yet approved) leave the record untouched so the
+   * human can still approve it; integrity failures (other inbox or account, edited or changed draft, different
+   * recipients or subject) void it. Success creates the O_EXCL claim marker.
+   */
+  claimForSend(approvalId: string, live: LiveDraft & {
+    inboxId: string;
+    inboxSub?: string | undefined;
+    policy: SendPolicy;
+    expect: Expectation;
+  }, options?: ClaimOptions): Promise<ApprovalRecord>;
+  /**
+   * A change approval, pending, bound to `changeDigest(input.change)`.
+   *
+   * The digest is computed here, never taken from the caller, so a record cannot claim to be bound to one change while
+   * describing another. It stands in for the draft revision too, as a reaction's does: a change has no draft, and the
+   * same value means the same change.
+   */
+  createChange(input: CreateChangeApprovalInput): Promise<ApprovalRecord>;
+  /**
+   * Claims a change approval, once, for the change the caller is about to write.
+   *
+   * `live.change` is the change as the caller computes it now, and it has to digest to what was prepared: a different
+   * path, a different value, a different account or a different effect voids the approval, because the person agreed
+   * to something else. `live.policy` is the change policy in force now, and the stricter of it and the one at prepare
+   * decides — so tightening the policy after an agent prepared a change takes effect on that change, and loosening it
+   * does not release one prepared under `confirm`.
+   *
+   * Under `chat` a pending approval is claimable: the yes was given in the conversation. Anything stricter needs a
+   * person to have typed the code at a terminal first; until then the refusal leaves the record as it is.
+   */
+  claimForChange(approvalId: string, live: LiveChange, options?: ClaimOptions): Promise<ApprovalRecord>;
+  /**
+   * A download's question, pending, bound to `downloadDigest(input.download)` — computed here, never taken from the
+   * caller, as a change's digest is. It stands in for the draft revision too.
+   *
+   * `policy` is the change policy of the mailbox or workspace the files come from, as it stands when the question is
+   * asked: where a stranger's files land on this machine is a change to it, and is answered the way that account's
+   * other changes are approved. A claim holds the question to the stricter of this and the policy then.
+   */
+  createDownload(input: {
+    download: DownloadBinding;
+    policy: ChangePolicy;
+  }): Promise<ApprovalRecord & {
+    download: DownloadBinding;
+  }>;
+  /**
+   * Records the person's answer to a download's question, given where an agent cannot give it: at their own terminal,
+   * or in a form a trusted client showed them. The question moves to `approved`, carrying the answer, and waits for
+   * the download to claim it — which it may then do under `confirm`, and which saves where this answer says.
+   *
+   * Only a pending question can be answered, and only once: a second answer is refused, not taken over the first.
+   */
+  answerDownload(approvalId: string, via: ApprovalChannel, answer: RecordedSaveAnswer, platform?: NodeJS.Platform): Promise<ApprovalRecord & {
+    download: DownloadBinding;
+  }>;
+  /**
+   * Claims a download's question, once, for the download the caller is about to make — and returns it, with the
+   * folders it offered, so that `downloads` and `current` in the answer mean the paths the person read, and with the
+   * answer the person recorded, when they recorded one.
+   *
+   * `live` is the download as the caller computes it now: the same account, the same request, the same files under
+   * the same names — the person answered for those files and no others. Any other is refused, and the question left
+   * open, as it was: a second call that got an argument wrong is the agent's slip, not the person's, and voiding the
+   * question for it would make the person answer again for nothing. It still expires, and is claimed once.
+   *
+   * `options.policy` is the change policy of that account now, and the stricter of it and the one the question was
+   * asked under decides. Under `chat`, a pending question is claimed with the answer the caller carries: the person
+   * gave it in the conversation. Under `confirm`, only a question the person answered at a terminal or in a trusted
+   * form can be claimed; a pending one is refused, and left as it is, so they can still answer it. One used, voided or
+   * expired is refused as an approval in that state is.
+   *
+   * `options.signal` is the download's cancellation, asked under the lock as a send's is (`ClaimOptions.signal`): a
+   * download cancelled while this waited saves nothing and leaves the question open, the answer still unused.
+   */
+  claimForDownload(approvalId: string, live: DownloadRequest, options?: {
+    policy?: ChangePolicy | undefined;
+    pendingHint?: string | undefined;
+    signal?: AbortSignal | undefined;
+    platform?: NodeJS.Platform | undefined;
+    handoffs?: CliHandoffs | undefined;
+  }): Promise<ApprovalRecord & {
+    download: DownloadBinding;
+  }>;
+  /** Records the outcome of the one send attempt. */
+  complete(approvalId: string, outcome: {
+    sentMessageId: string;
+  } | {
+    error: string;
+  }): Promise<ApprovalRecord>;
+  /** Voids a pending or approved record (user revoked it, or policy tightened). Other records are left as they are. */
+  revoke(approvalId: string, reason: string): Promise<ApprovalRecord>;
+  list(filter?: {
+    inboxId?: string;
+    states?: ApprovalState[];
+  }): Promise<ApprovalRecord[]>;
 }
-declare const ZodPipe: $constructor<ZodPipe>;
-declare function pipe<const A extends SomeType, B extends $ZodType<unknown, output$1<A>> = $ZodType<unknown, output$1<A>>>(in_: A, out: B | $ZodType<unknown, output$1<A>>): ZodPipe<A, B>;
-interface ZodCodec<A extends SomeType = $ZodType, B extends SomeType = $ZodType> extends ZodPipe<A, B>, $ZodCodec<A, B> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  _zod: $ZodCodecInternals<A, B>;
-  def: $ZodCodecDef<A, B>;
+//#endregion
+//#region src/audit.d.ts
+/**
+ * Every mailbox write leaves one line here: what was done, to which inbox, with which ids and outcome. Never message
+ * bodies, never secrets — recipient *domains* only, so the log can be shared when asking for help.
+ */
+interface AuditRecord {
+  at: string;
+  /** Immutable inbox id; `alias` is the label at the time. */
+  inboxId: string;
+  alias?: string;
+  operation: string;
+  /** `started` marks the first half of a change recorded before it is made; a later record for the same ids ends it. */
+  outcome: "ok" | "refused" | "failed" | "started";
+  ids?: Record<string, string | string[] | CondensedIds>;
+  recipientDomains?: string[];
+  /**
+   * Full canonical recipient addresses. Only a send writes these: for every other operation the domains are enough,
+   * and storing less is better — but when mail has actually left, "who did it go to" is the first question anyone
+   * asks afterwards, and a domain does not answer it.
+   */
+  recipients?: string[];
+  approvalId?: string;
+  reason?: string;
+  surface?: "cli" | "mcp";
+  /**
+   * The policy that decided how this was approved. Written by change approvals, where it is the whole question
+   * afterwards: a loosening a person typed a code for and one an agent claimed after a yes in chat look the same in
+   * the configuration, and only this line tells them apart.
+   */
+  policy?: SendPolicy;
+}
+/** Large id lists are condensed so every audit line stays small enough to be appended atomically. */
+interface CondensedIds {
+  count: number;
+  sha256: string;
+  first: string[];
+}
+declare class AuditLog {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string, now?: () => Date);
+  append(record: Omit<AuditRecord, "at"> & {
+    at?: string;
+  }, options?: {
+    durable?: boolean;
+  }): Promise<AuditRecord>;
+  /** The most recent records, newest last, optionally filtered by inbox and a lower time bound. */
+  tail(options?: {
+    limit?: number;
+    inbox?: string;
+    since?: string;
+  }): Promise<AuditRecord[]>;
 }
-declare const ZodCodec: $constructor<ZodCodec>;
-declare function codec<const A extends SomeType, B extends SomeType = $ZodType>(in_: A, out: B, params: {
-  decode: (value: output$1<A>, payload: ParsePayload<output$1<A>>) => MaybeAsync<input$1<B>>;
-  encode: (value: input$1<B>, payload: ParsePayload<input$1<B>>) => MaybeAsync<output$1<A>>;
-}): ZodCodec<A, B>;
-declare function invertCodec<A extends SomeType, B extends SomeType>(codec: ZodCodec<A, B>): ZodCodec<B, A>;
-interface ZodPreprocess<B extends SomeType = $ZodType, I = unknown> extends ZodPipe<$ZodTransform<unknown, I>, B>, $ZodPreprocess<B, I> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  _zod: $ZodPreprocessInternals<B, I>;
-  def: $ZodPreprocessDef<B, I>;
+//#endregion
+//#region src/ledger.d.ts
+interface Caps {
+  perHour: number;
+  perDay: number;
+}
+interface CapStatus {
+  hour: number;
+  day: number;
+  /** When the next slot frees up, if a cap is reached. */
+  resetAt?: string;
+}
+declare class SendLedger {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string, now?: () => Date);
+  /** Counts sends (including in-flight reservations) in the last hour and day. */
+  status(inboxId: string, caps: Caps): Promise<CapStatus>;
+  /** Reserves a slot or refuses with APPROVAL_REQUIRED and the time the cap resets. Atomic across processes. */
+  reserve(inboxId: string, approvalId: string, caps: Caps): Promise<CapStatus>;
+  /** Releases a reservation whose send did not happen. */
+  release(inboxId: string, approvalId: string): Promise<void>;
 }
-declare const ZodPreprocess: $constructor<ZodPreprocess>;
-interface ZodReadonly<T extends SomeType = $ZodType> extends _ZodType<$ZodReadonlyInternals<T>>, $ZodReadonly<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+//#endregion
+//#region src/plans.d.ts
+/**
+ * Bulk mailbox changes (more than 20 messages, anything driven by a query, and every trash) are two-step: a dry run
+ * returns a plan token bound to the exact set of ids and the exact change; executing requires that token, once, within
+ * ten minutes. The ids are resolved at dry-run time, so a query cannot silently grow between preview and execution.
+ */
+interface PlanRecord {
+  token: string;
+  inboxId: string;
+  operation: string;
+  /** Digest of the operation parameters (labels added/removed, archive, trash…). */
+  paramsDigest: string;
+  /** Digest of the sorted id list. */
+  idsDigest: string;
+  count: number;
+  createdAt: string;
+  expiresAt: string;
+}
+declare class PlanStore {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string, now?: () => Date);
+  create(input: {
+    inboxId: string;
+    operation: string;
+    params: unknown;
+    ids: readonly string[];
+  }): Promise<PlanRecord>;
+  /**
+   * Consumes a plan exactly once. It must be for the same inbox, operation, parameters and ids; the file is deleted
+   * inside the lock, so a second consume fails.
+   */
+  consume(token: string, expected: {
+    inboxId: string;
+    operation: string;
+    params: unknown;
+    ids: readonly string[];
+  }): Promise<PlanRecord>;
 }
-declare const ZodReadonly: $constructor<ZodReadonly>;
-declare function readonly<T extends SomeType>(innerType: T): ZodReadonly<T>;
-interface ZodTemplateLiteral<Template extends string = string> extends _ZodType<$ZodTemplateLiteralInternals<Template>>, $ZodTemplateLiteral<Template> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
+//#endregion
+//#region src/secrets.d.ts
+/**
+ * Where refresh tokens, client secrets and approval keys live. Two backends, chosen per inbox or client and recorded
+ * in config; the choice is never switched at runtime and there is no silent fallback from one to the other.
+ *
+ * - `keychain`: the OS store (macOS Keychain, Windows Credential Manager, Linux Secret Service — pinned, never the
+ *   kernel keyring, which forgets everything on reboot) through the optional `@napi-rs/keyring` package.
+ * - `file`: one owner-only JSON file per secret in an owner-only directory. Chosen explicitly, never by default.
+ */
+type SecretStoreKind = "keychain" | "file";
+interface SecretStore {
+  readonly kind: SecretStoreKind;
+  get(ref: string): Promise<string | null>;
+  set(ref: string, value: string): Promise<void>;
+  delete(ref: string): Promise<boolean>;
+  /** Forgets any cached value, so the next read goes to the backend (e.g. after another process re-authorised). */
+  invalidate(ref: string): void;
+  /**
+   * Resolves once no earlier call is still occupying the backend. Absent on a store with nothing to wait for.
+   *
+   * For a caller that must not give up on a write: the keychain fails every call fast while a timed-out native call
+   * is still held by an OS dialog, so retrying on a timer spends every attempt against the same stuck call. A
+   * refresh that has already spent Slack's single-use token is that caller — it has one value it cannot get again,
+   * and waiting for the dialog to be answered is the only retry that can succeed.
+   */
+  settled?(): Promise<void>;
 }
-declare const ZodTemplateLiteral: $constructor<ZodTemplateLiteral>;
-declare function templateLiteral<const Parts extends $ZodTemplateLiteralPart[]>(parts: Parts, params?: string | $ZodTemplateLiteralParams): ZodTemplateLiteral<$PartsToTemplateLiteral<Parts>>;
-interface ZodLazy<T extends SomeType = $ZodType> extends _ZodType<$ZodLazyInternals<T>>, $ZodLazy<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+//#endregion
+//#region src/state.d.ts
+/**
+ * Per-inbox runtime facts that any process may update (last successful refresh, last use, health). Kept out of
+ * config.json so a running server never rewrites user intent — a stale in-memory copy of config written back by a
+ * server could otherwise silently undo a policy the user just tightened.
+ */
+interface InboxRuntimeState {
+  lastRefreshOkAt?: string | undefined;
+  lastUsedAt?: string | undefined;
+  /** Set to `undefined` to clear it: the merged value is dropped when the file is written. */
+  lastError?: {
+    code: string;
+    message: string;
+    at: string;
+  } | undefined;
+  grantedScopes?: string[] | undefined;
+  refreshTokenExpiresAt?: string | undefined;
 }
-declare const ZodLazy: $constructor<ZodLazy>;
-declare function lazy<T extends SomeType>(getter: () => T): ZodLazy<T>;
-interface ZodPromise<T extends SomeType = $ZodType> extends _ZodType<$ZodPromiseInternals<T>>, $ZodPromise<T> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  unwrap(): T;
+declare class InboxStateStore {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string);
+  get(inboxId: string): Promise<InboxRuntimeState>;
+  /** Merges `patch` into the stored state under a per-inbox lock. */
+  update(inboxId: string, patch: Partial<InboxRuntimeState>): Promise<InboxRuntimeState>;
 }
-declare const ZodPromise: $constructor<ZodPromise>;
-declare function promise<T extends SomeType>(innerType: T): ZodPromise<T>;
-interface ZodFunction<Args extends $ZodFunctionIn = $ZodFunctionIn, Returns extends $ZodFunctionOut = $ZodFunctionOut> extends _ZodType<$ZodFunctionInternals<Args, Returns>>, $ZodFunction<Args, Returns> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
-  _def: $ZodFunctionDef<Args, Returns>;
-  _input: $InferInnerFunctionType<Args, Returns>;
-  _output: $InferOuterFunctionType<Args, Returns>;
-  input<const Items extends TupleItems, const Rest extends $ZodFunctionOut = $ZodFunctionOut>(args: Items, rest?: Rest): ZodFunction<$ZodTuple<Items, Rest>, Returns>;
-  input<NewArgs extends $ZodFunctionIn>(args: NewArgs): ZodFunction<NewArgs, Returns>;
-  input(...args: any[]): ZodFunction<any, Returns>;
-  output<NewReturns extends $ZodType>(output: NewReturns): ZodFunction<Args, NewReturns>;
+/**
+ * A platform identifier that is not an email address: a Slack user or conversation id.
+ *
+ * It carries its scope because, unlike an address, it is not globally unique — `U024BE7LH` names a different person
+ * in every workspace that happens to mint that id. The address store is deliberately cross-inbox, on the reasoning
+ * that a message read in one mailbox can ask for a send from another; that reasoning does not transfer here, and a
+ * store that matched ids across workspaces would flag an unrelated person every time two workspaces collided.
+ *
+ * The id, never the display name. `@sam` is set by the account that bears it and can be changed to `@finance-bot`
+ * between the message being read and the send being checked; the id cannot.
+ */
+interface TaintHandle {
+  /** `slack`. Lower-cased on the way in. */
+  platform: string;
+  /** The workspace or team the id belongs to — a Slack team id. */
+  scope: string;
+  /** `U024BE7LH`, `C0123`, `D0456`. Passed in the platform's own canonical form; core does not know its shape. */
+  id: string;
+}
+type TaintSource = "header" | "body";
+interface TaintObservation {
+  address: string;
+  source: TaintSource;
+  inboxId: string;
+  messageId?: string | undefined;
+}
+/** The same observation for a handle. `inboxId` is the account that did the reading, as it is for an address. */
+interface TaintHandleObservation {
+  handle: TaintHandle;
+  source: TaintSource;
+  inboxId: string;
+  messageId?: string | undefined;
+}
+/** What is never recorded: the user's own addresses and the domains they call internal. */
+interface TaintExclusions {
+  ownAddresses: readonly string[];
+  internalDomains: readonly string[];
+  /**
+   * Handles that are never recorded: the account's own user id, and whoever the caller treats as internal — the
+   * counterpart of `internalDomains`, decided per platform because "internal" means a domain for mail and
+   * workspace membership for Slack, and core should not be the thing that knows the difference.
+   */
+  ownHandles?: readonly TaintHandle[] | undefined;
+}
+interface TaintCheck {
+  address: boolean;
+  domain: boolean;
+}
+declare class TaintStore {
+  #private;
+  readonly directory: string;
+  constructor(stateDir: string, now?: () => Date);
+  /**
+   * Records observations. Throws if it cannot — callers must fail the read rather than return content whose taint
+   * was not recorded.
+   */
+  record(observations: readonly TaintObservation[], exclusions: TaintExclusions, handleObservations?: readonly TaintHandleObservation[]): Promise<void>;
+  /** Whether an address, or its (non-public) domain, was seen in email content in the window — from any inbox. */
+  check(address: string): Promise<TaintCheck>;
+  /**
+   * Whether a handle was seen in message content in the window.
+   *
+   * Only within its own workspace — see `TaintHandle`. There is no second answer to give, the way an address also
+   * carries a domain: two ids sharing a workspace says nothing about either of them.
+   */
+  checkHandle(handle: TaintHandle): Promise<boolean>;
 }
-declare const ZodFunction: $constructor<ZodFunction>;
-declare function _function(): ZodFunction;
-declare function _function<const In extends ReadonlyArray<$ZodType>>(params: {
-  input: In;
-}): ZodFunction<ZodTuple<In, null>, $ZodFunctionOut>;
-declare function _function<const In extends ReadonlyArray<$ZodType>, const Out extends $ZodFunctionOut = $ZodFunctionOut>(params: {
-  input: In;
-  output: Out;
-}): ZodFunction<ZodTuple<In, null>, Out>;
-declare function _function<const In extends $ZodFunctionIn = $ZodFunctionIn>(params: {
-  input: In;
-}): ZodFunction<In, $ZodFunctionOut>;
-declare function _function<const Out extends $ZodFunctionOut = $ZodFunctionOut>(params: {
-  output: Out;
-}): ZodFunction<$ZodFunctionIn, Out>;
-declare function _function<In extends $ZodFunctionIn = $ZodFunctionIn, Out extends $ZodType = $ZodType>(params?: {
-  input: In;
-  output: Out;
-}): ZodFunction<In, Out>;
-interface ZodCustom<O = unknown, I = unknown> extends _ZodType<$ZodCustomInternals<O, I>>, $ZodCustom<O, I> {
-  "~standard": ZodStandardSchemaWithJSON<this>;
+//#endregion
+//#region src/core.d.ts
+/** Everything a provider package needs from the core, wired to one config directory. */
+interface Core {
+  paths: ResolvedPaths;
+  /** The subset of `paths` explicitly pinned by global CLI options. */
+  pathOverrides: Readonly<PathOverrides>;
+  config: ConfigStore;
+  states: InboxStateStore;
+  approvals: ApprovalStore;
+  ledger: SendLedger;
+  plans: PlanStore;
+  taint: TaintStore;
+  audit: AuditLog;
+  /** Opens the config directory's one secret backend (as recorded in config, or `kind` before the first write). */
+  secrets(kind?: SecretStoreKind): Promise<SecretStore>;
+  /**
+   * The commands this process tells a person to run — its own CLI's, core's, another product's — located from the
+   * caller it was opened with (`OpenCoreOptions.caller`), for these folders. Undefined when none was given: then there
+   * is no command to print at all, and anything that asks for one meets the programming error `requireHandoffs` throws —
+   * never a bare name. Every package opens core with its caller.
+   */
+  handoffs?: CliHandoffs | undefined;
 }
-declare const ZodCustom: $constructor<ZodCustom>;
-declare function check<O = unknown>(fn: CheckFn<O>): $ZodCheck<O>;
-declare function custom<O>(fn?: (data: unknown) => unknown, _params?: string | $ZodCustomParams | undefined): ZodCustom<O, O>;
-declare function refine<T>(fn: (arg: NoInfer<T>) => MaybeAsync<unknown>, _params?: string | $ZodCustomParams): $ZodCheck<T>;
-declare function superRefine<T>(fn: (arg: T, payload: $RefinementCtx<T>) => void | Promise<void>, params?: $ZodSuperRefineParams): $ZodCheck<T>;
-declare const describe: typeof describe$1;
-declare const meta: typeof meta$1;
-type ZodInstanceOfParams = Params<ZodCustom, $ZodIssueCustom, "type" | "check" | "checks" | "fn" | "abort" | "error" | "params" | "path">;
-interface ZodInstanceOf<T = unknown> extends ZodCustom<T, T> {
-  properties<Shape extends { [k in keyof T as T[k] extends Function ? never : k]?: $ZodType<unknown, T[k]>; }>(shape: Shape, params?: string | $ZodCheckPropertiesParams): ZodInstanceOf<T & $InferObjectInput<Shape, {}>>;
+//#endregion
+//#region src/caller.d.ts
+/** This package's name, as its manifest has it. */
+export declare const PACKAGE_NAME = "@agentcomms/whatsapp";
+//#endregion
+//#region ../../node_modules/.pnpm/@modelcontextprotocol+server@2.0.0/node_modules/@modelcontextprotocol/server/dist/types-DUs7mGBv.d.mts
+//#region ../../node_modules/.pnpm/json-schema-typed@8.0.2/node_modules/json-schema-typed/draft_2020_12.d.ts
+type MaybeReadonlyArray<T> = Array<T> | ReadonlyArray<T>;
+type ValueOf<T> = T[keyof T];
+/**
+ * JSON Schema [Draft 2020-12](https://json-schema.org/draft/2020-12/json-schema-validation.html)
+ */
+type JSONSchema<Value = any, SchemaType = (Value extends boolean ? "boolean" : Value extends null ? "null" : Value extends number ? "number" | "integer" : Value extends string ? "string" : Value extends unknown[] ? "array" : Value extends Record<string | number, unknown> ? "object" : JSONSchema.TypeValue)> = boolean | {
+  /**
+   * Using JSON Pointer fragments requires knowledge of the structure of the
+   * schema. When writing schema documents with the intention to provide
+   * re-usable schemas, it may be preferable to use a plain name fragment
+   * that is not tied to any particular structural location.  This allows a
+   * subschema to be relocated without requiring JSON Pointer references to
+   * be updated.
+   *
+   * The `$anchor` keyword is used to specify such a fragment.  It is an
+   * identifier keyword that can only be used to create plain name fragments.
+   *
+   * If present, the value of this keyword MUST be a string, which MUST start
+   * with a letter `[A-Za-z]`, followed by any number of letters, digits
+   * `[0-9]`, hyphens `-`, underscores `_`, colons `:`,
+   * or periods `.`.
+   *
+   * Note that the anchor string does not include the `#` character,
+   * as it is not a URI-reference.  An `{"$anchor": "foo"}` becomes the
+   * fragment `#foo` when used in a URI.
+   *
+   * The base URI to which the resulting fragment is appended is determined
+   * by the `$id` keyword as explained in the previous section.
+   * Two `$anchor` keywords in the same schema document MAY have the same
+   * value if they apply to different base URIs, as the resulting full URIs
+   * will be distinct.  However, the effect of two `$anchor` keywords
+   * with the same value and the same base URI is undefined.  Implementations
+   * MAY raise an error if such usage is detected.
+   */
+  $anchor?: string;
+  /**
+   * This keyword reserves a location for comments from schema authors to
+   * readers or maintainers of the schema.
+   *
+   * The value of this keyword MUST be a string. Implementations MUST NOT
+   * present this string to end users.  Tools for editing schemas SHOULD
+   * support displaying and editing this keyword.  The value of this keyword
+   * MAY be used in debug or error output which is intended for developers
+   * making use of schemas.
+   *
+   * Schema vocabularies SHOULD allow `$comment` within any object
+   * containing vocabulary keywords.  Implementations MAY assume `$comment`
+   * is allowed unless the vocabulary specifically forbids it.  Vocabularies
+   * MUST NOT specify any effect of `$comment` beyond what is described in
+   * this specification.
+   *
+   * Tools that translate other media types or programming languages
+   * to and from `application/schema+json` MAY choose to convert that media
+   * type or programming language's native comments to or from `$comment`
+   * values. The behavior of such translation when both native comments and
+   * `$comment` properties are present is implementation-dependent.
+   *
+   * Implementations MAY strip `$comment` values at any point during
+   * processing. In particular, this allows for shortening schemas when the
+   * size of deployed schemas is a concern.
+   *
+   * Implementations MUST NOT take any other action based on the presence,
+   * absence, or contents of `$comment` properties.  In particular, the
+   * value of `$comment` MUST NOT be collected as an annotation result.
+   */
+  $comment?: string;
+  /**
+   * The `$defs` keyword reserves a location for schema authors to inline
+   * re-usable JSON Schemas into a more general schema. The keyword does not
+   * directly affect the validation result.
+   *
+   * This keyword's value MUST be an object. Each member value of this object
+   * MUST be a valid JSON Schema.
+   */
+  $defs?: Record<string, JSONSchema>;
+  /**
+   * "The `$dynamicAnchor` indicates that the fragment is an extension
+   * point when used with the `$dynamicRef` keyword. This low-level,
+   * advanced feature makes it easier to extend recursive schemas such as the
+   * meta-schemas, without imposing any particular semantics on that
+   * extension. See `$dynamicRef` for more details.
+   */
+  $dynamicAnchor?: string;
+  /**
+   * The `$dynamicRef` keyword is an applicator that allows for deferring
+   * the full resolution until runtime, at which point it is resolved each
+   * time it is encountered while evaluating an instance.
+   *
+   * Together with `$dynamicAnchor`, `$dynamicRef` implements a
+   * cooperative extension mechanism that is primarily useful with recursive
+   * schemas (schemas that reference themselves).  Both the extension point
+   * and the runtime-determined extension target are defined with
+   * `$dynamicAnchor`, and only exhibit runtime dynamic behavior when
+   * referenced with `$dynamicRef`.
+   *
+   * The value of the `$dynamicRef` property MUST be a string which is
+   * a URI-Reference.  Resolved against the current URI base, it produces
+   * the URI used as the starting point for runtime resolution.  This initial
+   * resolution is safe to perform on schema load.
+   *
+   * If the initially resolved starting point URI includes a fragment that
+   * was created by the `$dynamicAnchor` keyword, the initial URI MUST be
+   * replaced by the URI (including the fragment) for the outermost schema
+   * resource in the [dynamic scope][scopes] that defines
+   * an identically named fragment with `$dynamicAnchor`.
+   *
+   * Otherwise, its behavior is identical to `$ref`, and no runtime
+   * resolution is needed.
+   *
+   * [scopes]: https://json-schema.org/draft/2020-12/json-schema-core.html#scopes
+   *
+   * @format "uri-reference"
+   */
+  $dynamicRef?: string;
+  /**
+   * The `$id` keyword identifies a schema resource with its
+   * [canonical][[RFC6596]] URI.
+   *
+   * Note that this URI is an identifier and not necessarily a network
+   * locator. In the case of a network-addressable URL, a schema need not be
+   * downloadable from its canonical URI.
+   *
+   * If present, the value for this keyword MUST be a string, and MUST
+   * represent a valid [URI-reference][RFC3986].  This URI-reference SHOULD
+   * be normalized, and MUST resolve to an [absolute-URI][RFC3986] (without a
+   * fragment).  Therefore, `$id` MUST NOT contain a non-empty fragment,
+   * and SHOULD NOT contain an empty fragment.
+   *
+   * Since an empty fragment in the context of the
+   * `application/schema+json` media type refers to the same resource as
+   * the base URI without a fragment, an implementation MAY normalize a URI
+   * ending with an empty fragment by removing the fragment.  However, schema
+   * authors SHOULD NOT rely on this behavior across implementations.
+   *
+   * This URI also serves as the base URI for relative URI-references in
+   * keywords within the schema resource, in accordance with
+   * [RFC 3986][RFC3986] section 5.1.1 regarding base URIs embedded in
+   * content.
+   *
+   * The presence of `$id` in a subschema indicates that the subschema
+   * constitutes a distinct schema resource within a single schema document.
+   * Furthermore, in accordance with [RFC 3986][RFC3986] section 5.1.2
+   * regarding encapsulating entities, if an `$id` in a subschema is a
+   * relative URI-reference, the base URI for resolving that reference is the
+   * URI of the parent schema resource.
+   *
+   * If no parent schema object explicitly identifies itself as a resource
+   * with `$id`, the base URI is that of the entire document.
+   *
+   * The root schema of a JSON Schema document SHOULD contain an `$id`
+   * keyword with an [absolute-URI][RFC3986] (containing a scheme, but no
+   * fragment).
+   *
+   * [RFC6596]: https://datatracker.ietf.org/doc/html/rfc6596
+   * [RFC3986]: https://datatracker.ietf.org/doc/html/rfc3986
+   *
+   * @format "uri-reference"
+   */
+  $id?: string;
+  /**
+   * The `$ref` keyword is an applicator that is used to reference a
+   * statically identified schema. Its results are the results of the
+   * referenced schema. Other keywords can appear alongside of `$ref` in
+   * the same schema object.
+   *
+   * The value of the `$ref` property MUST be a string which is a
+   * URI-Reference. Resolved against the current URI base, it produces the
+   * URI of the schema to apply.
+   *
+   * @format "uri-reference"
+   */
+  $ref?: string;
+  /**
+   * The `$schema` keyword is both used as a JSON Schema dialect identifier
+   * and as the identifier of a resource which is itself a JSON Schema, which
+   * describes the set of valid schemas written for this particular dialect.
+   *
+   * The value of this keyword MUST be a [URI][RFC3986] (containing a scheme)
+   * and this URI MUST be normalized. The current schema MUST be valid
+   * against the meta-schema identified by this URI.
+   *
+   * If this URI identifies a retrievable resource, that resource SHOULD be
+   * of media type `application/schema+json`.
+   *
+   * The `$schema` keyword SHOULD be used in the document root schema
+   * object, and MAY be used in the root schema objects of embedded schema
+   * resources. It MUST NOT appear in non-resource root schema objects.  If
+   * absent from the document root schema, the resulting behavior is
+   * implementation-defined.
+   *
+   * Values for this property are defined elsewhere in this and other
+   * documents, and by other parties.
+   *
+   * [RFC3986]: https://datatracker.ietf.org/doc/html/rfc3986
+   *
+   * @format "uri"
+   */
+  $schema?: string;
+  /**
+   * The `$vocabulary` keyword is used in meta-schemas to identify the
+   * vocabularies available for use in schemas described by that meta-schema.
+   * It is also used to indicate whether each vocabulary is required or
+   * optional, in the sense that an implementation MUST understand the
+   * required vocabularies in order to successfully process the schema.
+   * Together, this information forms a dialect. Any vocabulary that is
+   * understood by the implementation MUST be processed in a manner
+   * consistent with the semantic definitions contained within the
+   * vocabulary.
+   *
+   * The value of this keyword MUST be an object.  The property names in the
+   * object MUST be URIs (containing a scheme) and this URI MUST be
+   * normalized. Each URI that appears as a property name identifies a
+   * specific set of keywords and their semantics.
+   *
+   * The URI MAY be a URL, but the nature of the retrievable resource is
+   * currently undefined, and reserved for future use.  Vocabulary authors
+   * MAY use the URL of the vocabulary specification, in a human-readable
+   * media type such as `text/html` or `text/plain`, as the vocabulary
+   * URI.
+   *
+   * The values of the object properties MUST be booleans. If the value is
+   * `true`, then implementations that do not recognize the vocabulary MUST
+   * refuse to process any schemas that declare this meta-schema with
+   * `$schema`.  If the value is `false`, implementations that do not
+   * recognize the vocabulary SHOULD proceed with processing such schemas.
+   * The value has no impact if the implementation understands the
+   * vocabulary.
+   *
+   * Unrecognized keywords SHOULD be ignored.  This remains the case for
+   * keywords defined by unrecognized vocabularies.  It is not currently
+   * possible to distinguish between unrecognized keywords that are defined
+   * in vocabularies from those that are not part of any vocabulary.
+   *
+   * The `$vocabulary` keyword SHOULD be used in the root schema of any
+   * schema document intended for use as a meta-schema.  It MUST NOT appear
+   * in subschemas.
+   *
+   * The `$vocabulary` keyword MUST be ignored in schema documents that are
+   * not being processed as a meta-schema.
+   */
+  $vocabulary?: Record<string, string>;
+  /**
+   * @deprecated `additionalItems` has been deprecated in favor of `prefixItems`
+   * paired with `items`.
+   */
+  additionalItems?: JSONSchema;
+  /**
+   * The value of `additionalProperties` MUST be a valid JSON Schema.
+   *
+   * The behavior of this keyword depends on the presence and annotation
+   * results of `properties` and `patternProperties` within the same
+   * schema object. Validation with `additionalProperties` applies only to
+   * the child values of instance names that do not appear in the annotation
+   * results of either `properties` or `patternProperties`.
+   *
+   * For all such properties, validation succeeds if the child instance
+   * validates against the `additionalProperties` schema.
+   *
+   * The annotation result of this keyword is the set of instance property
+   * names validated by this keyword's subschema. Annotation results for
+   * `additionalProperties` keywords from multiple schemas applied to the
+   * same instance location are combined by taking the union of the sets.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty
+   * schema.
+   *
+   * Implementations MAY choose to implement or optimize this keyword in
+   * another way that produces the same effect, such as by directly checking
+   * the names in `properties` and the patterns in `patternProperties`
+   * against the instance property set.
+   */
+  additionalProperties?: JSONSchema;
+  /**
+   * This keyword's value MUST be a non-empty array. Each item of the array
+   * MUST be a valid JSON Schema.
+   *
+   * An instance validates successfully against this keyword if it validates
+   * successfully against all schemas defined by this keyword's value.
+   */
+  allOf?: MaybeReadonlyArray<JSONSchema<Value, SchemaType>>;
+  /**
+   * This keyword's value MUST be a non-empty array. Each item of the array
+   * MUST be a valid JSON Schema.
+   *
+   * An instance validates successfully against this keyword if it validates
+   * successfully against at least one schema defined by this keyword's
+   * value.
+   */
+  anyOf?: MaybeReadonlyArray<JSONSchema<Value, SchemaType>>;
+  /**
+   * An instance validates successfully against this keyword if its value is
+   * equal to the value of the keyword.
+   *
+   * Use of this keyword is functionally equivalent to the `enum` keyword
+   * with a single value.
+   */
+  const?: Value;
+  /**
+   * The value of this keyword MUST be a valid JSON Schema.
+   *
+   * An array instance is valid against `contains` if at least one of its
+   * elements is valid against the given schema. The subschema MUST be
+   * applied to every array element even after the first match has been
+   * found, in order to collect annotations for use by other keywords.
+   * This is to ensure that all possible annotations are collected.
+   *
+   * Logically, the validation result of applying the value subschema to each
+   * item in the array MUST be OR'ed with `false`, resulting in an overall
+   * validation result.
+   *
+   * This keyword produces an annotation value which is an array of the
+   * indexes to which this keyword validates successfully when applying its
+   * subschema, in ascending order. The value MAY be a boolean `true` if
+   * the subschema validates successfully when applied to every index of the
+   * instance. The annotation MUST be present if the instance array to which
+   * this keyword's schema applies is empty.
+   */
+  contains?: JSONSchema<Value, SchemaType>;
+  /**
+   * If the instance value is a string, this property defines that the
+   * string SHOULD be interpreted as binary data and decoded using the
+   * encoding named by this property. [RFC 2045, Sec 6.1][RFC2045] lists the
+   * possible values for this property.
+   *
+   * The value of this property SHOULD be ignored if the instance described
+   * is not a string.
+   *
+   * If this keyword is absent, but `contentMediaType` is present, this
+   * indicates that the media type could be encoded into `UTF-8` like any
+   * other JSON string value, and does not require additional decoding.
+   *
+   * The value of this property MUST be a string.
+   *
+   * [RFC2045]: https://datatracker.ietf.org/doc/html/rfc2045#section-6.1
+   */
+  contentEncoding?: "7bit" | "8bit" | "base64" | "binary" | "ietf-token" | "quoted-printable" | "x-token";
+  /**
+   * If the instance is a string, this property indicates the media type
+   * of the contents of the string.  If `contentEncoding` is present,
+   * this property describes the decoded string.
+   *
+   * The value of this property must be a media type, as defined by
+   * [RFC 2046][RFC2046]. This property defines the media type of instances
+   * which this schema defines.
+   *
+   * The value of this property SHOULD be ignored if the instance described
+   * is not a string.
+   *
+   * If the `contentEncoding` property is not present, but the instance
+   * value is a string, then the value of this property SHOULD specify a text
+   * document type, and the character set SHOULD be the character set into
+   * which the JSON string value was decoded (for which the default is
+   * Unicode).
+   *
+   * [RFC2046]: https://datatracker.ietf.org/doc/html/rfc2046
+   */
+  contentMediaType?: string;
+  /**
+   * If the instance is a string, and if `contentMediaType` is present,
+   * this property contains a schema which describes the structure of the
+   * string.
+   *
+   * This keyword MAY be used with any media type that can be mapped into
+   * JSON Schema's data model.
+   *
+   * The value of this property MUST be a valid JSON schema. It SHOULD be
+   * ignored if `contentMediaType` is not present.
+   */
+  contentSchema?: JSONSchema<Value, SchemaType>;
+  /**
+   * This keyword can be used to supply a default JSON value associated with
+   * a particular schema. It is RECOMMENDED that a `default` value be valid
+   * against the associated schema.
+   */
+  default?: Value;
+  /**
+   * @deprecated `definitions` has been renamed to `$defs`.
+   */
+  definitions?: Record<string, JSONSchema>;
+  /**
+   * @deprecated `dependencies` has been split into two keywords:
+   * `dependentSchemas` and `dependentRequired`.
+   */
+  dependencies?: Record<string, MaybeReadonlyArray<string> | JSONSchema>;
+  /**
+   * The value of this keyword MUST be an object.  Properties in
+   * this object, if any, MUST be arrays.  Elements in each array,
+   * if any, MUST be strings, and MUST be unique.
+   *
+   * This keyword specifies properties that are required if a specific
+   * other property is present.  Their requirement is dependent on the
+   * presence of the other property.
+   *
+   * Validation succeeds if, for each name that appears in both
+   * the instance and as a name within this keyword's value, every
+   * item in the corresponding array is also the name of a property
+   * in the instance.
+   *
+   * Omitting this keyword has the same behavior as an empty object.
+   */
+  dependentRequired?: Record<string, MaybeReadonlyArray<string>>;
+  /**
+   * This keyword specifies subschemas that are evaluated if the instance is
+   * an object and contains a certain property.
+   *
+   * This keyword's value MUST be an object. Each value in the object MUST be
+   * a valid JSON Schema.
+   *
+   * If the object key is a property in the instance, the entire instance
+   * must validate against the subschema. Its use is dependent on the
+   * presence of the property.
+   *
+   * Omitting this keyword has the same behavior as an empty object.
+   */
+  dependentSchemas?: Record<string, JSONSchema>;
+  /**
+   * The value of this keyword MUST be a boolean.  When multiple occurrences
+   * of this keyword are applicable to a single sub-instance, applications
+   * SHOULD consider the instance location to be deprecated if any occurrence
+   * specifies a `true` value.
+   *
+   * If `deprecated` has a value of boolean `true`, it indicates that
+   * applications SHOULD refrain from usage of the declared property. It MAY
+   * mean the property is going to be removed in the future.
+   *
+   * A root schema containing `deprecated` with a value of `true`
+   * indicates that the entire resource being described MAY be removed in the
+   * future.
+   *
+   * The `deprecated` keyword applies to each instance location to which
+   * the schema object containing the keyword successfully applies.  This can
+   * result in scenarios where every array item or object property is
+   * deprecated even though the containing array or object is not.
+   *
+   * Omitting this keyword has the same behavior as a value of `false`.
+   */
+  deprecated?: boolean;
+  /**
+   * Can be used to decorate a user interface with explanation or information
+   * about the data produced.
+   */
+  description?: string;
+  /**
+   * This keyword's value MUST be a valid JSON Schema.
+   *
+   * When `if` is present, and the instance fails to validate against its
+   * subschema, then validation succeeds against this keyword if the instance
+   * successfully validates against this keyword's subschema.
+   *
+   * This keyword has no effect when `if` is absent, or when the instance
+   * successfully validates against its subschema. Implementations MUST NOT
+   * evaluate the instance against this keyword, for either validation or
+   * annotation collection purposes, in such cases.
+   */
+  else?: JSONSchema<Value, SchemaType>;
+  /**
+   * The value of this keyword MUST be an array. This array SHOULD have at
+   * least one element. Elements in the array SHOULD be unique.
+   *
+   * An instance validates successfully against this keyword if its value is
+   * equal to one of the elements in this keyword's array value.
+   *
+   * Elements in the array might be of any type, including `null`.
+   */
+  enum?: MaybeReadonlyArray<Value>;
+  /**
+   * The value of this keyword MUST be an array. When multiple occurrences of
+   * this keyword are applicable to a single sub-instance, implementations
+   * MUST provide a flat array of all values rather than an array of arrays.
+   *
+   * This keyword can be used to provide sample JSON values associated with a
+   * particular schema, for the purpose of illustrating usage. It is
+   * RECOMMENDED that these values be valid against the associated schema.
+   *
+   * Implementations MAY use the value(s) of `default`, if present, as an
+   * additional example. If `examples` is absent, `default` MAY still be
+   * used in this manner.
+   */
+  examples?: MaybeReadonlyArray<Value>;
+  /**
+   * The value of `exclusiveMaximum` MUST be a number, representing an
+   * exclusive upper limit for a numeric instance.
+   *
+   * If the instance is a number, then the instance is valid only if it has a
+   * value strictly less than (not equal to) `exclusiveMaximum`.
+   */
+  exclusiveMaximum?: number;
+  /**
+   * The value of `exclusiveMinimum` MUST be a number, representing an
+   * exclusive lower limit for a numeric instance.
+   *
+   * If the instance is a number, then the instance is valid only if it has a
+   * value strictly greater than (not equal to) `exclusiveMinimum`.
+   */
+  exclusiveMinimum?: number;
+  /**
+   * Implementations MAY treat `format` as an assertion in addition to an
+   * annotation, and attempt to validate the value's conformance to the
+   * specified semantics.
+   *
+   * The value of this keyword is called a format attribute. It MUST be a
+   * string. A format attribute can generally only validate a given set
+   * of instance types. If the type of the instance to validate is not in
+   * this set, validation for this format attribute and instance SHOULD
+   * succeed. Format attributes are most often applied to strings, but can
+   * be specified to apply to any type.
+   *
+   * Implementations MAY support custom format attributes. Save for agreement
+   * between parties, schema authors SHALL NOT expect a peer implementation
+   * to support such custom format attributes.  An implementation MUST NOT
+   * fail validation or cease processing due to an unknown format attribute.
+   * When treating `format` as an annotation, implementations SHOULD
+   * collect both known and unknown format attribute values.
+   */
+  format?: string;
+  /**
+   * This keyword's value MUST be a valid JSON Schema.
+   *
+   * This validation outcome of this keyword's subschema has no direct effect
+   * on the overall validation result. Rather, it controls which of the
+   * `then` or `else` keywords are evaluated.
+   *
+   * Instances that successfully validate against this keyword's subschema
+   * MUST also be valid against the subschema value of the `then` keyword,
+   * if present.
+   *
+   * Instances that fail to validate against this keyword's subschema MUST
+   * also be valid against the subschema value of the `else` keyword, if
+   * present.
+   *
+   * If annotations are being collected, they are collected
+   * from this keyword's subschema in the usual way, including when the
+   * keyword is present without either `then` or `else`.
+   */
+  if?: JSONSchema<Value, SchemaType>;
+  /**
+   * The value of `items` MUST be a valid JSON Schema.
+   *
+   * This keyword applies its subschema to all instance elements at indexes
+   * greater than the length of the `prefixItems` array in the same schema
+   * object, as reported by the annotation result of that `prefixItems`
+   * keyword.  If no such annotation result exists, `items` applies its
+   * subschema to all instance array elements.
+   *
+   * Note that the behavior of `items` without `prefixItems` is identical
+   * to that of the schema form of `items` in prior drafts.
+   *
+   * When `prefixItems` is present, the behavior of `items` is identical
+   * to the former `additionalItems` keyword.
+   *
+   * If the `items` subschema is applied to any positions within the
+   * instance array, it produces an annotation result of boolean `true`,
+   * indicating that all remaining array elements have been evaluated against
+   * this keyword's subschema.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty
+   * schema.
+   *
+   * Implementations MAY choose to implement or optimize this keyword
+   * in another way that produces the same effect, such as by directly
+   * checking for the presence and size of a `prefixItems` array.
+   */
+  items?: JSONSchema;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * If `contains` is not present within the same schema object, then this
+   * keyword has no effect.
+   *
+   * An instance array is valid against `maxContains` in two ways,
+   * depending on the form of the annotation result of an adjacent
+   * `contains` keyword. The first way is if the annotation result is an
+   * array and the length of that array is less than or equal to the
+   * `maxContains` value. The second way is if the annotation result is a
+   * boolean `true` and the instance array length is less than or equal to
+   * the `maxContains` value.
+   */
+  maxContains?: number;
+  /**
+   * The value of `maximum` MUST be a number, representing an inclusive
+   * upper limit for a numeric instance.
+   *
+   * If the instance is a number, then this keyword validates only if the
+   * instance is less than or exactly equal to `maximum`.
+   */
+  maximum?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * An array instance is valid against `maxItems` if its size is less
+   * than, or equal to, the value of this keyword.
+   *
+   * @minimum 0
+   */
+  maxItems?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * A string instance is valid against this keyword if its length is less
+   * than, or equal to, the value of this keyword.
+   *
+   * The length of a string instance is defined as the number of its
+   * characters as defined by [RFC 8259][RFC8259].
+   *
+   * [RFC8259]: https://datatracker.ietf.org/doc/html/rfc8259
+   *
+   * @minimum 0
+   */
+  maxLength?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * An object instance is valid against `maxProperties` if its number of
+   * `properties` is less than, or equal to, the value of this keyword.
+   *
+   * @minimum 0
+   */
+  maxProperties?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * If `contains` is not present within the same schema object, then this
+   * keyword has no effect.
+   *
+   * An instance array is valid against `minContains` in two ways,
+   * depending on the form of the annotation result of an adjacent
+   * `contains` keyword. The first way is if the annotation result is an
+   * array and the length of that array is greater than or equal to the
+   * `minContains` value. The second way is if the annotation result is a
+   * boolean `true` and the instance array length is greater than or equal
+   * to the `minContains` value.
+   *
+   * A value of `0` is allowed, but is only useful for setting a range
+   * of occurrences from `0` to the value of `maxContains`.  A value of
+   * `0` with no `maxContains` causes `contains` to always pass
+   * validation.
+   *
+   * Omitting this keyword has the same behavior as a value of `1`.
+   *
+   * @default 1
+   */
+  minContains?: number;
+  /**
+   * The value of `minimum` MUST be a number, representing an inclusive
+   * lower limit for a numeric instance.
+   *
+   * If the instance is a number, then this keyword validates only if the
+   * instance is greater than or exactly equal to `minimum`.
+   */
+  minimum?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * An array instance is valid against `minItems` if its size is greater
+   * than, or equal to, the value of this keyword.
+   *
+   * Omitting this keyword has the same behavior as a value of `0`.
+   *
+   * @default 0
+   * @minimum 0
+   */
+  minItems?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * A string instance is valid against this keyword if its length is greater
+   * than, or equal to, the value of this keyword.
+   *
+   * The length of a string instance is defined as the number of its
+   * characters as defined by [RFC 8259][RFC8259].
+   *
+   * Omitting this keyword has the same behavior as a value of `0`.
+   *
+   * [RFC8259]: https://datatracker.ietf.org/doc/html/rfc8259
+   *
+   * @default 0
+   * @minimum 0
+   */
+  minLength?: number;
+  /**
+   * The value of this keyword MUST be a non-negative integer.
+   *
+   * An object instance is valid against `minProperties` if its number of
+   * `properties` is greater than, or equal to, the value of this keyword.
+   *
+   * Omitting this keyword has the same behavior as a value of `0`.
+   *
+   * @default 0
+   * @minimum 0
+   */
+  minProperties?: number;
+  /**
+   * The value of `multipleOf` MUST be a number, strictly greater than
+   * `0`.
+   *
+   * A numeric instance is valid only if division by this keyword's value
+   * results in an integer.
+   *
+   * @exclusiveMinimum 0
+   */
+  multipleOf?: number;
+  /**
+   * This keyword's value MUST be a valid JSON Schema.
+   *
+   * An instance is valid against this keyword if it fails to validate
+   * successfully against the schema defined by this keyword.
+   */
+  not?: JSONSchema<Value, SchemaType>;
+  /**
+   * This keyword's value MUST be a non-empty array. Each item of the array
+   * MUST be a valid JSON Schema.
+   *
+   * An instance validates successfully against this keyword if it validates
+   * successfully against exactly one schema defined by this keyword's value.
+   */
+  oneOf?: MaybeReadonlyArray<JSONSchema<Value, SchemaType>>;
+  /**
+   * The value of this keyword MUST be a string. This string SHOULD be a
+   * valid regular expression, according to the [ECMA-262][ecma262] regular
+   * expression dialect.
+   *
+   * A string instance is considered valid if the regular expression matches
+   * the instance successfully. Recall: regular expressions are not
+   * implicitly anchored.
+   *
+   * [ecma262]: https://www.ecma-international.org/publications-and-standards/standards/ecma-262/
+   *
+   * @format "regex"
+   */
+  pattern?: string;
+  /**
+   * The value of `patternProperties` MUST be an object. Each property name
+   * of this object SHOULD be a valid regular expression, according to the
+   * [ECMA-262][ecma262] regular expression dialect. Each property value of
+   * this object MUST be a valid JSON Schema.
+   *
+   * Validation succeeds if, for each instance name that matches any regular
+   * expressions that appear as a property name in this keyword's value,
+   * the child instance for that name successfully validates against each
+   * schema that corresponds to a matching regular expression.
+   *
+   * The annotation result of this keyword is the set of instance property
+   * names matched by this keyword. Omitting this keyword has the same
+   * assertion behavior as an empty object.
+   *
+   * [ecma262]: https://www.ecma-international.org/publications-and-standards/standards/ecma-262/
+   */
+  patternProperties?: Record<string, JSONSchema>;
+  /**
+   * The value of `prefixItems` MUST be a non-empty array of valid JSON
+   * Schemas.
+   *
+   * Validation succeeds if each element of the instance validates against
+   * the schema at the same position, if any.  This keyword does not
+   * constrain the length of the array.  If the array is longer than this
+   * keyword's value, this keyword validates only the prefix of matching
+   * length.
+   *
+   * This keyword produces an annotation value which is the largest index to
+   * which this keyword applied a subschema.  The value MAY be a boolean
+   * `true` if a subschema was applied to every index of the instance, such
+   * as is produced by the `items` keyword.
+   * This annotation affects the behavior of `items` and
+   * `unevaluatedItems`.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty array.
+   */
+  prefixItems?: MaybeReadonlyArray<JSONSchema> | JSONSchema;
+  /**
+   * The value of `properties` MUST be an object. Each value of this object
+   * MUST be a valid JSON Schema.
+   *
+   * Validation succeeds if, for each name that appears in both the instance
+   * and as a name within this keyword's value, the child instance for that
+   * name successfully validates against the corresponding schema.
+   *
+   * The annotation result of this keyword is the set of instance property
+   * names matched by this keyword.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty
+   * object.
+   */
+  properties?: Record<string, JSONSchema>;
+  /**
+   * The value of `propertyNames` MUST be a valid JSON Schema.
+   *
+   * If the instance is an object, this keyword validates if every property
+   * name in the instance validates against the provided schema.
+   * Note the property name that the schema is testing will always be a
+   * string.
+   *
+   * Omitting this keyword has the same behavior as an empty schema.
+   */
+  propertyNames?: JSONSchema;
+  /**
+   * The value of this keyword MUST be a boolean. When multiple occurrences
+   * of this keyword are applicable to a single sub-instance, the resulting
+   * value MUST be `true` if any occurrence specifies a `true` value, and
+   * MUST be `false` otherwise.
+   *
+   * If `readOnly` has a value of boolean `true`, it indicates that the
+   * value of the instance is managed exclusively by the owning authority,
+   * and attempts by an application to modify the value of this property are
+   * expected to be ignored or rejected by that owning authority.
+   *
+   * An instance document that is marked as `readOnly` for the entire
+   * document MAY be ignored if sent to the owning authority, or MAY result
+   * in an error, at the authority's discretion.
+   *
+   * For example, `readOnly` would be used to mark a database-generated
+   * serial number as read-only.
+   *
+   * This keyword can be used to assist in user interface instance
+   * generation.
+   *
+   * @default false
+   */
+  readOnly?: boolean;
+  /**
+   * The value of this keyword MUST be an array. Elements of this array, if
+   * any, MUST be strings, and MUST be unique.
+   *
+   * An object instance is valid against this keyword if every item in the
+   * array is the name of a property in the instance.
+   *
+   * Omitting this keyword has the same behavior as an empty array.
+   */
+  required?: MaybeReadonlyArray<string>;
+  /**
+   * This keyword's value MUST be a valid JSON Schema.
+   *
+   * When `if` is present, and the instance successfully validates against
+   * its subschema, then validation succeeds against this keyword if the
+   * instance also successfully validates against this keyword's subschema.
+   *
+   * This keyword has no effect when `if` is absent, or when the instance
+   * fails to validate against its subschema. Implementations MUST NOT
+   * evaluate the instance against this keyword, for either validation or
+   * annotation collection purposes, in such cases.
+   */
+  then?: JSONSchema<Value, SchemaType>;
+  /**
+   * Can be used to decorate a user interface with a short label about the
+   * data produced.
+   */
+  title?: string;
+  /**
+   * The value of this keyword MUST be either a string or an array. If it is
+   * an array, elements of the array MUST be strings and MUST be unique.
+   *
+   * String values MUST be one of the six primitive types (`"null"`,
+   * `"boolean"`, `"object"`, `"array"`, `"number"`, or
+   * `"string"`), or `"integer"` which matches any number with a zero
+   * fractional part.
+   *
+   * An instance validates if and only if the instance is in any of the sets
+   * listed for this keyword.
+   */
+  type?: SchemaType;
+  /**
+   * The value of `unevaluatedItems` MUST be a valid JSON Schema.
+   *
+   * The behavior of this keyword depends on the annotation results of
+   * adjacent keywords that apply to the instance location being validated.
+   * Specifically, the annotations from `prefixItems`, `items`, and
+   * `contains`, which can come from those keywords when they are adjacent
+   * to the `unevaluatedItems` keyword. Those three annotations, as well as
+   * `unevaluatedItems`, can also result from any and all adjacent
+   * [in-place applicator][in-place-applicator] keywords.
+   *
+   * If no relevant annotations are present, the `unevaluatedItems`
+   * subschema MUST be applied to all locations in the array.
+   * If a boolean `true` value is present from any of the relevant
+   * annotations, `unevaluatedItems` MUST be ignored.  Otherwise, the
+   * subschema MUST be applied to any index greater than the largest
+   * annotation value for `prefixItems`, which does not appear in any
+   * annotation value for `contains`.
+   *
+   * This means that `prefixItems`, `items`, `contains`, and all
+   * in-place applicators MUST be evaluated before this keyword can be
+   * evaluated. Authors of extension keywords MUST NOT define an in-place
+   * applicator that would need to be evaluated after this keyword.
+   *
+   * If the `unevaluatedItems` subschema is applied to any positions within
+   * the instance array, it produces an annotation result of boolean
+   * `true`, analogous to the behavior of `items`.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty
+   * schema.
+   *
+   * [in-place-applicator]: https://json-schema.org/draft/2020-12/json-schema-core.html#in-place
+   */
+  unevaluatedItems?: JSONSchema;
+  /**
+   * The value of `unevaluatedProperties` MUST be a valid JSON Schema.
+   *
+   * The behavior of this keyword depends on the annotation results of
+   * adjacent keywords that apply to the instance location being validated.
+   * Specifically, the annotations from `properties`,
+   * `patternProperties`, and `additionalProperties`, which can come from
+   * those keywords when they are adjacent to the `unevaluatedProperties`
+   * keyword.  Those three annotations, as well as `unevaluatedProperties`,
+   * can also result from any and all adjacent
+   * [in-place applicator][in-place-applicator] keywords.
+   *
+   * Validation with `unevaluatedProperties` applies only to the child
+   * values of instance names that do not appear in the `properties`,
+   * `patternProperties`, `additionalProperties`, or
+   * `unevaluatedProperties` annotation results that apply to the
+   * instance location being validated.
+   *
+   * For all such properties, validation succeeds if the child instance
+   * validates against the "unevaluatedProperties" schema.
+   *
+   * This means that `properties`, `patternProperties`,
+   * `additionalProperties`, and all in-place applicators MUST be evaluated
+   * before this keyword can be evaluated.  Authors of extension keywords
+   * MUST NOT define an in-place applicator that would need to be evaluated
+   * after this keyword.
+   *
+   * The annotation result of this keyword is the set of instance property
+   * names validated by this keyword's subschema.
+   *
+   * Omitting this keyword has the same assertion behavior as an empty
+   * schema.
+   *
+   * [in-place-applicator]: https://json-schema.org/draft/2020-12/json-schema-core.html#in-place
+   */
+  unevaluatedProperties?: JSONSchema;
+  /**
+   * The value of this keyword MUST be a boolean.
+   *
+   * If this keyword has boolean value `false`, the instance validates
+   * successfully. If it has boolean value `true`, the instance validates
+   * successfully if all of its elements are unique.
+   *
+   * Omitting this keyword has the same behavior as a value of `false`.
+   *
+   * @default false
+   */
+  uniqueItems?: boolean;
+  /**
+   * The value of this keyword MUST be a boolean. When multiple occurrences
+   * of this keyword is applicable to a single sub-instance, the resulting
+   * value MUST be `true` if any occurrence specifies a `true` value, and
+   * MUST be `false` otherwise.
+   *
+   * If `writeOnly` has a value of boolean `true`, it indicates that the
+   * value is never present when the instance is retrieved from the owning
+   * authority. It can be present when sent to the owning authority to update
+   * or create the document (or the resource it represents), but it will not
+   * be included in any updated or newly created version of the instance.
+   *
+   * An instance document that is marked as `writeOnly` for the entire
+   * document MAY be returned as a blank document of some sort, or MAY
+   * produce an error upon retrieval, or have the retrieval request ignored,
+   * at the authority's discretion.
+   *
+   * For example, `writeOnly` would be used to mark a password input field.
+   *
+   * These keywords can be used to assist in user interface instance
+   * generation. In particular, an application MAY choose to use a widget
+   * that hides input values as they are typed for write-only fields.
+   *
+   * @default false
+   */
+  writeOnly?: boolean;
+};
+declare namespace JSONSchema {
+  type TypeValue = ValueOf<TypeName> | TypeName | Array<ValueOf<TypeName> | TypeName> | ReadonlyArray<ValueOf<TypeName> | TypeName>;
+  /**
+   * JSON Schema interface
+   */
+  type Interface<Value = any, SchemaType extends TypeValue = TypeValue> = Exclude<JSONSchema<Value, SchemaType>, boolean>;
+  type Array<T = any> = Pick<Interface<T, "array">, KeywordByType.Any | KeywordByType.Array>;
+  type Boolean = Pick<Interface<boolean, "boolean">, KeywordByType.Any>;
+  type Integer = Pick<Interface<number, "integer">, KeywordByType.Any | KeywordByType.Number>;
+  type Number = Pick<Interface<number, "number">, KeywordByType.Any | KeywordByType.Number>;
+  type Null = Pick<Interface<null, "null">, KeywordByType.Any>;
+  type Object<T = any> = Pick<Interface<T, "object">, KeywordByType.Any | KeywordByType.Object>;
+  type String = Pick<Interface<string, "string">, KeywordByType.Any | KeywordByType.String>;
 }
-declare const ZodInstanceOf: $constructor<ZodInstanceOf>;
-declare function _instanceof<T extends typeof Class>(cls: T, params?: ZodInstanceOfParams): ZodInstanceOf<InstanceType<T>>;
-declare const stringbool: (_params?: string | $ZodStringBoolParams) => ZodCodec<ZodString, ZodBoolean>;
-type _ZodJSONSchema = ZodUnion<[ZodString, ZodNumber, ZodBoolean, ZodNull, ZodArray<ZodJSONSchema>, ZodRecord<ZodString, ZodJSONSchema>]>;
-type _ZodJSONSchemaInternals = _ZodJSONSchema["_zod"];
-interface ZodJSONSchemaInternals extends _ZodJSONSchemaInternals {
-  output: JSONType;
-  input: JSONType;
+declare namespace KeywordByType {
+  type Any = "$anchor" | "$comment" | "$defs" | "$dynamicAnchor" | "$dynamicRef" | "$id" | "$ref" | "$schema" | "$vocabulary" | "allOf" | "anyOf" | "const" | "default" | "definitions" | "deprecated" | "description" | "else" | "enum" | "examples" | "format" | "if" | "not" | "oneOf" | "readOnly" | "then" | "title" | "type" | "writeOnly";
+  type Array = "additionalItems" | "contains" | "items" | "maxContains" | "maxItems" | "minContains" | "minItems" | "prefixItems" | "unevaluatedItems" | "uniqueItems";
+  type Number = "exclusiveMaximum" | "exclusiveMinimum" | "maximum" | "minimum" | "multipleOf";
+  type Object = "additionalProperties" | "dependencies" | "dependentRequired" | "dependentSchemas" | "maxProperties" | "minProperties" | "patternProperties" | "properties" | "propertyNames" | "required" | "unevaluatedProperties";
+  type String = "contentEncoding" | "contentMediaType" | "contentSchema" | "maxLength" | "minLength" | "pattern";
 }
-interface ZodJSONSchema extends _ZodJSONSchema {
-  _zod: ZodJSONSchemaInternals;
+/**
+ * Content encoding strategy enum.
+ *
+ * - [Content-Transfer-Encoding Syntax](https://datatracker.ietf.org/doc/html/rfc2045#section-6.1)
+ * - [7bit vs 8bit encoding](https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit/28531705#28531705)
+ */
+/**
+ * Enum consisting of simple type names for the `type` keyword
+ */
+declare enum TypeName {
+  /**
+   * Value MUST be an array.
+   */
+  Array = "array",
+  /**
+   * Value MUST be a boolean.
+   */
+  Boolean = "boolean",
+  /**
+   * Value MUST be an integer, no floating point numbers are allowed. This is a
+   * subset of the number type.
+   */
+  Integer = "integer",
+  /**
+   * Value MUST be null. Note this is mainly for purpose of being able use union
+   * types to define nullability. If this type is not included in a union, null
+   * values are not allowed (the primitives listed above do not allow nulls on
+   * their own).
+   */
+  Null = "null",
+  /**
+   * Value MUST be a number, floating point numbers are allowed.
+   */
+  Number = "number",
+  /**
+   * Value MUST be an object.
+   */
+  Object = "object",
+  /**
+   * Value MUST be a string.
+   */
+  String = "string"
 }
-declare function json(params?: string | $ZodCustomParams): ZodJSONSchema;
-declare function preprocess<A, U extends SomeType, B = unknown>(fn: (arg: B, ctx: $RefinementCtx) => A, schema: U): ZodPreprocess<U, B>;
 //#endregion
-//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/compat.d.cts
-/** @deprecated Use `z.output<T>` instead. */
-type TypeOf<T> = output$1<T>;
-/** @deprecated Use `z.output<T>` instead. */
-type Infer$1<T> = output$1<T>;
-/** @deprecated Use `z.core.$ZodTypes` instead */
-type ZodFirstPartySchemaTypes = $ZodTypes;
-/** @deprecated Use the raw string literal codes instead, e.g. "invalid_type". */
-declare const ZodIssueCode: {
-  readonly invalid_type: "invalid_type";
-  readonly too_big: "too_big";
-  readonly too_small: "too_small";
-  readonly invalid_format: "invalid_format";
-  readonly not_multiple_of: "not_multiple_of";
-  readonly unrecognized_keys: "unrecognized_keys";
-  readonly invalid_union: "invalid_union";
-  readonly invalid_key: "invalid_key";
-  readonly invalid_element: "invalid_element";
-  readonly invalid_value: "invalid_value";
-  readonly custom: "custom";
-};
-/** @deprecated Use `z.core.$ZodFlattenedError<z.output<T>>` instead; it takes an inferred type, not a schema. */
-type inferFlattenedErrors<T extends $ZodType, U = string> = $ZodFlattenedError<output$1<T>, U>;
-/** @deprecated Use `z.core.$ZodFormattedError<z.output<T>>` instead; it takes an inferred type, not a schema. */
-type inferFormattedError<T extends $ZodType<any, any>, U = string> = $ZodFormattedError<output$1<T>, U>;
-/** Use `z.$brand` instead */
-type BRAND<T extends string | number | symbol = string | number | symbol> = {
-  [$brand]: { [k in T]: true; };
+//#region ../core-internal/src/validators/types.d.ts
+/**
+ * JSON Schema type definition (JSON Schema Draft 2020-12)
+ *
+ * This uses the object form of JSON Schema (excluding boolean schemas).
+ * While `true` and `false` are valid JSON Schemas, this SDK uses the
+ * object form for practical type safety.
+ *
+ * Re-exported from json-schema-typed for convenience.
+ * @see https://json-schema.org/draft/2020-12/json-schema-core.html
+ */
+type JsonSchemaType = JSONSchema.Interface;
+/**
+ * Result of a JSON Schema validation operation
+ */
+type JsonSchemaValidatorResult<T> = {
+  valid: true;
+  data: T;
+  errorMessage: undefined;
+} | {
+  valid: false;
+  data: undefined;
+  errorMessage: string;
 };
-/** @deprecated Use `z.config(params)` instead. */
-declare function setErrorMap(map: $ZodErrorMap): void;
-/** @deprecated Use `z.config()` instead. */
-declare function getErrorMap(): $ZodErrorMap<$ZodIssue> | undefined;
-/** @deprecated Use z.ZodType (without generics) instead. */
-type ZodTypeAny<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
-/** @deprecated Use `z.ZodType` */
-type ZodSchema<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
-/** @deprecated Use `z.ZodType` */
-type Schema<Output = unknown, Input = unknown, Internals extends $ZodTypeInternals<Output, Input> = $ZodTypeInternals<Output, Input>> = ZodType<Output, Input, Internals>;
-/** Included for Zod 3 compatibility */
-type ZodRawShape$1 = $ZodShape;
-/** @deprecated Do not use. Stub definition, only included for zod-to-json-schema compatibility. */
-declare enum ZodFirstPartyTypeKind {}
-//#endregion
-//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/from-json-schema.d.cts
-type JSONSchemaVersion = "draft-2020-12" | "draft-7" | "draft-4" | "openapi-3.0";
-interface FromJSONSchemaParams {
-  defaultTarget?: JSONSchemaVersion;
-  registry?: $ZodRegistry<any>;
-}
 /**
- * Converts a JSON Schema to a Zod schema. This function should be considered semi-experimental. It's behavior is liable to change. */
-declare function fromJSONSchema(schema: JSONSchema | boolean, params?: FromJSONSchemaParams): ZodType;
-//#endregion
-//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/deep-partial.d.cts
-/** Distributes `.partial()` through every object in a schema type, preserving the wrappers around them. */
-type DeepPartial<T extends SomeType> = T extends ZodObject<infer Shape, infer Config> ? ZodObject<{ -readonly [K in keyof Shape]: ZodOptional<DeepPartial<Shape[K]>>; }, Config> : T extends ZodDiscriminatedUnion<infer Options, any> ? ZodUnion<{ -readonly [I in keyof Options]: Options[I] extends SomeType ? DeepPartial<Options[I]> : Options[I]; }> : T extends ZodUnion<infer Options> ? ZodUnion<{ -readonly [I in keyof Options]: Options[I] extends SomeType ? DeepPartial<Options[I]> : Options[I]; }> : T extends ZodArray<infer El> ? ZodArray<DeepPartial<El>> : T extends ZodTuple<infer Items, infer Rest> ? ZodTuple<{ -readonly [K in keyof Items]: Items[K] extends SomeType ? DeepPartial<Items[K]> : Items[K]; }, Rest extends SomeType ? DeepPartial<Rest> : Rest> : T extends ZodIntersection<infer A, infer B> ? ZodIntersection<DeepPartial<A>, DeepPartial<B>> : T extends ZodRecord<infer K, infer V> ? ZodRecord<K, DeepPartial<V>> : T extends ZodMap<infer K, infer V> ? ZodMap<K, DeepPartial<V>> : T extends ZodSet<infer El> ? ZodSet<DeepPartial<El>> : T extends ZodOptional<infer Inner> ? ZodOptional<DeepPartial<Inner>> : T extends ZodNullable<infer Inner> ? ZodNullable<DeepPartial<Inner>> : T extends ZodDefault<infer Inner> ? ZodDefault<DeepPartial<Inner>> : T extends ZodPrefault<infer Inner> ? ZodPrefault<DeepPartial<Inner>> : T extends ZodNonOptional<infer Inner> ? ZodNonOptional<DeepPartial<Inner>> : T extends ZodCatch<infer Inner> ? ZodCatch<DeepPartial<Inner>> : T extends ZodReadonly<infer Inner> ? ZodReadonly<DeepPartial<Inner>> : T extends ZodSuccess<infer Inner> ? ZodSuccess<DeepPartial<Inner>> : T extends ZodPromise<infer Inner> ? ZodPromise<DeepPartial<Inner>> : T extends ZodCodec<infer A, infer B> ? ZodCodec<DeepPartial<A>, DeepPartial<B>> : T extends ZodPreprocess<infer B> ? ZodPreprocess<DeepPartial<B>> : T extends ZodPipe<infer A, infer B> ? ZodPipe<DeepPartial<A>, DeepPartial<B>> : T extends ZodLazy<infer Inner> ? ZodLazy<DeepPartial<Inner>> : T;
-/** Returns a copy of the schema with every nested object's properties made optional. */
-declare function deepPartial<T extends SomeType>(schema: T): DeepPartial<T>;
-//#endregion
-//#region ../../node_modules/.pnpm/zod@4.6.5/node_modules/zod/v4/classic/in-out.d.cts
-type input<T> = input$1<T>;
-type output<T> = output$1<T>;
-/** Returns a copy of the schema with every pipe replaced by its input side. A codec's checks are dropped: they constrain the decoded value the input side never produces. */
-declare function input<T extends $ZodType>(schema: T): ZodType<input$1<T>, input$1<T>>;
-/** Returns a copy of the schema with every pipe replaced by its output side, carrying over the pipe's own checks. */
-declare function output<T extends $ZodType>(schema: T): ZodType<output$1<T>, output$1<T>>;
-declare namespace iso_d_exports {
-  export { ZodISODate, ZodISODateTime, ZodISODuration, ZodISOTime, date$1 as date, datetime, duration, time };
-}
-declare function datetime(params?: string | $ZodISODateTimeParams): ZodISODateTime;
-declare function date$1(params?: string | $ZodISODateParams): ZodISODate;
-declare function time(params?: string | $ZodISOTimeParams): ZodISOTime;
-declare function duration(params?: string | $ZodISODurationParams): ZodISODuration;
-declare namespace coerce_d_exports {
-  export { ZodCoercedBigInt, ZodCoercedBoolean, ZodCoercedDate, ZodCoercedNumber, ZodCoercedString, bigint, boolean, date, number, string };
-}
-interface ZodCoercedString<T = unknown> extends _ZodString<$ZodStringInternals<T>> {}
-declare function string<T = unknown>(params?: string | $ZodStringParams): ZodCoercedString<T>;
-interface ZodCoercedNumber<T = unknown> extends _ZodNumber<$ZodNumberInternals<T>> {}
-declare function number<T = unknown>(params?: string | $ZodNumberParams): ZodCoercedNumber<T>;
-interface ZodCoercedBoolean<T = unknown> extends _ZodBoolean<$ZodBooleanInternals<T>> {}
-declare function boolean<T = unknown>(params?: string | $ZodBooleanParams): ZodCoercedBoolean<T>;
-interface ZodCoercedBigInt<T = unknown> extends _ZodBigInt<$ZodBigIntInternals<T>> {}
-declare function bigint<T = unknown>(params?: string | $ZodBigIntParams): ZodCoercedBigInt<T>;
-interface ZodCoercedDate<T = unknown> extends _ZodDate<$ZodDateInternals<T>> {}
-declare function date<T = unknown>(params?: string | $ZodDateParams): ZodCoercedDate<T>;
-declare namespace external_d_exports {
-  export { $brand, $input, $output, BRAND, CompileOptions, GlobalMeta, INVALID, Infer$1 as Infer, IssueData, JSONType, NEVER, $RefinementCtx as RefinementCtx, SafeExtendShape, Schema, TimePrecision, TypeOf, ZodAny, ZodArray, ZodBase64, ZodBase64URL, ZodBigInt, ZodBigIntFormat, ZodBoolean, ZodCIDRv4, ZodCIDRv6, ZodCUID, ZodCUID2, ZodCatch, ZodCodec, ZodCoercedBigInt, ZodCoercedBoolean, ZodCoercedDate, ZodCoercedNumber, ZodCoercedString, ZodCompileAsyncError, ZodCompileUnsupportedError, ZodCreditCard, ZodCustom, ZodCustomStringFormat, ZodDate, ZodDefault, ZodDiscriminatedUnion, ZodE164, ZodEmail, ZodEmoji, ZodEnum, ZodError, ZodErrorMap, ZodExactOptional, ZodFile, ZodFirstPartySchemaTypes, ZodFirstPartyTypeKind, ZodFlattenedError, ZodFloat32, ZodFloat64, ZodFormattedError, ZodFunction, ZodGUID, ZodIBAN, ZodIPv4, ZodIPv6, ZodISODate, ZodISODateTime, ZodISODuration, ZodISOTime, ZodInstanceOf, ZodInt, ZodInt32, ZodInt64, ZodIntersection, ZodIssue, ZodIssueCode, ZodJSONSchema, ZodJSONSchemaInternals, ZodJWT, ZodKSUID, ZodLazy, ZodLiteral, ZodMAC, ZodMap, ZodNaN, ZodNanoID, ZodNever, ZodNonOptional, ZodNull, ZodNullable, ZodNumber, ZodNumberFormat, ZodObject, ZodOptional, ZodPipe, ZodPrefault, ZodPreprocess, ZodPromise, ZodRawShape$1 as ZodRawShape, ZodReadonly, ZodRealError, ZodRecord, ZodSafeParseError, ZodSafeParseResult, ZodSafeParseSuccess, ZodSchema, ZodSet, ZodStandardSchemaWithJSON, ZodString, ZodStringFormat, ZodSuccess, ZodSymbol, ZodTemplateLiteral, ZodTransform, ZodTuple, ZodType, ZodTypeAny, ZodUInt32, ZodUInt64, ZodULID, ZodURL, ZodUUID, ZodUndefined, ZodUnion, ZodUnknown, ZodVoid, ZodXID, ZodXor, _ZodBigInt, _ZodBoolean, _ZodDate, _ZodNumber, _ZodString, _ZodType, _default, _function, any, array, base64, base64url, bigint$1 as bigint, boolean$1 as boolean, _catch as catch, check, cidrv4, cidrv6, clone, codec, coerce_d_exports as coerce, compile, config, index_d_exports$1 as core, creditCard, cuid, cuid2, currencyCode, custom, date$2 as date, decode, decodeAsync, deepPartial, describe, discriminatedUnion, e164, email, emoji, encode, encodeAsync, _endsWith as endsWith, _enum as enum, exactOptional, file, flattenError, float32, float64, formatError, fromJSONSchema, _function as function, getDiscriminatedOption, getErrorMap, globalRegistry, _gt as gt, _gte as gte, guid, hash, hex, hostname, httpUrl, iban, _includes as includes, output$1 as infer, inferFlattenedErrors, inferFormattedError, input, _instanceof as instanceof, int, int32, int64, intersection, invertCodec, ipv4, ipv6, iso_d_exports as iso, json, jwt, keyof, ksuid, lazy, _length as length, literal, index_d_exports$2 as locales, looseObject, looseRecord, _lowercase as lowercase, _lt as lt, _lte as lte, mac, map, _maxLength as maxLength, _maxSize as maxSize, memoizer, meta, _mime as mime, _minLength as minLength, _minSize as minSize, _multipleOf as multipleOf, nan, nanoid, nativeEnum, _negative as negative, never, _nonnegative as nonnegative, nonoptional, _nonpositive as nonpositive, _normalize as normalize, _null as null, nullable, nullish, number$1 as number, object, optional, output, _overwrite as overwrite, parse, parseAsync, partialRecord, pipe, _positive as positive, prefault, preprocess, prettifyError, promise, _properties as properties, _property as property, readonly, record, refine, _regex as regex, regexes_d_exports as regexes, registry, safeDecode, safeDecodeAsync, safeEncode, safeEncodeAsync, safeParse, safeParseAsync, set, setErrorMap, _size as size, _slugify as slugify, _startsWith as startsWith, strictObject, string$1 as string, stringFormat, stringbool, success, superRefine, symbol, templateLiteral, toJSONSchema, _toLowerCase as toLowerCase, _toUpperCase as toUpperCase, toZod, transform, treeifyError, _trim as trim, tuple, uint32, uint64, ulid, _undefined as undefined, union, unknown, _uppercase as uppercase, url, util_d_exports as util, uuid, uuidv4, uuidv6, uuidv7, validate, validateAsync, _void as void, withParser, xid, xor };
+ * A validator function that validates data against a JSON Schema
+ */
+type JsonSchemaValidator<T> = (input: unknown) => JsonSchemaValidatorResult<T>;
+/**
+ * Provider interface for creating validators from JSON Schemas
+ *
+ * This is the main extension point for custom validator implementations.
+ * Implementations should:
+ * - Support JSON Schema Draft 2020-12 (or be compatible with it)
+ * - Return validator functions that can be called multiple times
+ * - Handle schema compilation/caching internally
+ * - Provide clear error messages on validation failure
+ *
+ * @example
+ * ```ts source="./types.examples.ts#jsonSchemaValidator_implementation"
+ * class MyValidatorProvider implements jsonSchemaValidator {
+ *     getValidator<T>(schema: JsonSchemaType): JsonSchemaValidator<T> {
+ *         // Compile/cache validator from schema
+ *         return (input: unknown) =>
+ *             isValid(schema, input)
+ *                 ? { valid: true, data: input as T, errorMessage: undefined }
+ *                 : { valid: false, data: undefined, errorMessage: 'Error details' };
+ *     }
+ * }
+ * ```
+ */
+interface jsonSchemaValidator {
+  /**
+   * Create a validator for the given JSON Schema
+   *
+   * @param schema - Standard JSON Schema object
+   * @returns A validator function that can be called multiple times
+   */
+  getValidator<T>(schema: JsonSchemaType): JsonSchemaValidator<T>;
 }
 declare namespace index_d_exports {
   export { $brand, $input, $output, BRAND, CompileOptions, GlobalMeta, INVALID, Infer$1 as Infer, IssueData, JSONType, NEVER, $RefinementCtx as RefinementCtx, SafeExtendShape, Schema, TimePrecision, TypeOf, ZodAny, ZodArray, ZodBase64, ZodBase64URL, ZodBigInt, ZodBigIntFormat, ZodBoolean, ZodCIDRv4, ZodCIDRv6, ZodCUID, ZodCUID2, ZodCatch, ZodCodec, ZodCoercedBigInt, ZodCoercedBoolean, ZodCoercedDate, ZodCoercedNumber, ZodCoercedString, ZodCompileAsyncError, ZodCompileUnsupportedError, ZodCreditCard, ZodCustom, ZodCustomStringFormat, ZodDate, ZodDefault, ZodDiscriminatedUnion, ZodE164, ZodEmail, ZodEmoji, ZodEnum, ZodError, ZodErrorMap, ZodExactOptional, ZodFile, ZodFirstPartySchemaTypes, ZodFirstPartyTypeKind, ZodFlattenedError, ZodFloat32, ZodFloat64, ZodFormattedError, ZodFunction, ZodGUID, ZodIBAN, ZodIPv4, ZodIPv6, ZodISODate, ZodISODateTime, ZodISODuration, ZodISOTime, ZodInstanceOf, ZodInt, ZodInt32, ZodInt64, ZodIntersection, ZodIssue, ZodIssueCode, ZodJSONSchema, ZodJSONSchemaInternals, ZodJWT, ZodKSUID, ZodLazy, ZodLiteral, ZodMAC, ZodMap, ZodNaN, ZodNanoID, ZodNever, ZodNonOptional, ZodNull, ZodNullable, ZodNumber, ZodNumberFormat, ZodObject, ZodOptional, ZodPipe, ZodPrefault, ZodPreprocess, ZodPromise, ZodRawShape$1 as ZodRawShape, ZodReadonly, ZodRealError, ZodRecord, ZodSafeParseError, ZodSafeParseResult, ZodSafeParseSuccess, ZodSchema, ZodSet, ZodStandardSchemaWithJSON, ZodString, ZodStringFormat, ZodSuccess, ZodSymbol, ZodTemplateLiteral, ZodTransform, ZodTuple, ZodType, ZodTypeAny, ZodUInt32, ZodUInt64, ZodULID, ZodURL, ZodUUID, ZodUndefined, ZodUnion, ZodUnknown, ZodVoid, ZodXID, ZodXor, _ZodBigInt, _ZodBoolean, _ZodDate, _ZodNumber, _ZodString, _ZodType, _default, _function, any, array, base64, base64url, bigint$1 as bigint, boolean$1 as boolean, _catch as catch, check, cidrv4, cidrv6, clone, codec, coerce_d_exports as coerce, compile, config, index_d_exports$1 as core, creditCard, cuid, cuid2, currencyCode, custom, date$2 as date, decode, decodeAsync, deepPartial, external_d_exports as default, describe, discriminatedUnion, e164, email, emoji, encode, encodeAsync, _endsWith as endsWith, _enum as enum, exactOptional, file, flattenError, float32, float64, formatError, fromJSONSchema, _function as function, getDiscriminatedOption, getErrorMap, globalRegistry, _gt as gt, _gte as gte, guid, hash, hex, hostname, httpUrl, iban, _includes as includes, output$1 as infer, inferFlattenedErrors, inferFormattedError, input, _instanceof as instanceof, int, int32, int64, intersection, invertCodec, ipv4, ipv6, iso_d_exports as iso, json, jwt, keyof, ksuid, lazy, _length as length, literal, index_d_exports$2 as locales, looseObject, looseRecord, _lowercase as lowercase, _lt as lt, _lte as lte, mac, map, _maxLength as maxLength, _maxSize as maxSize, memoizer, meta, _mime as mime, _minLength as minLength, _minSize as minSize, _multipleOf as multipleOf, nan, nanoid, nativeEnum, _negative as negative, never, _nonnegative as nonnegative, nonoptional, _nonpositive as nonpositive, _normalize as normalize, _null as null, nullable, nullish, number$1 as number, object, optional, output, _overwrite as overwrite, parse, parseAsync, partialRecord, pipe, _positive as positive, prefault, preprocess, prettifyError, promise, _properties as properties, _property as property, readonly, record, refine, _regex as regex, regexes_d_exports as regexes, registry, safeDecode, safeDecodeAsync, safeEncode, safeEncodeAsync, safeParse, safeParseAsync, set, setErrorMap, _size as size, _slugify as slugify, _startsWith as startsWith, strictObject, string$1 as string, stringFormat, stringbool, success, superRefine, symbol, templateLiteral, toJSONSchema, _toLowerCase as toLowerCase, _toUpperCase as toUpperCase, toZod, transform, treeifyError, _trim as trim, tuple, uint32, uint64, ulid, _undefined as undefined, union, unknown, _uppercase as uppercase, url, util_d_exports as util, uuid, uuidv4, uuidv6, uuidv7, validate, validateAsync, _void as void, withParser, xid, xor, external_d_exports as z };
@@ -11533,9 +12765,16 @@ interface SourceIo {
  * Accounts are core's (`config.json`'s `accounts`), read through core's `ConfigStore`; the person's chat lists are this
  * package's own file (`lists.ts`). The first read of the configuration in a process moves the spike's accounts in, when
  * there are any (`spike-migration.ts`).
+ *
+ * Core is opened with this package as its caller, so every command this tells a person to run — its own, core's — is
+ * located from here: this Node and this installation's CLI, with the folders of this run pinned, or the sentence saying
+ * there is none (CUE-403; CONTRIBUTING.md, "Telling a person what to run"). `handoffs` makes them.
  */
 interface WhatsAppContextOptions {
+  core?: Core | undefined;
   env?: NodeJS.ProcessEnv | undefined;
+  /** Explicit suite directories, resolved before any store is constructed. */
+  pathOverrides?: PathOverrides | undefined;
   now?: (() => Date) | undefined;
   surface?: "cli" | "mcp" | undefined;
   /**
@@ -11567,6 +12806,9 @@ interface WhatsAppContextOptions {
  * **Pinned** (`agent-whatsapp mcp --account acme/whatsapp`, which `mcp install --account` writes): every call acts on
  * that account, `account` may be left out, any other is refused, and nothing about another account is said — not in
  * the greeting, not in `whatsapp_status`. The pin is held by the account's id, so a rename follows it.
+ *
+ * The greeting names no command (CUE-403): what a person runs is in the result that needs it — `whatsapp_status`'s
+ * `setup`, a refusal's `hint` — located from this installation when it is asked for.
  */
 interface WhatsAppMcpOptions extends WhatsAppContextOptions {}
 interface WhatsAppMcpServer {
@@ -11599,7 +12841,4 @@ export declare function composeDraft(request: {
   text: string;
 }): DraftResult;
 //#endregion
-//#region src/index.d.ts
-export declare const PACKAGE_NAME = "@agentcomms/whatsapp";
-//#endregion
 export type { DraftResult, WhatsAppMcpOptions, WhatsAppMcpServer };