docs(driver-turso): the replica arm's sync is not cancelled, and the mirror does not declare mode (#16024)

Two prose repairs the contract review raised as non-blocking; no behaviour and
no schema changes.

- packages/drivers/driver-turso/README.md — the README named both arms and the
  WebSocket gap but dropped the clause `turso-driver.ts`'s docblock and the
  changeset both carry: on the replica arm the native binding's own sync is not
  cancelled, only no longer awaited. Wording matched to the docblock.

- docs/design/driver-turso.md §10 — "Both declare exactly the keys the driver
  reads" overstated: the package-published mirror does not declare `mode`,
  which `TursoDriver.detectMode` reads. The sentence now claims only the
  direction ADR-0049 governs (no declared key the driver does not read) and
  names the gap. The gap itself is pre-existing and deliberately left alone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ADLdAs2pVcH17h9tZKWMBg

Author: claude

docs/design/driver-turso.md

@@ -513,9 +513,11 @@ packages/plugins/driver-turso/
 `TursoConfigSchema` exists twice on purpose: the authoring contract in
 `packages/spec/src/data/driver/turso.zod.ts` (strict — what a `datasource` may declare), and the
 package-published Spec / Studio mirror in `packages/drivers/driver-turso/src/spec/turso.zod.ts`.
-Both declare exactly the keys the driver reads (ADR-0049 enforce-or-remove); the mirror keeps its
-retired keys (`timeout` → `timeoutMs`; `localPath` and `wasm`, removed) as `z.never()` tombstones
-whose refusal carries the prescription. The live keys:
+Neither declares a key the driver does not read — the direction ADR-0049 (enforce-or-remove)
+governs. The converse does not hold, and the mirror is the shorter list: it does not declare
+`mode`, which the driver does read (`TursoDriverConfig.mode`). The mirror keeps its retired keys
+(`timeout` → `timeoutMs`; `localPath` and `wasm`, removed) as `z.never()` tombstones whose refusal
+carries the prescription. The live keys:
 
 | Property | Type | Default | Description |
 |:---|:---|:---:|:---|

packages/drivers/driver-turso/README.md

@@ -213,7 +213,10 @@ interface TursoDriverConfig {
    *   client makes is aborted once the window elapses, and the operation fails
    *   as TIMEOUT / 504 instead of hanging. wss:// and ws:// URLs use the
    *   WebSocket transport, which has no such seam, and are not bounded.
-   * - Replica mode: bounds sync(), the one remote operation on that arm.
+   * - Replica mode: bounds sync(), the one remote operation on that arm. A
+   *   sync still running when the window closes rejects with the same
+   *   envelope; the native binding's own sync is not cancelled, only no longer
+   *   awaited.
    * Not the libSQL busy timeout (`Config.timeout`), which is a local-file
    * lock-contention setting that remote clients ignore.
    */