docs(driver-memory): stop calling this production-ready; say what it does not enforce (#4065)

The class docstring opened with "A production-ready implementation of the
ObjectStack Driver Protocol". The driver stores no constraints of any kind:
`create()` is a `table.push()` and `syncSchema()` only allocates an array and
indexes temporal fields, so there is no primary key, no uniqueness, no NOT NULL,
no foreign key and no column typing. `bulkCreate` lands two rows with the same
id where a SQL driver raises a constraint violation, and a read returns both —
the second finding in #4065, and the mechanism behind the 2N row growth there.

Per Prime Directive #10 the options for `declared ≠ enforced` are implement it,
trim the claim, or file it. With this driver moving to maintenance-only — kept
for the last-resort rung of the dev step-down, browser/edge runtimes with no
SQLite build, and the read-coercion parity gate — the claim is what goes.

The docstring now states the missing constraints plainly, names the driver as a
WEAK oracle for tests, and points at in-memory SQLite instead. No behaviour
change; 197 driver-memory tests unchanged and green.

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

Author: claude

.changeset/memory-driver-opt-in-persistence.md

@@ -65,3 +65,13 @@ genuinely wanted durability now state it, rather than inheriting it:
 `DevPlugin`'s driver is now explicitly `persistence: false`, matching the cache,
 queue, job, i18n, storage and search stubs it ships beside — it was the one piece
 of that stack that quietly outlived the process.
+
+**One claim trimmed, no behaviour attached.** The class docstring called this a
+"production-ready implementation of the ObjectStack Driver Protocol". It stores
+no constraints at all — `create()` is a `table.push()` and `syncSchema()` only
+allocates an array — so there is no primary key, uniqueness, `NOT NULL`, foreign
+key or column typing, and `bulkCreate` lands duplicate ids where a SQL driver
+raises a violation (the second finding in #4065). The docstring now says so, and
+points test authors at in-memory SQLite. Per Prime Directive #10 the fix for
+`declared ≠ enforced` is to implement it, trim the claim, or file it; with this
+driver moving to maintenance-only the claim is what goes.

packages/plugins/driver-memory/src/memory-driver.ts

@@ -80,18 +80,38 @@ interface MemoryTransaction {
 
 /**
  * In-Memory Driver for ObjectStack
- * 
- * A production-ready implementation of the ObjectStack Driver Protocol
- * powered by Mingo — a MongoDB-compatible query and aggregation engine.
- * 
+ *
+ * An implementation of the ObjectStack Driver Protocol powered by Mingo — a
+ * MongoDB-compatible query and aggregation engine.
+ *
  * Features:
  * - MongoDB-compatible query engine (Mingo) for filtering, projection, aggregation
  * - Full CRUD and bulk operations
  * - Aggregation pipeline support ($match, $group, $sort, $project, $unwind, etc.)
  * - Snapshot-based transactions (begin/commit/rollback)
  * - Field projection and distinct values
  * - Strict mode and initial data loading
- * 
+ *
+ * ## What this driver does NOT enforce
+ *
+ * It stores no constraints of any kind. {@link create} is a `table.push()` and
+ * {@link syncSchema} only allocates an array and indexes temporal fields, so
+ * there is no primary key, no uniqueness, no `NOT NULL`, no foreign key and no
+ * column typing. `bulkCreate` will happily land two rows with the same `id`
+ * where a SQL driver raises a constraint violation, and a read returns both.
+ *
+ * That makes it a WEAK oracle: code green against this driver can still be
+ * broken against the SQL engines production runs on. Prefer in-memory SQLite
+ * for tests — `SqlDriver` with `connection: { filename: ':memory:' }`, or
+ * `SqliteWasmDriver({ filename: ':memory:' })` where no native build is wanted.
+ * This driver's remaining roles are the last-resort rung of the dev step-down
+ * (native better-sqlite3 → WASM SQLite → here), browser/edge runtimes where no
+ * SQLite build is available, and the cross-driver read-coercion parity gate.
+ *
+ * The docstring said "production-ready" until #4065; the constraints above were
+ * true then too, and saying so is the fix (Prime Directive #10 — never advertise
+ * a capability the runtime does not deliver).
+ *
  * Reference: objectql/packages/drivers/memory
  */
 export class InMemoryDriver implements IDataDriver {