implementer
ce0d3c0d44
tests/config-schema.test.mjs covers both acceptance criteria: the schema is defined with TypeBox/Ajv (static assertions on the committed package — golden-tuple exact pins, Type.Object schema, Ajv compile, boundary re-exports — each backed by a mutation probe proving non-vacuity) and the schema covers the validated config fields (host, port, databaseUrl, sessionSecret with their constraints). The deterministic probe executes the issue's test plan — 'validate a full config against the TypeBox/Ajv schema' — against the committed schema through Ajv via Node type stripping (no build step), plus the negative cases (missing required field naming sessionSecret, secret too short, unknown property, port bounds, and empty databaseUrl); when the package is built (as in the CI job) it also exercises the compiled validateConfig boundary exactly as the later adapter will consume it.