fix(driver-turso)!: refuse timeout beside a pre-configured client at construction (ADR-0049 enforce-or-remove)
#22559
pr-automation.yml
on: pull_request
Check PR Size
16s
Check Changeset
50s
Auto Label
19s
Annotations
1 notice
|
Check Changeset:
.changeset/driver-turso-supplied-client-timeout-refusal.md#L0
ADR-0087 exemption (no-migration-prescription): An accept-set narrowing performed at the driver constructor: no key, spec symbol, Zod schema, object definition or stored representation is added, removed or renamed — `TursoDriverConfig.timeout` and `TursoDriverConfig.client` keep their names and types, and the published `turso` config schema is untouched (it never declared `client`, which is a live object rather than authorable metadata). What moves is which CONFIGURATIONS `new TursoDriver()` accepts, so `objectstack migrate meta` has nothing to visit and there is no tombstone to mint. The refusal itself names both keys, the mode and both ways out, and which of the two an author wants is authoring intent no ledger line can decide.
|