ata-validator

Added

• A validator the build compiled away (fromCompiled around a module written ahead of time, what @ata-project/unplugin puts in place of new Validator(schema)) carries Standard Schema V1 as the runtime Validator does: the same ~standard object, built by lib/standard-schema.js for both, with the same issues, value and published schema. A compiled validator can now be handed to a form library, a router or an RPC layer that reads ~standard. tests/test_compiled_standard.js compares the two.

Fixed

• toStandaloneModule(schema, { coerceTypes }) and toStandaloneModule(validator) for a validator built with coerceTypes or removeAdditional wrote a module that checked the data as it was, so it rejected { id: "5" } where the validator accepts it. The module now runs the validator's pass over the data before the check, as bundleStandalone does since 1.59.0, and refuses where that pass cannot be written into a module. fastify-ata/standalone builds its files through this call.

Measured against 1.59.0

Node 25.2.1, interleaved runs from worktrees of both versions: cold compile, warm compile, hot validation with and without code generation, request costs and Fastify boot all within the noise of repeated runs; standalone module sizes unchanged. The browser runtime bundle grew by 82 bytes gzipped (136,709 to 136,791), the boundary of the shared Standard Schema module.