@maroonedog/luq 2.2.0 → 2.3.0

package/dist/standard-schema/plugin-keyword-map.js

@@ -0,0 +1,93 @@
+"use strict";
+// ===========================================================================
+// L10 src/standard-schema/plugin-keyword-map.ts
+//
+// "This plugin, called with these arguments, means this JSON Schema keyword."
+// The reading direction of keyword-map-*.ts, reusing the correspondence those
+// files already settled rather than inventing a second one.
+//
+// Plugin names are written as STRINGS. Importing the plugins themselves would
+// drag every one of them into the bundle of anyone who emits a schema, which
+// does not fit "you only ship what you used". A test cross-checks each string
+// against the real `plugin.name`, so the names cannot drift without the cost.
+//
+// A plugin that is not listed here cannot be written out. A plugin the user
+// wrote themselves is never listed, so it never can. That is a consequence of
+// the design rather than an oversight, and it surfaces as
+// UnrepresentableRuleError instead of being hidden.
+// ===========================================================================
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PLUGIN_KEYWORDS = void 0;
+const numberAt = (args, index) => typeof args[index] === "number" ? args[index] : Number.NaN;
+/**
+ * A second argument makes `.min(n)` exclusive. The same boundary the
+ * reading direction draws when it maps `exclusiveMinimum`.
+ */
+const boundOf = (inclusive, exclusive) => (args) => ({
+    [args[1] === true ? exclusive : inclusive]: numberAt(args, 0),
+});
+/** A format with no arguments: the name is the `format` value verbatim. */
+const format = (name) => () => ({ format: name });
+exports.PLUGIN_KEYWORDS = Object.freeze({
+    // --- strings ----------------------------------------------------------
+    stringMin: (args) => ({ minLength: numberAt(args, 0) }),
+    stringMax: (args) => ({ maxLength: numberAt(args, 0) }),
+    stringExactLength: (args) => ({
+        minLength: numberAt(args, 0),
+        maxLength: numberAt(args, 0),
+    }),
+    // Draft-07's `pattern` is an ECMA-262 SOURCE string. Flags cannot be
+    // spelled there, and dropping them changes the meaning, so a flagged
+    // RegExp counts as unwritable rather than being silently narrowed.
+    stringPattern: (args) => args[0] instanceof RegExp ? { pattern: args[0].source } : null,
+    stringContentEncoding: (args) => ({ contentEncoding: args[0] }),
+    stringContentMediaType: (args) => ({ contentMediaType: args[0] }),
+    // --- formats (names taken verbatim from the format map) ---------------
+    stringDatetime: format("date-time"),
+    stringDate: format("date"),
+    stringTime: format("time"),
+    stringDuration: format("duration"),
+    stringEmail: format("email"),
+    stringIdnEmail: format("idn-email"),
+    stringHostname: format("hostname"),
+    stringIdnHostname: format("idn-hostname"),
+    stringIpv4: format("ipv4"),
+    stringIpv6: format("ipv6"),
+    // `url` is not a registered JSON Schema format name. Both spellings map
+    // to this plugin on the reading side, but a writer has to pick one, so it
+    // picks the registered `uri`.
+    stringUrl: format("uri"),
+    stringUriReference: format("uri-reference"),
+    stringIri: format("iri"),
+    stringIriReference: format("iri-reference"),
+    stringUriTemplate: format("uri-template"),
+    stringJsonPointer: format("json-pointer"),
+    stringRelativeJsonPointer: format("relative-json-pointer"),
+    stringRegex: format("regex"),
+    uuid: format("uuid"),
+    // --- numbers ----------------------------------------------------------
+    numberMin: boundOf("minimum", "exclusiveMinimum"),
+    numberMax: boundOf("maximum", "exclusiveMaximum"),
+    numberMultipleOf: (args) => ({ multipleOf: numberAt(args, 0) }),
+    numberRange: (args) => ({
+        minimum: numberAt(args, 0),
+        maximum: numberAt(args, 1),
+    }),
+    numberPositive: () => ({ exclusiveMinimum: 0 }),
+    numberNegative: () => ({ exclusiveMaximum: 0 }),
+    // --- arrays -----------------------------------------------------------
+    arrayMinLength: (args) => ({ minItems: numberAt(args, 0) }),
+    arrayMaxLength: (args) => ({ maxItems: numberAt(args, 0) }),
+    arrayUnique: () => ({ uniqueItems: true }),
+    // --- values -----------------------------------------------------------
+    literal: (args) => ({ const: args[0] }),
+    oneOf: (args) => (Array.isArray(args[0]) ? { enum: args[0] } : null),
+    // --- handled by type or presence, adding no keyword -------------------
+    // numberInteger becomes `type: "integer"`, so it feeds the type decision.
+    numberInteger: () => null,
+    required: () => null,
+    optional: () => null,
+    nullable: () => null,
+    // Changes the order things run in, not the set of accepted values.
+    skip: () => null,
+});

package/dist/standard-schema/plugin-keyword-map.mjs

@@ -0,0 +1,90 @@
+// ===========================================================================
+// L10 src/standard-schema/plugin-keyword-map.ts
+//
+// "This plugin, called with these arguments, means this JSON Schema keyword."
+// The reading direction of keyword-map-*.ts, reusing the correspondence those
+// files already settled rather than inventing a second one.
+//
+// Plugin names are written as STRINGS. Importing the plugins themselves would
+// drag every one of them into the bundle of anyone who emits a schema, which
+// does not fit "you only ship what you used". A test cross-checks each string
+// against the real `plugin.name`, so the names cannot drift without the cost.
+//
+// A plugin that is not listed here cannot be written out. A plugin the user
+// wrote themselves is never listed, so it never can. That is a consequence of
+// the design rather than an oversight, and it surfaces as
+// UnrepresentableRuleError instead of being hidden.
+// ===========================================================================
+const numberAt = (args, index) => typeof args[index] === "number" ? args[index] : Number.NaN;
+/**
+ * A second argument makes `.min(n)` exclusive. The same boundary the
+ * reading direction draws when it maps `exclusiveMinimum`.
+ */
+const boundOf = (inclusive, exclusive) => (args) => ({
+    [args[1] === true ? exclusive : inclusive]: numberAt(args, 0),
+});
+/** A format with no arguments: the name is the `format` value verbatim. */
+const format = (name) => () => ({ format: name });
+export const PLUGIN_KEYWORDS = Object.freeze({
+    // --- strings ----------------------------------------------------------
+    stringMin: (args) => ({ minLength: numberAt(args, 0) }),
+    stringMax: (args) => ({ maxLength: numberAt(args, 0) }),
+    stringExactLength: (args) => ({
+        minLength: numberAt(args, 0),
+        maxLength: numberAt(args, 0),
+    }),
+    // Draft-07's `pattern` is an ECMA-262 SOURCE string. Flags cannot be
+    // spelled there, and dropping them changes the meaning, so a flagged
+    // RegExp counts as unwritable rather than being silently narrowed.
+    stringPattern: (args) => args[0] instanceof RegExp ? { pattern: args[0].source } : null,
+    stringContentEncoding: (args) => ({ contentEncoding: args[0] }),
+    stringContentMediaType: (args) => ({ contentMediaType: args[0] }),
+    // --- formats (names taken verbatim from the format map) ---------------
+    stringDatetime: format("date-time"),
+    stringDate: format("date"),
+    stringTime: format("time"),
+    stringDuration: format("duration"),
+    stringEmail: format("email"),
+    stringIdnEmail: format("idn-email"),
+    stringHostname: format("hostname"),
+    stringIdnHostname: format("idn-hostname"),
+    stringIpv4: format("ipv4"),
+    stringIpv6: format("ipv6"),
+    // `url` is not a registered JSON Schema format name. Both spellings map
+    // to this plugin on the reading side, but a writer has to pick one, so it
+    // picks the registered `uri`.
+    stringUrl: format("uri"),
+    stringUriReference: format("uri-reference"),
+    stringIri: format("iri"),
+    stringIriReference: format("iri-reference"),
+    stringUriTemplate: format("uri-template"),
+    stringJsonPointer: format("json-pointer"),
+    stringRelativeJsonPointer: format("relative-json-pointer"),
+    stringRegex: format("regex"),
+    uuid: format("uuid"),
+    // --- numbers ----------------------------------------------------------
+    numberMin: boundOf("minimum", "exclusiveMinimum"),
+    numberMax: boundOf("maximum", "exclusiveMaximum"),
+    numberMultipleOf: (args) => ({ multipleOf: numberAt(args, 0) }),
+    numberRange: (args) => ({
+        minimum: numberAt(args, 0),
+        maximum: numberAt(args, 1),
+    }),
+    numberPositive: () => ({ exclusiveMinimum: 0 }),
+    numberNegative: () => ({ exclusiveMaximum: 0 }),
+    // --- arrays -----------------------------------------------------------
+    arrayMinLength: (args) => ({ minItems: numberAt(args, 0) }),
+    arrayMaxLength: (args) => ({ maxItems: numberAt(args, 0) }),
+    arrayUnique: () => ({ uniqueItems: true }),
+    // --- values -----------------------------------------------------------
+    literal: (args) => ({ const: args[0] }),
+    oneOf: (args) => (Array.isArray(args[0]) ? { enum: args[0] } : null),
+    // --- handled by type or presence, adding no keyword -------------------
+    // numberInteger becomes `type: "integer"`, so it feeds the type decision.
+    numberInteger: () => null,
+    required: () => null,
+    optional: () => null,
+    nullable: () => null,
+    // Changes the order things run in, not the set of accepted values.
+    skip: () => null,
+});

package/dist/standard-schema/split-issue-path.d.ts

@@ -1,9 +1,11 @@
-/** 開いた結果。オブジェクトのキーは string、配列の添字は number。 */
+/** The opened path: object keys as strings, array indices as numbers. */
 export type IssuePathSegments = readonly (string | number)[];
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 export declare function splitIssuePath(path: string): IssuePathSegments;

package/dist/standard-schema/split-issue-path.js

@@ -2,26 +2,28 @@
 // ===========================================================================
 // L10 src/standard-schema/split-issue-path.ts
 //
-// Luq の issue path ("items[1].productId") を Standard Schema の path
-// (["items", 1, "productId"]) に開く。
+// Opens an issue path ("items[1].productId") into the spec's segment list
+// (["items", 1, "productId"]).
 //
-// 方向に注意: これは formatIssuePath の逆で、宣言パス (parseFieldPath が
-// 読む "items[*].productId") のパーサではない。issue path には [*] が
-// 決して現れず、代わりに実インデックスが入る。二つの文法を一つの関数で
-// 扱おうとすると、[*] を 0 と読むような取り違えが静かに入るので分けてある。
+// Mind the direction: this reverses issue-path FORMATTING, and is not a parser
+// for declared paths. An issue path never contains [*] — it carries the real
+// index instead. Handling both grammars in one function is how [*] quietly
+// starts being read as 0, so they are kept apart.
 //
-// 配列インデックスは number として出す。仕様の PropertyKey は
-// string | number | symbol を許し、消費側 (フォームライブラリ) は
-// 添字を number として受け取る前提で書かれているため。
+// Array indices come out as numbers. The spec's PropertyKey allows
+// string | number | symbol, and the consumers — form libraries — are written
+// expecting a number.
 // ===========================================================================
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.splitIssuePath = splitIssuePath;
 const INDEX_PATTERN = /^\[(\d+)\]/;
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 function splitIssuePath(path) {
     if (path === "")
@@ -54,7 +56,7 @@ function splitIssuePath(path) {
     }
     return expectKey ? [path] : segments;
 }
-/** キーは "." か "[" の手前まで。どちらも無ければ末尾まで。 */
+/** A key runs to the next "." or "[", or to the end when there is neither. */
 function findKeyEnd(rest) {
     const dot = rest.indexOf(".");
     const bracket = rest.indexOf("[");

package/dist/standard-schema/split-issue-path.mjs

@@ -1,24 +1,26 @@
 // ===========================================================================
 // L10 src/standard-schema/split-issue-path.ts
 //
-// Luq の issue path ("items[1].productId") を Standard Schema の path
-// (["items", 1, "productId"]) に開く。
+// Opens an issue path ("items[1].productId") into the spec's segment list
+// (["items", 1, "productId"]).
 //
-// 方向に注意: これは formatIssuePath の逆で、宣言パス (parseFieldPath が
-// 読む "items[*].productId") のパーサではない。issue path には [*] が
-// 決して現れず、代わりに実インデックスが入る。二つの文法を一つの関数で
-// 扱おうとすると、[*] を 0 と読むような取り違えが静かに入るので分けてある。
+// Mind the direction: this reverses issue-path FORMATTING, and is not a parser
+// for declared paths. An issue path never contains [*] — it carries the real
+// index instead. Handling both grammars in one function is how [*] quietly
+// starts being read as 0, so they are kept apart.
 //
-// 配列インデックスは number として出す。仕様の PropertyKey は
-// string | number | symbol を許し、消費側 (フォームライブラリ) は
-// 添字を number として受け取る前提で書かれているため。
+// Array indices come out as numbers. The spec's PropertyKey allows
+// string | number | symbol, and the consumers — form libraries — are written
+// expecting a number.
 // ===========================================================================
 const INDEX_PATTERN = /^\[(\d+)\]/;
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 export function splitIssuePath(path) {
     if (path === "")
@@ -51,7 +53,7 @@ export function splitIssuePath(path) {
     }
     return expectKey ? [path] : segments;
 }
-/** キーは "." か "[" の手前まで。どちらも無ければ末尾まで。 */
+/** A key runs to the next "." or "[", or to the end when there is neither. */
 function findKeyEnd(rest) {
     const dot = rest.indexOf(".");
     const bracket = rest.indexOf("[");

package/dist/standard-schema/standard-schema.types.d.ts

@@ -1,4 +1,4 @@
-/** 仕様の StandardSchemaV1。Input と Output を型として運ぶ。 */
+/** The spec's StandardSchemaV1, carrying Input and Output as types. */
 export interface StandardSchemaV1<Input = unknown, Output = Input> {
     readonly "~standard": StandardSchemaProps<Input, Output>;
 }
@@ -7,8 +7,8 @@ export interface StandardSchemaProps<Input = unknown, Output = Input> {
     readonly vendor: string;
     readonly validate: (value: unknown, options?: StandardSchemaOptions | undefined) => StandardSchemaResult<Output> | Promise<StandardSchemaResult<Output>>;
     /**
-     * 実行時には存在しない。型を運ぶためだけのメンバーで、仕様がそう定めている。
-     * InferInput / InferOutput はここから読む。
+     * Absent at run time. The spec defines it as a type-only member, and it is
+     * what InferInput / InferOutput read.
      */
     readonly types?: StandardSchemaTypes<Input, Output> | undefined;
 }
@@ -25,8 +25,9 @@ export interface StandardSchemaFailure {
     readonly issues: readonly StandardSchemaIssue[];
 }
 /**
- * path は仕様上 optional。Luq は必ず入れる (root への issue は空配列)。
- * 省略と「ルートを指す」を呼び出し側が区別できるようにするため。
+ * The spec makes path optional; it is always present here, with an issue on
+ * the root carrying the empty list. That keeps "omitted" distinguishable from
+ * "points at the root" on the consuming side.
  */
 export interface StandardSchemaIssue {
     readonly message: string;
@@ -38,8 +39,8 @@ export interface StandardSchemaPathSegment {
 export type InferStandardInput<Schema extends StandardSchemaV1> = NonNullable<Schema["~standard"]["types"]>["input"];
 export type InferStandardOutput<Schema extends StandardSchemaV1> = NonNullable<Schema["~standard"]["types"]>["output"];
 /**
- * validate の第2引数。仕様が定めているので受ける。
- * libraryOptions はベンダーごとの追加パラメータで、Luq はまだ何も定義していない。
+ * validate's second parameter, declared because the spec defines it.
+ * libraryOptions is the per-vendor extension point, and none is defined yet.
  */
 export interface StandardSchemaOptions {
     readonly libraryOptions?: Record<string, unknown> | undefined;

package/dist/standard-schema/standard-schema.types.js

@@ -2,12 +2,12 @@
 // ===========================================================================
 // L10 src/standard-schema/standard-schema.types.ts
 //
-// Standard Schema v1 の型を自前で宣言する。@standard-schema/spec に依存しない。
-// 仕様が「型だけのパッケージなので inline してよい」と明示しており、依存を
-// 足せば利用者の node_modules に1つ増える一方で、得るものは何も無いため。
-// 形が仕様からずれていないことは test/type/standard-schema/ が固定する。
+// Declares the Standard Schema v1 types here rather than depending on the
+// spec package. The spec explicitly permits inlining, being types only, and a
+// dependency would add an entry to every user's node_modules for nothing.
+// Type tests pin the shape against the spec so it cannot drift.
 //
-// この層が L10 なのは、Validator (L6) の上に載る変換であり、コアの誰も
-// これを import しないから。import の向きは L6 -> L10 ではなく L10 -> L6。
+// This is the outermost layer because it is a view laid over the validator and
+// nothing in the core imports it. The import direction runs inwards only.
 // ===========================================================================
 Object.defineProperty(exports, "__esModule", { value: true });

package/dist/standard-schema/standard-schema.types.mjs

@@ -1,12 +1,12 @@
 // ===========================================================================
 // L10 src/standard-schema/standard-schema.types.ts
 //
-// Standard Schema v1 の型を自前で宣言する。@standard-schema/spec に依存しない。
-// 仕様が「型だけのパッケージなので inline してよい」と明示しており、依存を
-// 足せば利用者の node_modules に1つ増える一方で、得るものは何も無いため。
-// 形が仕様からずれていないことは test/type/standard-schema/ が固定する。
+// Declares the Standard Schema v1 types here rather than depending on the
+// spec package. The spec explicitly permits inlining, being types only, and a
+// dependency would add an entry to every user's node_modules for nothing.
+// Type tests pin the shape against the spec so it cannot drift.
 //
-// この層が L10 なのは、Validator (L6) の上に載る変換であり、コアの誰も
-// これを import しないから。import の向きは L6 -> L10 ではなく L10 -> L6。
+// This is the outermost layer because it is a view laid over the validator and
+// nothing in the core imports it. The import direction runs inwards only.
 // ===========================================================================
 export {};

package/dist/standard-schema/to-standard-json-schema.d.ts

@@ -0,0 +1,19 @@
+import type { Validator } from "../builder/validator.types";
+import { type StandardLuqSchema } from "./to-standard-schema";
+/** The spec's Options: target is required, libraryOptions is vendor-defined. */
+export interface JsonSchemaOptions {
+    readonly target: string;
+    readonly libraryOptions?: Record<string, unknown> | undefined;
+}
+interface JsonSchemaConverter {
+    readonly input: (options: JsonSchemaOptions) => Record<string, unknown>;
+    readonly output: (options: JsonSchemaOptions) => Record<string, unknown>;
+}
+/** A `~standard` carrying both validate and jsonSchema. */
+export type StandardJsonSchemaLuqSchema<T extends object, TParsed = T> = StandardLuqSchema<T, TParsed> & {
+    readonly "~standard": StandardLuqSchema<T, TParsed>["~standard"] & {
+        readonly jsonSchema: JsonSchemaConverter;
+    };
+};
+export declare function toStandardJsonSchema<T extends object, TParsed = T>(validator: Validator<T, TParsed>): StandardJsonSchemaLuqSchema<T, TParsed>;
+export {};

package/dist/standard-schema/to-standard-json-schema.js

@@ -0,0 +1,36 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.toStandardJsonSchema = toStandardJsonSchema;
+const declared_calls_store_1 = require("../builder/declared-calls-store");
+const assemble_json_schema_1 = require("./assemble-json-schema");
+const json_schema_target_1 = require("./json-schema-target");
+const declarations_unavailable_error_1 = require("./declarations-unavailable-error");
+const unrepresentable_rule_error_1 = require("./unrepresentable-rule-error");
+const to_standard_schema_1 = require("./to-standard-schema");
+const declaration_recorder_1 = require("./declaration-recorder");
+// At module scope, not inside the export: this has to be in place before any
+// build() runs, and a chain that already ran cannot be asked again.
+(0, declaration_recorder_1.installJsonSchemaDeclarationRecorder)();
+function toStandardJsonSchema(validator) {
+    const declared = (0, declared_calls_store_1.readDeclaredCalls)(validator);
+    const emit = (options) => {
+        // Refuse an unsupported target before writing anything. Same order even
+        // when there is nothing to write, or a wrong target passes as an empty
+        // schema instead of an error.
+        const schemaUri = (0, json_schema_target_1.resolveJsonSchemaTarget)(options.target);
+        if (declared === undefined)
+            throw new declarations_unavailable_error_1.DeclarationsUnavailableError();
+        return {
+            $schema: schemaUri,
+            ...(0, assemble_json_schema_1.assembleJsonSchema)(declared, (0, unrepresentable_rule_error_1.readUnrepresentablePolicy)(options.libraryOptions)),
+        };
+    };
+    const standard = (0, to_standard_schema_1.toStandardSchema)(validator);
+    return {
+        ...standard,
+        "~standard": {
+            ...standard["~standard"],
+            jsonSchema: { input: emit, output: emit },
+        },
+    };
+}

package/dist/standard-schema/to-standard-json-schema.mjs

@@ -0,0 +1,33 @@
+import { readDeclaredCalls } from "../builder/declared-calls-store.mjs";
+import { assembleJsonSchema } from "./assemble-json-schema.mjs";
+import { resolveJsonSchemaTarget } from "./json-schema-target.mjs";
+import { DeclarationsUnavailableError } from "./declarations-unavailable-error.mjs";
+import { readUnrepresentablePolicy } from "./unrepresentable-rule-error.mjs";
+import { toStandardSchema } from "./to-standard-schema.mjs";
+import { installJsonSchemaDeclarationRecorder } from "./declaration-recorder.mjs";
+// At module scope, not inside the export: this has to be in place before any
+// build() runs, and a chain that already ran cannot be asked again.
+installJsonSchemaDeclarationRecorder();
+export function toStandardJsonSchema(validator) {
+    const declared = readDeclaredCalls(validator);
+    const emit = (options) => {
+        // Refuse an unsupported target before writing anything. Same order even
+        // when there is nothing to write, or a wrong target passes as an empty
+        // schema instead of an error.
+        const schemaUri = resolveJsonSchemaTarget(options.target);
+        if (declared === undefined)
+            throw new DeclarationsUnavailableError();
+        return {
+            $schema: schemaUri,
+            ...assembleJsonSchema(declared, readUnrepresentablePolicy(options.libraryOptions)),
+        };
+    };
+    const standard = toStandardSchema(validator);
+    return {
+        ...standard,
+        "~standard": {
+            ...standard["~standard"],
+            jsonSchema: { input: emit, output: emit },
+        },
+    };
+}

package/dist/standard-schema/to-standard-schema.d.ts

@@ -1,22 +1,22 @@
 import type { Validator } from "../builder/validator.types";
 import type { StandardSchemaOptions, StandardSchemaResult } from "./standard-schema.types";
 /**
- * 仕様の Props は validate が Promise を返すことも許すが、Luq は必ず同期で返す。
- * ここで同期に絞っておくと、消費側が `await` も型の絞り込みも書かずに済む。
- * 狭めた型は広い型に代入できるので、StandardSchemaV1 としての互換は保たれる
- * (test/type/standard-schema/ の AssignableToSpec がそれを固定している)。
+ * The spec allows validate to return a Promise; this one never does. Pinning
+ * it to synchronous here spares consumers both the `await` and the narrowing.
+ * A narrower type is still assignable to the wider one, so compatibility with
+ * StandardSchemaV1 holds — and a type test pins that.
  */
 interface SynchronousStandardProps<T extends object, TParsed> {
     readonly version: 1;
     readonly vendor: string;
     /**
-     * 第2引数 options は仕様にある。Luq は今のところ読まないが、**受けること
-     * 自体に意味がある**: 引数の少ない関数は多い方に代入できてしまうので、
-     * 書かないと「仕様に合っている」と型が言うのに消費側の options が黙って
-     * 捨てられる。受けた上で無視しているのだと分かる形にしてある。
+     * The second parameter is in the spec and is deliberately declared even
+     * though nothing reads it yet. **Declaring it is the point**: a function
+     * with fewer parameters is assignable to one with more, so leaving it out
+     * would let the type claim conformance while a consumer's options were
+     * silently discarded. Written this way, ignoring them is visible.
      *
-     * libraryOptions に何を入れるかはベンダーごとの取り決めで、Luq はまだ
-     * 何も定義していない。定義したらここで読む。
+     * What goes in libraryOptions is per-vendor, and none is defined yet.
      */
     readonly validate: (value: unknown, options?: StandardSchemaOptions | undefined) => StandardSchemaResult<TParsed>;
     readonly types?: {
@@ -25,17 +25,18 @@ interface SynchronousStandardProps<T extends object, TParsed> {
     } | undefined;
 }
 /**
- * Standard Schema としての Luq バリデータ。
+ * A Luq validator seen as a Standard Schema.
  *
- * Input は `.for<T>()` に渡した型、Output は transform 適用後の型。
- * 推論ではなく宣言から来るので、InferInput が利用者の書いた型そのものを指す。
+ * Input is the type given to `.for<T>()`; Output is that type after
+ * transforms. Both come from the declaration rather than from inference, so
+ * InferInput names the very type the caller wrote.
  */
 export type StandardLuqSchema<T extends object, TParsed = T> = Validator<T, TParsed> & {
     readonly "~standard": SynchronousStandardProps<T, TParsed>;
 };
 /**
- * 元の Validator のメンバー (validate / parse / pick / pickAll) はそのまま残る。
- * 返り値は Validator でもあるので、片方のためにもう片方を諦める必要は無い。
+ * The original validator's members stay. What comes back is still a
+ * Validator, so neither face has to be given up for the other.
  */
 export declare function toStandardSchema<T extends object, TParsed = T>(validator: Validator<T, TParsed>): StandardLuqSchema<T, TParsed>;
 export {};

package/dist/standard-schema/to-standard-schema.js

@@ -2,21 +2,20 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.toStandardSchema = toStandardSchema;
 const split_issue_path_1 = require("./split-issue-path");
-/** package.json の name と揃える。消費側がエラー表示に使う。 */
+/** Matches the package name. Consumers show it in error output. */
 const VENDOR = "luq";
 const COLLECT_EVERY_ISSUE = {
     abortEarly: false,
     abortEarlyOnEachField: false,
 };
 /**
- * 元の Validator のメンバー (validate / parse / pick / pickAll) はそのまま残る。
- * 返り値は Validator でもあるので、片方のためにもう片方を諦める必要は無い。
+ * The original validator's members stay. What comes back is still a
+ * Validator, so neither face has to be given up for the other.
  */
 function toStandardSchema(validator) {
-    // アサーションを書かずに組み立てる。src/core/type-erasure.ts が
-    // 「型を破ってよい唯一の場所」で、ここはその場所ではない。
-    // 各メンバーを明示的に写すので、Validator に新しいメンバーが増えたときは
-    // ここがコンパイルエラーになる — 黙って落ちるより良い。
+    // Assembled without a type assertion; this is not a file allowed to write
+    // one. Copying each member by name means a new member on Validator breaks
+    // the build here, which beats being dropped in silence.
     const props = {
         version: 1,
         vendor: VENDOR,
@@ -36,25 +35,19 @@ function toStandardSchema(validator) {
     };
 }
 /**
- * code と severity は仕様に置き場所が無いので落ちる。message は Luq が
- * 組み立て済みのものをそのまま渡す。
+ * code and severity have nowhere to go in the spec, so they are dropped. The
+ * message is passed through as already composed.
  */
 function toStandardIssue(issue) {
     return { message: issue.message, path: (0, split_issue_path_1.splitIssuePath)(issue.path) };
 }
 // ---------------------------------------------------------------------------
-// なぜコアの build() が ~standard を常に生やさないのか（実測に基づく判断）
+// Why build() does not simply put ~standard on every validator.
 //
-//   core-only                      gzip  7,420 B
-//   core + standard-schema         gzip  7,732 B   (+312 B)
-//   six-plugin                     gzip  8,373 B
-//   six-plugin + standard-schema   gzip  8,692 B   (+319 B)
-//
-// コアに同梱すると、Standard Schema を使わない利用者も 312 B を払う。中核が
-// 7,420 B なので 4.2% にあたり、「使った分しか入らない」という約束と噛み合わない。
-// サブパスにしておけば import しない限り 0 B で、tRPC などに渡したい人だけが払う。
-//
-// 代償は、利用者が toStandardSchema() で1回包む必要があること。build() が
-// 直接 ~standard を持つほうが体験は良いが、その体験のために全員に課金する形に
-// なるので取らなかった。将来コアに入れるなら、この 312 B が判断材料になる。
+// It would be the nicer experience — no wrapping call — but it bills everyone
+// for it, including the majority who never hand a validator to a spec
+// consumer. Measured against the core bundle the surcharge was a few percent,
+// which does not fit "you only ship what you used". As a subpath it costs
+// nothing until imported. Re-measure before revisiting the decision; the
+// figures live with the size budget, not here.
 // ---------------------------------------------------------------------------