docs(driver-turso, spec): comments and the D3 entry stop calling syncUrl-under-remote constructed-and-ignored

With the inert floor at 0 the driver constructs-and-ignores nothing the
schemas refuse. The comments beside tursoTransportIssues (spec and mirror),
both section headings, the spec test's block comment, the parity test's
two comments, and the turso-config-transport-mismatch-refused entry's
header comment and reason clause now say what holds since #20200, the
entry's clause put in the past tense. Text only.

Claude-Session: https://claude.ai/code/session_01N8TPEsoJxPsdSdNKGnNGEN
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

packages/drivers/driver-turso/src/spec/turso-config-constructor-parity.test.ts

@@ -10,8 +10,8 @@
  *  3. this package's own `TursoConfigSchema` mirror (`./turso.zod.ts`).
  *
  * The two schemas used to accept every combination below, so a datasource the
- * driver refuses at construction (or constructs and ignores) was accepted at
- * authoring and failed a boot later. Each row states the constructor's verdict
+ * driver refuses at construction (or, until #20200, constructed and ignored)
+ * was accepted at authoring and failed a boot later. Each row states the constructor's verdict
  * and the schemas' verdict, and the test asserts all three against it:
  *
  *  - a row the constructor REFUSES is refused by both schemas, on the key the
@@ -224,7 +224,7 @@ describe('turso config: the constructor, the spec contract and this mirror agree
 
     it(row.refusedOn ? `the spec contract refuses it on \`${row.refusedOn}\`` : 'the spec contract accepts it', () => {
       // Authoring refuses what construction refuses, and nothing it accepts
-      // but the declared-and-ignored keys.
+      // but an `inert` row's declared-and-ignored key (none since #20200).
       expect(Boolean(row.refusedOn)).toBe(row.ctor === 'refuse' || Boolean(row.inert));
       const verdict = schemaVerdict(SpecTursoConfigSchema, row.config);
       expect(verdict.refusedOn, verdict.message).toBe(row.refusedOn);

packages/drivers/driver-turso/src/spec/turso.zod.ts

@@ -82,13 +82,14 @@ const WASM_RETIRED =
   + 'Run `os migrate meta --from 17` to list the mechanical edits for existing sources; apply them by hand.';
 
 // ==========================================================================
-// 2a. Transport coherence — what `new TursoDriver` refuses or ignores
+// 2a. Transport coherence — what `new TursoDriver` refuses
 // ==========================================================================
 //
 // #19977. Each key below parsed on its own, so this mirror accepted
 // combinations the driver in this very package refuses at construction
-// (`VALIDATION_ERROR` / 400), or constructs and ignores. It now refuses them,
-// with the supported spelling in the message. The predicates and the messages
+// (`VALIDATION_ERROR` / 400), or, until #20200, constructed and ignored. It
+// now refuses them, with the supported spelling in the message. The
+// predicates and the messages
 // are the ones `@objectstack/spec`'s own turso contract
 // (`packages/spec/src/data/driver/turso.zod.ts`, `tursoTransportIssues`)
 // carries, byte for byte: the helper is internal to that package and not on
@@ -390,8 +391,8 @@ export const TursoConfigSchema = lazySchema(() => z.object({
         + 'nothing.',
     });
   }
-  // What the driver refuses at construction, or constructs and ignores —
-  // see `tursoTransportIssues` above.
+  // What the driver refuses at construction — see `tursoTransportIssues`
+  // above.
   for (const issue of tursoTransportIssues(cfg)) {
     ctx.addIssue({ code: 'custom', path: [issue.path], message: issue.message });
   }

packages/spec/src/data/driver/turso.test.ts

@@ -197,8 +197,9 @@ describe('TursoConfig.timeout carries its unit (#15680)', () => {
 });
 
 // #19977 — the transport refusals: every combination `new TursoDriver` refuses
-// at construction, plus `syncUrl` under a forced `mode: 'remote'` (which it
-// constructs and ignores), refused at authoring. Asserted on the envelope — the
+// at construction (since #20200 that includes `syncUrl` under a forced
+// `mode: 'remote'`, which it used to construct and ignore), refused at
+// authoring. Asserted on the envelope — the
 // issue code, the key it sits on, and the spelling it prescribes — never on a
 // bare `success: false`, which a schema refusing for some OTHER reason (a
 // credential, a placeholder) would satisfy identically. The driver-local mirror

packages/spec/src/data/driver/turso.zod.ts

@@ -78,34 +78,37 @@ export const TursoTransportModeSchema = z.enum(['local', 'replica', 'remote'])
 export type TursoTransportMode = z.input<typeof TursoTransportModeSchema>;
 
 // ==========================================================================
-// 1b. Transport coherence — what `new TursoDriver` refuses or ignores
+// 1b. Transport coherence — what `new TursoDriver` refuses
 // ==========================================================================
 //
 // #19977. `url`, `syncUrl`, `mode` and `timeoutMs` each parsed on their own,
 // so this shape accepted combinations the driver refuses at construction
-// (`VALIDATION_ERROR` / 400) — or constructs and then ignores. Authoring now
-// refuses exactly those, with the supported spelling in the message:
+// (`VALIDATION_ERROR` / 400) — or, until #20200, constructed and then ignored.
+// Authoring now refuses exactly those, with the supported spelling in the
+// message:
 //
 //  - a local or replica mode (forced by `mode`, or selected by `syncUrl`
 //    beside a `file:` / `:memory:` url, or by a url that is none of those)
 //    on a url its local SQLite engine cannot open: a remote url, or anything
 //    that is not a `file:` url or `:memory:` (a bare path, another scheme);
 //  - a replica on an in-memory url;
 //  - `timeoutMs` beside a `wss://` / `ws://` url in remote mode;
-//  - `syncUrl` under a forced `mode: 'remote'`, which the driver accepts and
-//    then IGNORES: the remote client is built without it, no sync ever runs,
-//    and the driver's sync call fails as not supported while its sync-enabled
-//    check still answers true. That arm has no constructor refusal behind it;
-//    it is refused here because a declared setting that changes nothing is
-//    the shape ADR-0049 does not ship.
+//  - `syncUrl` under a forced `mode: 'remote'`, which the driver used to accept
+//    and then IGNORE: the remote client was built without it, no sync ever
+//    ran, and the driver's sync call failed as not supported while its
+//    sync-enabled check still answered true. It was refused here first,
+//    because a declared setting that changes nothing is the shape ADR-0049
+//    does not ship; since #20200 the constructor refuses it too, in this
+//    arm's own words.
 //
 // The predicates MIRROR the constructor's on `main` (`localEngineDefect`,
 // `refuseWebSocketTimeout` and `detectMode` in
 // `packages/drivers/driver-turso/src/turso-driver.ts`): a scheme matches in
 // any letter case, `:memory:` is matched exactly, and a `file:` url whose path
 // is `:memory:` (or starts `:memory:?`) is in-memory. Nothing the constructor
-// accepts is refused here, the `syncUrl`-under-`mode: 'remote'` arm aside. The
-// url is classified TRIMMED, because
+// accepts is refused here: the one former exception, the
+// `syncUrl`-under-`mode: 'remote'` arm, has been a constructor refusal too
+// since #20200. The url is classified TRIMMED, because
 // both loaders trim it before construction (`resolveTursoUrl` in
 // `@objectstack/service-datasource`); `syncUrl` counts when it is a non-empty
 // string, as `buildTursoDriverConfig` forwards it. The driver-local mirror
@@ -467,8 +470,8 @@ export const TursoConfigSchema = lazySchema(() => strictObject(
           + 'nothing.',
       });
     }
-    // What the driver refuses at construction, or constructs and ignores —
-    // see `tursoTransportIssues` above the shape.
+    // What the driver refuses at construction — see `tursoTransportIssues`
+    // above the shape.
     for (const issue of tursoTransportIssues(cfg)) {
       ctx.addIssue({ code: 'custom', path: [issue.path], message: issue.message });
     }

packages/spec/src/migrations/entries/semantic/18.turso-config-transport-mismatch-refused.ts

@@ -5,10 +5,11 @@ import type { SemanticMigration } from '../../types.js';
 // The AUTHORING half of the turso driver's constructor refusals. The driver
 // refuses these configurations when it is built; this entry records that the
 // datasource contract now refuses them where they are written, together with
-// the one combination the driver builds and then ignores. A structured TODO,
-// not a D2 conversion: which way out an author wants — a remote database, an
-// embedded replica on a local file, or a plain local file — is intent no
-// artifact records.
+// the one combination the driver used to build and then ignore (syncUrl under
+// a forced remote mode), which the constructor refuses too since #20200. A
+// structured TODO, not a D2 conversion: which way out an author wants — a
+// remote database, an embedded replica on a local file, or a plain local
+// file — is intent no artifact records.
 export const entry: SemanticMigration = {
   id: 'turso-config-transport-mismatch-refused',
   // No backticks in `surface` — build-upgrade-guide renders it inside a code
@@ -35,14 +36,16 @@ export const entry: SemanticMigration = {
     '#19977. Each key parsed on its own, so the contract accepted configurations the turso driver '
     + 'refuses when it is built (VALIDATION_ERROR / 400 from the constructor, since the #19893 '
     + 'and #19976 changes) — a datasource published clean and then failed at boot or at test '
-    + 'connection. One more it builds and then ignores: syncUrl under a forced remote mode, where '
-    + 'the remote client is created without it, no sync ever runs and the sync call fails as not '
-    + 'supported while the driver reports sync as enabled (measured on the built driver). '
-    + 'Authoring now refuses exactly the constructor\'s refused set — the same predicates, a '
-    + 'scheme matched in any letter case, the url read trimmed as both datasource loaders hand it '
-    + 'over — plus that ignored key, which is the declared-but-not-enforced shape ADR-0049 does '
-    + 'not ship. Nothing the constructor accepts is refused, that key aside: a forced remote mode '
-    + 'keeps its url unjudged, as the constructor does. Stored datasource rows are not re-parsed '
+    + 'connection. One more it built and then ignored until #20200: syncUrl under a forced remote '
+    + 'mode, where the remote client was created without it, no sync ever ran and the sync call '
+    + 'failed as not supported while the driver reported sync as enabled (measured on the built '
+    + 'driver). Authoring now refuses exactly the constructor\'s refused set — the same predicates, '
+    + 'a scheme matched in any letter case, the url read trimmed as both datasource loaders hand '
+    + 'it over — plus that key, refused at authoring first as the declared-but-not-enforced shape '
+    + 'ADR-0049 does not ship, and by the constructor too since #20200. Nothing the constructor '
+    + 'accepts is refused (at #19977 that key was the one exception; since #20200 there is none): '
+    + 'a forced remote mode keeps its url unjudged, as the constructor does. Stored datasource '
+    + 'rows are not re-parsed '
     + 'when they load, so a stored row still reaches the constructor as written; the constructor '
     + 'refuses the first four shapes there already and, since #20200, also refuses syncUrl under '
     + 'a forced remote mode and sync with no syncUrl when the datasource boots. What changes here '