[objectstack-fleet]

Fixes #20054

Clause-②: no (narrowing)

What this changes

A remote TursoDriver (libsql://, https://, wss:// and the other remote schemes) now constructs, connects and runs CRUD with better-sqlite3 not installed. That is the install package.json (an optional peer) and the README's "Dependencies by Mode" table give remote mode, for Vercel and Edge deployments.

The fix is one arm of TursoDriver.toKnexConfig. The SqlDriver base constructor always builds a Knex instance. Remote mode used to hand it { client: 'better-sqlite3', connection: { filename: ':memory:' } }. knex's Client constructor loads the dialect's native driver (initializeDriver, which runs require('better-sqlite3')) and builds a pool only when the config carries a connection. Remote mode now passes { client: 'better-sqlite3', useNullAsDefault: true } with no connection: the SQLite dialect's compiler, with no native module, no pool and no private :memory: database. The client is still spelled better-sqlite3, so isSqlite and every dialect-keyed rule the remote arms borrow from the base answer as before. SqlDriver is not touched, and no export changes.

Files:

• packages/drivers/driver-turso/src/turso-driver.ts: the remote arm of toKnexConfig and its comment. Also the text of two remote refusals this change made false (see Deviations).
• packages/drivers/driver-turso/src/turso-remote-no-native-driver.test.ts: new pin.
• Two refusal test docblocks now use the past tense for the placeholder (comments only).
• .changeset/20054-turso-remote-no-native-driver.md: @objectstack/driver-turso minor, BREAKING (patch round 1).

Measurements

All readings were taken in objectstack-ai/objectstack. Base: 3557f85fa5. Head: this branch. The probes used dist built at each tree. "Absent" means better-sqlite3 made unresolvable in a separate node process (a Module._resolveFilename hook). The pin uses a Module._load hook instead.

H1 (the throw), confirmed at base. knex 3.3.0 lib/client.js: if (this.driverName && config.connection) this.initializeDriver();, which calls Client_BetterSQLite3._driver() (require('better-sqlite3')).

construction, module absent	base	head
remote libsql://probe-db.example.turso.io	throws Knex: run $ npm install better-sqlite3 --save	constructs, transportMode = 'remote'
local :memory: (control)	throws, same message	throws, same message
local file: (control)	throws, same message	throws, same message
all three, module present	construct	construct

H2: what the remote face uses this.knex for. I wrapped driver.knex in a Proxy that records every property read and call after construction. The remote driver ran over a real @libsql/client file: client.

• Construction: the SqlDriver constructor's knex(config) call, and installQueryTiming (this.knex.on for three events). Read from the source, not recorded.
• 22 remote-armed doors: connect, checkHealth, initObjects, syncSchema, syncSchemasBatch, create, bulkCreate, find, findOne, count, aggregate, update, upsert, bulkUpdate, updateMany, execute, paginationTieBreaker, bulkDelete, deleteMany, delete, dropTable and disconnect. Plus the 4 refusals: beginTransaction, detectManagedDrift, planMediaColumnMove, setDeferredDdl(true). Zero reads, at base and at head.
• The inherited helpers those arms call have no this.knex reference in their bodies (dist, 14 names): temporalFilterValue, temporalFilterColumnSql, the three sqlite*Sql rules, isNonTextColumn, formatInput, formatOutput, computeTenantField, calendarDayUpperBoundRewrite, orderKeysFor, registerExternalObject, toDateOnly and rawStatementFault.
• Only the SqlDriver methods remote mode does not override reach it: introspectSchema (.raw), distinct (builder), findWithWindowFunctions (builder, .raw, .client), analyzeQuery and explain (builder, .raw), and reclaimSpace (.raw).
• On this state, previewDeferredSchemaWork, flushDeferredSchemaDdl, applyMigrationEntries([]) and getSchemaSyncStats made zero reads. rotateShards threw before it reached Knex.
• Remote disconnect() never calls super.disconnect(), so knex is never destroyed on the remote face.

So nothing on the remote face needs a live Knex, and nothing needs a compiling one either. A Knex with no connection was the smallest seam: it lives in toKnexConfig, and SqlDriver's constructor contract stays as it is.

H3: the inherited methods, before and after. A remote face over a libsql file: client holding rows in probe_t.

method	base, module present	head, present	head, absent
introspectSchema()	resolves { tables: {} } (silent)	rejects Unable to acquire a connection	same
distinct('probe_t', 'name')	rejects DATABASE_ERROR / 500	same	same
findWithWindowFunctions(…)	rejects raw SqliteError no such table: probe_t	rejects Unable to acquire a connection	same
analyzeQuery / explain	resolves { sql, bindings, client, error: 'EXPLAIN QUERY PLAN … no such table …' }	resolves, same shape, error: 'Unable to acquire a connection'	same
reclaimSpace()	resolves (vacuumed the private database)	rejects Unable to acquire a connection	same
previewDeferredSchemaWork, flushDeferredSchemaDdl, applyMigrationEntries([]), getSchemaSyncStats	resolve, no Knex read	same	same
rotateShards('probe_t')	throws, no rotation policy	same	same

• Loud to silent: 0. Silent to loud: 2 (introspectSchema, reclaimSpace).
• The head readings with the module present and absent are byte-identical (diffed).
• A side reading: at base, a remote driver that had run introspectSchema() kept the process alive after disconnect(). timeout 20 killed it (exit 124), because a pooled better-sqlite3 connection was never destroyed. At head, the process exits (no pool is built).

H4: in-repo constructions. git grep 'new TursoDriver(' on non-test .ts files: 9 hits, 3 of them real calls:

• createTursoDriver and the plugin's onEnable in driver-turso/src/index.ts;
• the turso arm of service-datasource/src/default-datasource-driver-factory.ts.

The runtime loader adds new TursoDriverCtor( in runtime/src/turso-driver-factory.ts. None of the four reads .knex. The datasource factory's sqlServerVersion goes through driver.execute, which is the remote transport.

Repo-wide reads of a driver's Knex outside driver-sql, non-test:

• getKnex(): 0 calls (1 comment). Control: sql-driver.ts has 1 hit.
• .knex reads: 2 files. metadata-protocol's resolveDriverClientName reads driver.config.client first, and that answer is unchanged (better-sqlite3). runtime/src/raw-foreign-key-fixture.ts is used by two SqlDriver integration tests and not by any Turso test.

Tests

• New pin turso-remote-no-native-driver.test.ts: 10 tests.

  • Control: local :memory: and file: still throw without the module. The hook counted at least one load attempt, which proves it is live.
  • Remote construction without the module: 0 load attempts.
  • Remote CRUD through a real @libsql/client file: client without the module: 0 load attempts, and the rows read back from that file.
  • introspectSchema, distinct and findWithWindowFunctions, each with the module present and absent. Each call must either fail or answer from the remote database, never "no tables". The envelope is left to driver-turso remote: inherited SqlDriver methods the remote face does not override answer from the placeholder :memory: Knex database — introspectSchema() returns no tables, distinct() a 500, findWithWindowFunctions() a raw SQLite error #20055.

• Reverse verification. The fix was committed first. node scripts/ablation-replace.mjs restored connection: { filename: ':memory:' } in the remote arm: anchor 1 to 0, blob 227df64b3046 to a5b36d46ed8f. The pin went 6 failed, 4 passed, the direction predicted before the run:

  • construction and CRUD failed on knex's install error;
  • introspectSchema, module present, failed on expected [] to include 'probe_t';
  • all three inherited cases with the module absent failed at construction;
  • the two controls stayed green, and so did distinct and findWithWindowFunctions with the module present, which were already loud at base.

  After the restore, the blob equals HEAD and git diff HEAD is empty. The test imports ./index.js (source), so no rebuild was part of either leg.

• pnpm --filter @objectstack/driver-turso test: 67 files, 1510 passed. typecheck: exit 0. tsc --listFiles includes all 4 changed .ts files.

• pnpm --filter @objectstack/driver-sql test: 184 files passed, 11 skipped. 2845 tests passed, 170 skipped.

• Consumers that construct a TursoDriver (targeted files):

  • service-datasource: default-datasource-driver-factory, datasource-pool-support, turso-bound-secret-authoring and turso-driver-config. 4 files, 147 passed.
  • runtime: turso-driver-factory.convergence and standalone-stack.libsql. 2 files, 38 passed.
  • dogfood: date-bucket-parity-turso, which builds a real remote driver. 1 file, 5 passed.
  • The CLI's storage-driver.test.ts builds a fake TursoDriver class, not this one. It is declared to CI, not run here.

• pnpm check:driver-conformance, before (base, in a detached worktree) and after: OK — 50 covered cell(s), 0 in the DEBT ledger, 0 exempt, both.

Gates at head 014b58a689, derived from the real diff with node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (merge base 3557f85fa): 61 commands. The dispatch's list (derived at 2c1011b) had 54, and all 54 are included. The 7 new ones are check-adr-0087-registration x2, check-empty-changeset x2, release-rehearsal-clone --self-test, check:objectui-changeset and check:pm-changeset-deadline-census.

• 59 exit 0.
• 2 NOT MEASURED (exit 3, PREREQUISITE NOT MET): check:dual-build-cjs-loads and check:type-check-debt. Both read the whole workspace's built output, and this worktree built only the closures listed above. lint.yml builds the whole closure first, so CI measures them.
• check:dts-closure first exited 1. It named 26 packages whose dist/ I had built locally with OS_SKIP_DTS=1 to run the consumer suites. I removed those dist/ directories and re-ran it: exit 0, 46/46 declared declaration file(s) present across 8 package(s), driver-turso among them.
• The --ran reconciliation with exit codes recorded: 61 derived, 59 run, 2 NOT-MEASURED, 0 UNRUN.
• node scripts/check-issue-citations.mjs --base 3557f85fa5: exit 0, 3 citations resolve.
• Out-of-gate control-byte scan of the 5 changed files: no match.
• Not run locally, and owned by CI: the repo-wide pnpm lint, the CLI unit layer, and the path-scheduled CI jobs dispatch-gates names.

Deviations

• Two runtime strings in turso-driver.ts outside the claimed arm. The NOT_IMPLEMENTED / 501 messages of the remote detectManagedDrift() and planMediaColumnMove() said "in remote mode that connection is a placeholder in-memory database holding none of this datasource's tables". This change made that false. They now say remote mode has no Knex connection. Each still gives a reason that holds at head, measured by calling the inherited methods on a head remote driver:

  • the no-argument drift call answers [] from the empty managedObjectFields;
  • the media planner answers an empty scan;
  • an explicit-objects drift call now fails on hasTable.

  First sentences, codes and statuses are unchanged, so both existing pins stay green. Their docblocks and the two comments on the overrides were edited to match.

Acceptance notes

• introspectSchema() on a remote driver now fails with knex's Unable to acquire a connection. That message points at connectivity. The real answer belongs to driver-turso remote: inherited SqlDriver methods the remote face does not override answer from the placeholder :memory: Knex database — introspectSchema() returns no tables, distinct() a 500, findWithWindowFunctions() a raw SQLite error #20055, which will either route the call to the transport or refuse it with NOT_IMPLEMENTED. driver-turso remote: inherited SqlDriver methods the remote face does not override answer from the placeholder :memory: Knex database — introspectSchema() returns no tables, distinct() a 500, findWithWindowFunctions() a raw SQLite error #20055 remains open for all three methods. The callers I traced (not run):

  • ExternalDatasourceService.testConnection now reports ok: false with that message, where it reported ok: true, tableCount: 0;
  • the boot validation sweep now rows a federated object on a remote-Turso datasource as unreachable (logged at warn, boot continues), where it rowed missing_table against the empty answer.

  The datasource admin's testConnection prefers checkHealth, so it is unaffected.

• The pending changesets 19845-turso-remote-drift-detection-refusal.md and 19894-turso-remote-media-column-move-refusal.md describe the placeholder in the present tense. They narrate what those refusals replaced. I left them alone, and this PR's changeset says the placeholder is gone.

• Banner. os serve's banner reads a registered driver's config. For a remote Turso driver, describeDriverConnection returned :memory: at base (a false address) and returns undefined at head. describeRegisteredDriver then prints (unknown). The renderer was measured and the fallback traced.

• The CLI's migrate describeDb falls back to the client name. At head it would print better-sqlite3 for a remote Turso datasource instead of :memory:. Traced only.

Semver

@objectstack/driver-turso: minor, fix(driver-turso)!:, Clause-②: no (narrowing), with an ADR-0087 not-required (no-migration-prescription) disposition in the changeset. This was ruled in patch round 1, below.

Patch round 1

The PM seat answered the open question with B, for consistency with this lane's precedents on the same driver face: #19893 (PR #19971) and #19894 (PR #20014). On a remote driver, introspectSchema() and reclaimSpace() resolved before and reject now. That is a call the published driver answered and no longer answers, so it is declared, whatever the old answer's quality.

What changed, in .changeset/20054-turso-remote-no-native-driver.md only (commit 93d49b886e, no code change):

• the bump is now minor and the summary reads fix(driver-turso)!:;
• the declaration line is now Clause-②: no (narrowing);
• a BREAKING paragraph names introspectSchema() (used to resolve { tables: {} }) and reclaimSpace() (used to resolve). On a remote driver both now reject with knex's Unable to acquire a connection;
• findWithWindowFunctions(), analyzeQuery() / explain() and distinct() are listed apart, as changing their error wording only or not at all;
• an ADR-0087 not-required (no-migration-prescription) disposition in the driver-turso: a remote url plus syncUrl is classified replica and handed a :memory: Knex connection, so every write lands in process memory and never reaches the remote #19893 shape. No key, schema, object definition or stored representation moves, only which calls a remote driver answers. driver-turso remote: inherited SqlDriver methods the remote face does not override answer from the placeholder :memory: Knex database — introspectSchema() returns no tables, distinct() a 500, findWithWindowFunctions() a raw SQLite error #20055 carries the per-method answer or refusal.

The version axis is unchanged: .changeset/19894-turso-remote-media-column-move-refusal.md already bumps @objectstack/driver-turso minor in the pending release.

Gate verdicts at 93d49b886e, against merge base 3557f85fa5:

• check-changeset-no-major: ✓ This diff introduces no `major` bump. With this body as the --event payload: ✓ LEVEL AXIS: this PR declares clause-② `no (narrowing)`, and no package whose `packages/**/src/**` it moves is graded `patch`.
• check-adr-0087-registration: ✓ check-adr-0087-registration: 1 declared-breaking changeset(s), each carrying an ADR-0087 disposition. The changeset is tagged [BREAKING+bang+clause-②-narrowing] not-required (no-migration-prescription).
• check-empty-changeset: ✓ No empty-frontmatter changeset introduced by this diff (1 declaring changeset(s) added).

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/driver-turso, touching 4 documentable anchor(s).

2 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/data-modeling/drivers.mdx (via TursoDriver (symbol, a top-level class))
• content/docs/plugins/packages.mdx (via TursoDriver (symbol, a top-level class))

What this run could not see

• the SDK route bridge reached 60 of 215 client-bound route-ledger rows — the other 155 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 155: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 100 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 6 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from a75ccd92361f0e60765a4b14f3a282275b3c0958 — the merge of head 93d49b886e8e7d53dc5ee9e77e0d109bc89b7db6 into base b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin a75ccd92361f0e60765a4b14f3a282275b3c0958 && git checkout a75ccd92361f0e60765a4b14f3a282275b3c0958
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56 93d49b886e8e7d53dc5ee9e77e0d109bc89b7db6 && git checkout -B drift-repro b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56 && git merge --no-ff 93d49b886e8e7d53dc5ee9e77e0d109bc89b7db6

node scripts/docs-audit/affected-docs.mjs --json b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs b76aad5f6fac71cbbcd4ea6bfdf21a59e2fd4d56 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 93d49b886e8e7d53dc5ee9e77e0d109bc89b7db6

Scope: 5 files (+343/−31) on merge base 3557f85fa5:

• the changeset;
• the remote arm of turso-driver.ts's toKnexConfig, and the two reworded refusal messages;
• two refusal-test docblocks;
• the new pin turso-remote-no-native-driver.test.ts.

No governed surface is touched. Review is owed for the .changeset prose.

Read: cards #20054 and #20055, the PR body, the diff, all 41 check-runs, AGENTS.md, and the code at head and base.

Measured in two detached worktrees (head and base, each with the driver-turso closure built and each dist verified to carry its own remote arm, both removed afterwards), under knex 3.3.0 and @libsql/client 0.17.4. One scenario ran per process, at base and head, with better-sqlite3 present and with it refused through a Module._load hook that counts load attempts.

① Derived judgments

• The defect and the fix: RIGHT.
  • knex runs initializeDriver(), which requires better-sqlite3, only when config.connection is set.
  • With the module refused, at base: remote, local :memory: and local file: all throw Knex: run $ npm install better-sqlite3 --save, with 1 load attempt each.
  • At head: remote constructs, with 0 attempts. Local :memory: and file: still throw, with 1 attempt each (the control).
• Remote creation, connection and CRUD without the module: RIGHT. Over a real libSQL file: client these all answer, with 0 load attempts, and the rows land in the libSQL file: connect, checkHealth, initObjects, create, bulkCreate, update, count, find, findOne, aggregate, execute, delete and disconnect.
• No remote path reaches Knex: RIGHT.
  • A Proxy over driver.knex recorded 0 reads across 26 remote doors, at base and at head. That includes registerExternalObject, the four refusals and disconnect.
  • The query-timing listeners are unchanged.
  • At base, a remote driver that had run introspectSchema() kept the process alive after disconnect() (killed at the timeout). At head, the process exits.
  • resolveDriverClientName still answers better-sqlite3.
  • The serve banner's address goes from a false :memory: to (unknown).
• The inherited methods: the PR's table is exact.
  • introspectSchema() resolved { tables: {} } while the remote file held the table; it now rejects with Unable to acquire a connection. reclaimSpace() resolved and now rejects the same way.
  • distinct() answers DATABASE_ERROR / 500 at both.
  • findWithWindowFunctions() and analyzeQuery() / explain() change only their error wording.
  • Tally: silent→loud 2, loud→silent 0.
• Traced callers of introspectSchema():
  • ExternalDatasourceService.testConnection now answers ok: false where base answered ok: true, tableCount: 0;
  • the boot validation sweep rows unreachable (warn, boot continues) where base rowed a false missing_table;
  • the admin test prefers checkHealth, which TursoDriver routes to the transport, so it is unaffected.
• The two reworded refusals: every sentence TRUE, and code and status are unchanged (NOT_IMPLEMENTED / 501, the first sentences byte-identical). managedObjectFields is empty after a remote initObjects.
• Local and replica are unchanged: RIGHT. The config, introspectSchema, distinct, reclaimSpace and count are identical at base and head.
• The pin discriminates: RIGHT. 10/10 at head. On the base tree it gives 6 failed / 4 passed, exactly the PR's reverse-verification claim.
• CI at this head: 41 runs, 36 success, 5 skipped, 0 failures, and all seven required contexts are success.

② Semver level

@objectstack/driver-turso: minor, fix(driver-turso)!:, Clause-②: no (narrowing), with the ADR-0087 disposition not-required (no-migration-prescription): CONSISTENT.

• No packages/spec schema moves.
• Two published calls a remote driver answered now reject, which is a narrowing and so BREAKING.
• A breaking change ships minor in the launch window.
• The marker matches the driver-turso remote detectManagedDrift() diffs against the dummy :memory: Knex connection remote mode is given — drift is always empty, so the artifact boot migration gate reads a remote Turso database as never drifted #19845 / driver-turso remote planMediaColumnMove answers empty, so os migrate files-to-references reports nothing to move on a remote Turso database whose media columns are present #19894 precedents on the same driver face.

The dev's original patch / no reading was wrong, for the reason the seat's ruling B gives.

③ Boundary flags

• Changeset: every sentence is TRUE, including the BREAKING paragraph and the ADR-0087 marker's "no key, schema, object definition or stored representation moves". TursoDriverConfig and both TursoConfigSchema copies are untouched. "objectstack migrate meta has nothing to visit" is UNMEASURED, but consistent.
• PR body: TRUE where measured. H4's .knex census says 2 files; there are 3. driver-sqlite-wasm's self-read is irrelevant to Turso. No judgment depends on it.
• Not blocking, and belongs to driver-turso remote: inherited SqlDriver methods the remote face does not override answer from the placeholder :memory: Knex database — introspectSchema() returns no tables, distinct() a 500, findWithWindowFunctions() a raw SQLite error #20055: reclaimSpace() has an in-repo caller the PR does not name, LifecycleService.sweep() (packages/objectql/src/lifecycle/lifecycle-service.ts). On a remote-Turso datasource, a sweep that deleted rows now logs one warn and leaves the datasource out of report.reclaimed. At base it silently vacuumed a private database and reported it reclaimed. No data is at risk.
• Docs: the README's "Dependencies by Mode" better-sqlite3 sentences go from FALSE at base to TRUE at head. Nothing in content/docs/data-modeling/drivers.mdx or content/docs/plugins/packages.mdx is made false. A pre-existing inexactness is unchanged: on a Node host, @libsql/client's Node entry loads its own native libsql binding.

Implemented-by: claude/issue-20054-turso-remote-no-native-driver
Reviewed-by: session_01Bvd69VPa6puiNzzPUroDBx

VERDICT: PASS

Isolated reviewer: a contract-review-tier subagent, fed only the cards, the PR and AGENTS.md; adopted by the seat.