# @objectstack/driver-sqlite-wasm ## 17.7.0 ### Patch Changes - Updated dependencies [ecb6ca0] - Updated dependencies [135daaa] - Updated dependencies [22c2d6f] - Updated dependencies [909229e] - Updated dependencies [0721848] - Updated dependencies [bdd3654] - Updated dependencies [aead296] - Updated dependencies [c205b6c] - Updated dependencies [13a24ec] - Updated dependencies [ad7c351] - Updated dependencies [e901c27] - Updated dependencies [a387354] - Updated dependencies [f6b7520] - Updated dependencies [36e4647] - Updated dependencies [93a54b8] - Updated dependencies [f623e2f] - Updated dependencies [96a9719] - Updated dependencies [41a3c8d] - Updated dependencies [c52c49d] - Updated dependencies [cfa4d74] - Updated dependencies [99589f9] - Updated dependencies [36ad321] - Updated dependencies [dcc5ef4] - Updated dependencies [9b7a0ef] - Updated dependencies [5a9292e] - Updated dependencies [30af17e] - Updated dependencies [30af17e] - Updated dependencies [1c52a5e] - Updated dependencies [99e1912] - Updated dependencies [7ebb543] - Updated dependencies [3911901] - Updated dependencies [222ecc2] - Updated dependencies [3937ad2] - Updated dependencies [3a6d92f] - Updated dependencies [7526058] - Updated dependencies [53fd35e] - Updated dependencies [23365ea] - Updated dependencies [32d5769] - Updated dependencies [16eefc6] - Updated dependencies [6e33b67] - Updated dependencies [57cc695] - Updated dependencies [db3fee3] - Updated dependencies [4c8363f] - Updated dependencies [9f13c94] - Updated dependencies [6d67ad5] - Updated dependencies [ca0dfb6] - Updated dependencies [45efcfa] - Updated dependencies [6d728b8] - Updated dependencies [c9c555a] - Updated dependencies [68c5ab7] - Updated dependencies [b793010] - Updated dependencies [5555047] - Updated dependencies [35dfb81] - Updated dependencies [aa46322] - Updated dependencies [100c394] - Updated dependencies [72217cd] - Updated dependencies [72af58c] - Updated dependencies [1289925] - Updated dependencies [958cfe2] - Updated dependencies [ced3e1a] - Updated dependencies [7d674df] - Updated dependencies [3f1bc81] - Updated dependencies [72f3c74] - Updated dependencies [529d971] - Updated dependencies [16d241a] - Updated dependencies [4331a6b] - Updated dependencies [440cd32] - Updated dependencies [6c5697d] - Updated dependencies [9a4182a] - Updated dependencies [41b1333] - Updated dependencies [f1e4ae5] - Updated dependencies [eb9ef79] - Updated dependencies [eb9ef79] - Updated dependencies [f83d066] - Updated dependencies [1ac7308] - Updated dependencies [10454b3] - Updated dependencies [9e9d693] - Updated dependencies [6ec54f0] - Updated dependencies [5d095a0] - Updated dependencies [98eb3b9] - Updated dependencies [a2aadab] - Updated dependencies [fe10172] - Updated dependencies [ed15448] - Updated dependencies [9d91f58] - Updated dependencies [9059082] - Updated dependencies [309224d] - Updated dependencies [e83c9f6] - Updated dependencies [da40a5f] - Updated dependencies [045f764] - Updated dependencies [2df3d13] - Updated dependencies [07bf21f] - Updated dependencies [6fb7115] - Updated dependencies [53021e3] - Updated dependencies [a0176ef] - Updated dependencies [ba57588] - Updated dependencies [a43d90a] - Updated dependencies [607463d] - Updated dependencies [cab6396] - Updated dependencies [e864db5] - Updated dependencies [866683f] - Updated dependencies [88a39c0] - Updated dependencies [8e35895] - Updated dependencies [1f04696] - Updated dependencies [d16b9fb] - Updated dependencies [bab7685] - Updated dependencies [fb69825] - Updated dependencies [48eb9c1] - Updated dependencies [8832655] - Updated dependencies [100f68b] - Updated dependencies [8963dbf] - Updated dependencies [1354e7b] - Updated dependencies [1cbe165] - Updated dependencies [15fe567] - Updated dependencies [0bddffd] - Updated dependencies [7e0066a] - @objectstack/spec@17.7.0 - @objectstack/core@17.7.0 - @objectstack/driver-sql@17.7.0 ## 17.6.0 ### Patch Changes - ceee88f: fix(driver-sql, driver-turso, plugin-security, spec)!: `SqlDriver` and `TursoDriver` compile the filter they are handed — their copies of the whole-day bound and of the NULL-safe `$not` rewrite are deleted, and the RLS compile seam lowers type-blind when it cannot read the declared types (ADR-0053 D-D1 items 5, 7 and 9, #20822) Clause-②: no (narrowing) **BREAKING**: `SqlDriver` in `@objectstack/driver-sql` loses three `protected` methods: `calendarDayExclusiveUpperBound`, `calendarDayUpperBoundRewrite` and `calendarDayBetweenRewrite`. They were the driver's copy of the whole-day bound, which the shared lowering now applies once, at the seams, before a driver sees the filter. A subclass of `SqlDriver` that calls one of them, or overrides one with the `override` modifier, no longer compiles (TS2339, TS4113). That includes a subclass of `SqliteWasmDriver` or `TursoDriver`, which extend `SqlDriver`. A subclass that re-declares one without `override` still compiles, but the driver never calls it, so the rule it carried stops applying. It ships as `minor` under the launch-window convention. The class's public methods are unchanged. FROM → TO: a `SqlDriver` subclass that called `this.calendarDayUpperBoundRewrite(table, field, op, value)`, `this.calendarDayBetweenRewrite(table, field, value)` or `this.calendarDayExclusiveUpperBound(table, field, value)`, or overrode one of them, lowers the filter with `lowerFilterCondition` from `@objectstack/spec/data` instead, before the driver compiles it: `lowerFilterCondition(where, { isDatetimeColumn })`, where `isDatetimeColumn` answers which columns get the whole-day bound. **Supersedes two sentences of this release's shared-lowering entry** (`lowerFilterCondition`, #5930), which this change makes false: - "A guard without that set treats no column as `datetime`." Now: when the RLS compile seam has no field guard, or one without a `datetime` set, it cannot read which columns are `datetime`, so it applies the whole-day rule to every column (the `@objectstack/plugin-security` entry below). - "Each driver keeps its own copy of these rules, and every copy gives the same answer on lowered input." Now: `SqlDriver`, `SqliteWasmDriver` and `TursoDriver` keep no copy of the whole-day bound or of the NULL-safe `$not` rewrite. A read through the engine or the RLS compile seam gets the lowered answer, and a call on the driver itself gets the comparison it wrote (the `@objectstack/driver-sql` and `@objectstack/driver-turso` entries below). - **`@objectstack/plugin-security` — an RLS policy compiled with no field guard is lowered type-blind.** The RLS compile seam runs the shared `lowerFilterCondition` on every compiled `using` and `check` filter. When the security plugin could not resolve the object's declared fields (no field guard), or a caller of `RLSCompiler.compileFilter` passes a guard without a `datetime` set, the seam cannot read which columns are `datetime`, and it now applies the whole-day rule to every column (a bare-day upper bound becomes `$lt` the next day), as ADR-0053 D-D1 item 7 rules for a seam that cannot read the type. It used to read no column as `datetime`, which left the bound to each driver's own copy of the rule. Visible on a `using` policy such as `record.signed_on <= '2026-01-05'` on such an object: every row of that day is kept on every driver, including `InMemoryDriver`, which had compared it as written since its own copy was deleted. A guard with a `datetime` set is unchanged, and so are the NULL-polarity guards. - **`@objectstack/driver-sql` — `SqlDriver` keeps no copy of the rules the seams apply.** Deleted: the whole-day rewrite of a bare-day `$lte` and of a `$between` maximum on a `datetime` column, on the plain and the legacy-normalised column paths, including the last supported day (the protected methods `calendarDayExclusiveUpperBound`, `calendarDayUpperBoundRewrite` and `calendarDayBetweenRewrite` are removed from the class); and the NULL-safe rewrite of a `$not` operand (`nullSafeNegationOperand` and its polarity tables, module-private). A read through the engine or the RLS compile seam is unchanged: the seam hands the driver a filter the shared lowering has already rewritten, and the deleted copies gave the same answer on that input. A caller that passes no seam — `find`, `findOne`, `count`, `aggregate`, `distinct`, `updateMany`, `deleteMany` or `findWithWindowFunctions` called on the driver itself — now gets the comparison it wrote: a bare-day `$lte` compares against that day's midnight, a `$between` is inclusive at both ends, `$lte '9999-12-31'` compares against that midnight, and a `$not` is SQL's three-valued negation, so a row whose compared column is NULL is not returned by it. `$ne`, `$nin` and `$notContains` keep their NULL-safe form, which this emitter spells for the operator itself. The refusal of an `undefined` comparand (`INVALID_FILTER` / 400) is kept: without it some positions would answer instead of refusing. To keep the seam's reading on a direct call, lower the filter first: `driver.find(object, { where: lowerFilterCondition(where, { isDatetimeColumn }) })`, with `lowerFilterCondition` from `@objectstack/spec/data`. A subclass that called or overrode one of the three removed methods: see **BREAKING** above. - **`@objectstack/driver-sqlite-wasm` — `SqliteWasmDriver` inherits the `SqlDriver` change above**, with the same answers on a seamed read and on a direct call. - **`@objectstack/driver-turso` — both faces of `TursoDriver` compile the filter they are handed.** Local and replica mode inherit the `SqlDriver` change. Remote mode: `toRemoteFilter` no longer widens a bare-day `$lte` or a `$between` maximum (it still splits a two-bound `$between` into the `$gte` / `$lte` pair the remote transport compiles, both ends inclusive, and still converts each comparand to storage form), and `RemoteTransport` no longer rewrites a `$not` operand (its copy of the polarity tables is deleted). The two faces still answer every filter alike, on a seamed read and on a direct call. The remote transport keeps its refusal of an `undefined` comparand, worded as `driver-sql`'s, so both faces refuse it in one sentence. The same one line keeps the seam's reading on a direct call. - **`@objectstack/spec` — the ADR-0087 ledger records the removal.** The protocol-18 step of `MIGRATIONS_BY_MAJOR` gains the semantic entry `driver-sql-calendar-day-methods-removed`, which names the three removed methods with their replacement and acceptance criteria. Every upgrade channel that projects protocol 18 carries it. `spec-changes.json` and the generated upgrade guide stop at the current protocol, 17, so neither changes in this release. A subclass that re-declares one of the methods without `override` still compiles and is never called, so the ledger, not the compiler, is the notice that reaches it. - f3b16fc: Raise the published dependency floors to the 2026-10 production dependency group. No API changes. A consumer install resolves these ranges: Clause-②: no - `zod` `^4.6.1` → `^4.6.5`: `@objectstack/spec`, `@objectstack/core`, `@objectstack/objectql`, `@objectstack/rest`, `@objectstack/runtime`, `@objectstack/cli`, `@objectstack/mcp`, `@objectstack/metadata`, `@objectstack/metadata-core`, `@objectstack/metadata-protocol`, `@objectstack/driver-turso`. - `@libsql/client` `^0.17.3` → `^0.18.0`: `@objectstack/driver-turso`. Every behaviour the driver documents was re-measured on 0.18.0 and holds unchanged. That covers the URL scheme routing, the `URL_INVALID` and `URL_SCHEME_NOT_SUPPORTED` refusals, the WebSocket transport having no `fetch` or timeout seam, `syncUrl` being read only by the embedded-replica client, and the `?authToken=` precedence on `url` and `syncUrl`. The driver's refusal messages now name 0.18.0 as the measured version. 0.18.0 changes only the local `file:` client, which now pools connections. The driver creates that client only for an embedded replica, and calls only `sync()` on it. - `@modelcontextprotocol/sdk` `^1.30.0` → `^1.30.1`: `@objectstack/connector-mcp`, `@objectstack/mcp`. - `chalk` `^6.0.0` → `^6.0.1`: `@objectstack/cli`, `create-objectstack`. `yaml` `^2.9.0` → `^2.9.1` and `tsx` `^4.23.12` → `^4.23.15`: `@objectstack/cli`. - `mongodb` `^7.5.0` → `^7.6.0`: `@objectstack/driver-mongodb`. - `sql.js` `^1.14.1` → `^1.14.2`: `@objectstack/driver-sqlite-wasm`. - `@noble/hashes` `^2.3.0` → `^2.4.0` and `jose` `^6.2.8` → `^6.2.12`: `@objectstack/plugin-auth`. The better-auth family stays at exactly `1.7.3`. - `hono` `^4.13.5` → `^4.13.9`: `@objectstack/plugin-hono-server`. - `pinyin-pro` `^3.29.1` → `^3.29.4`: `@objectstack/plugin-pinyin-search`. - `@noble/ciphers` `^2.3.0` → `^2.4.0`: `@objectstack/service-settings`. - Updated dependencies [e5c7d07] - Updated dependencies [addbbf0] - Updated dependencies [93d4e0e] - Updated dependencies [88b484e] - Updated dependencies [9905e61] - Updated dependencies [f11b5f2] - Updated dependencies [0cb72cf] - Updated dependencies [c1d8051] - Updated dependencies [a918fe7] - Updated dependencies [41dcf11] - Updated dependencies [c46279f] - Updated dependencies [688ddef] - Updated dependencies [b1aab1e] - Updated dependencies [274e162] - Updated dependencies [05a7547] - Updated dependencies [0efbdc3] - Updated dependencies [c8dd8dd] - Updated dependencies [03cdb9a] - Updated dependencies [15b586d] - Updated dependencies [542670d] - Updated dependencies [e73ee2d] - Updated dependencies [92fe081] - Updated dependencies [c4c68ca] - Updated dependencies [d78a0bd] - Updated dependencies [5363e2d] - Updated dependencies [c876a74] - Updated dependencies [f1e921a] - Updated dependencies [7a1faf1] - Updated dependencies [c9d234c] - Updated dependencies [df67985] - Updated dependencies [42d78b9] - Updated dependencies [3fbf3ca] - Updated dependencies [24d521e] - Updated dependencies [b785c3b] - Updated dependencies [2473e26] - Updated dependencies [3a89d45] - Updated dependencies [f379f57] - Updated dependencies [889139c] - Updated dependencies [05cb2bc] - Updated dependencies [7510663] - Updated dependencies [a6866da] - Updated dependencies [1a75e39] - Updated dependencies [cd901d7] - Updated dependencies [d7631d5] - Updated dependencies [d830d71] - Updated dependencies [89801cd] - Updated dependencies [1ab9892] - Updated dependencies [fbec216] - Updated dependencies [35587f7] - Updated dependencies [ace770d] - Updated dependencies [ed54768] - Updated dependencies [99786f9] - Updated dependencies [63bfe69] - Updated dependencies [1940afd] - Updated dependencies [4f83db5] - Updated dependencies [f5c7b2c] - Updated dependencies [6afccda] - Updated dependencies [671d4c1] - Updated dependencies [bbcd20c] - Updated dependencies [c8111a5] - Updated dependencies [9ad6544] - Updated dependencies [c9c182e] - Updated dependencies [4b4ee88] - Updated dependencies [f10d802] - Updated dependencies [856321f] - Updated dependencies [810d42b] - Updated dependencies [6b004c0] - Updated dependencies [93e9e42] - Updated dependencies [ca5408c] - Updated dependencies [b280546] - Updated dependencies [975b248] - Updated dependencies [ebb66aa] - Updated dependencies [cf0346e] - Updated dependencies [ceee88f] - Updated dependencies [e18fea6] - Updated dependencies [f750119] - Updated dependencies [660a9b2] - Updated dependencies [dcd3309] - Updated dependencies [f6ccca4] - Updated dependencies [26437ae] - Updated dependencies [d1633f3] - Updated dependencies [32d3b3c] - Updated dependencies [c6b3a01] - Updated dependencies [bee75ce] - Updated dependencies [2742e53] - Updated dependencies [a75311d] - Updated dependencies [d98bf24] - Updated dependencies [8368f1c] - Updated dependencies [8368f1c] - Updated dependencies [31c3996] - Updated dependencies [95555e7] - Updated dependencies [a29a0ea] - Updated dependencies [83480c6] - Updated dependencies [013f97d] - Updated dependencies [5d5e679] - Updated dependencies [e07566b] - Updated dependencies [11d28c1] - Updated dependencies [399e3aa] - Updated dependencies [ba03198] - Updated dependencies [94608a7] - Updated dependencies [58a77db] - Updated dependencies [b3d7a70] - Updated dependencies [b3917d9] - Updated dependencies [c27404f] - Updated dependencies [a11faee] - Updated dependencies [2c1cef3] - Updated dependencies [27c0cf3] - Updated dependencies [097ef80] - Updated dependencies [70dae53] - Updated dependencies [665cab3] - Updated dependencies [682873d] - Updated dependencies [1bd14c9] - Updated dependencies [62b90d7] - Updated dependencies [cb45469] - Updated dependencies [f3b16fc] - Updated dependencies [d6d6e87] - Updated dependencies [df1feae] - Updated dependencies [e35c40a] - Updated dependencies [336e191] - Updated dependencies [9bdc6d3] - Updated dependencies [24c554d] - Updated dependencies [c6b6889] - Updated dependencies [ebdb6f2] - Updated dependencies [3dc33b2] - Updated dependencies [9969228] - Updated dependencies [95e24b0] - Updated dependencies [1a4c7f8] - Updated dependencies [c7396f1] - Updated dependencies [434c6c7] - Updated dependencies [4b59a38] - Updated dependencies [be5a83c] - Updated dependencies [d2bc644] - Updated dependencies [7923c8e] - Updated dependencies [95b91cc] - Updated dependencies [cfa9315] - Updated dependencies [0803a8b] - Updated dependencies [0d42104] - Updated dependencies [a3d7588] - Updated dependencies [b8191f7] - Updated dependencies [315888d] - Updated dependencies [1741c5d] - Updated dependencies [3711e0b] - Updated dependencies [a8acee2] - Updated dependencies [a51920f] - Updated dependencies [0f6dcac] - Updated dependencies [682873f] - Updated dependencies [2123fcc] - @objectstack/spec@17.6.0 - @objectstack/driver-sql@17.6.0 - @objectstack/core@17.6.0 ## 17.5.0 ### Minor Changes - 8a44ce7: fix(spec, drivers)!: a `$like` / `$ilike` pattern holding U+0000 is refused by every driver that answers `$like`, instead of being cut at the NUL on SQLite Clause-②: yes (narrowing) On the SQLite faces `$like` / `$ilike` compile to `GLOB`, and SQLite reads a pattern only up to its first U+0000. A pattern holding U+0000 was cut there, so the filter answered a different question, and nothing raised. Measured through `find` over 13 stored values (12 non-NULL), against `@objectstack/formula` on the same rows: all 20 U+0000 cases of the probe (10 patterns, bare and under `$not`) differed on `SqlDriver` over better-sqlite3, on `SqliteWasmDriver`, on `TursoDriver`'s local mode, and on its remote mode over a stub and over a real `@libsql/client` engine, with identical answers on all five. For example: - `$like: '%'` + U+0000 returned all 12 non-NULL rows, where `formula` returns the two ending in U+0000; - `$like: 'a'` + U+0000 + `'b'` also returned `'a'`; - `$ilike: 'AB'` + U+0000 also returned `'AB'` and `'ab'`. `driver-memory` answered all 20 as `formula` does. SQLite has no NUL-safe pattern primitive to compile to instead: `LIKE` cuts the same way, `replace()` cannot target U+0000, and `instr()` has no wildcards. So the one contract is a refusal, the way a pattern ending in a lone unpaired backslash is refused. **BREAKING** accept-set narrowing, shipped as `minor` under the repo's launch-window convention for breaking changes (`scripts/check-changeset-no-major.mjs`). **A filter that answered before is now refused**: a `$like` or `$ilike` pattern holding U+0000 anywhere (at the start, in the middle, at the end, alone, or after a backslash) gets `INVALID_FILTER` / 400, on every door that already refused the lone trailing backslash: - `@objectstack/driver-sql`: on the filter walk, before a dialect is chosen, so SQLite, Postgres and MySQL all refuse it. `@objectstack/driver-sqlite-wasm` and `TursoDriver`'s local mode inherit it; `@objectstack/driver-sqlite-wasm`'s own code does not change. - `@objectstack/driver-turso`: the remote transport's `$like` / `$ilike` arm, before anything is sent to the engine. - `@objectstack/driver-memory`: the shape gate of the query path and of the reference matcher `match()`, and the QueryAST `comparison` spelling (`like` / `ilike`). - `@objectstack/spec` exports the shared test, `hasNulInLikePattern`, beside `hasDanglingLikeEscape`, and the `$like` operator's description now names the refusal. On `driver-sql` and the Turso remote transport the refusal goes through the read-scope provenance seam, like every other filter-compile refusal there. On `driver-sql` (and so `driver-sqlite-wasm` and Turso's local mode), a caller whose predicate is marked `'author'` reads the operator, the field, the filter path and the pattern, with U+0000 written as `\u0000`. Any other caller gets only the class statement, and the rest goes to the server log. The remote transport withholds the same way, and through `TursoDriver` in remote mode no mark reaches it, so every caller gets the class statement there. On `driver-memory` every caller reads the full text, as for its dangling-escape refusal. A pattern that ends in a lone unpaired backslash AND holds U+0000 keeps the dangling-escape refusal it had before. **What stays accepted**, pinned per face: every `$like` / `$ilike` pattern without U+0000 answers exactly as before. **Not changed here:** - A pattern without U+0000 matched against a STORED value that holds U+0000 is not refused: it is well formed, and on the SQLite faces it reads the whole stored value, by its own entry in this release. - `@objectstack/formula` still evaluates such a pattern. It refuses nothing, and answers `false` for a dangling escape rather than refusing it, so it is not one of these doors. - `driver-mongodb`, objectql `having` and `service-analytics` refused every `$like` / `$ilike` before this change, and still do. **What an affected author does.** Remove the U+0000 from the pattern. No escape makes it portable: a backslash before it still leaves a U+0000 in the pattern. Blast radius, measured on this tree: no example or template writes a `$like` or `$ilike`, and the published `objectstack-query` skill and the hand-written docs that show one show no pattern holding U+0000. Whether any out-of-repo caller sends one is NOT measured and is not claimed to be zero. - 51efbf1: feat(driver-sql)!: a text operator over a column whose DECLARED type is temporal answers the type-gated no-match on every SQL face (#15683) **BREAKING** in the answer sense, on every SQL face, landing in the launch window as `minor` under the lockstep convention this cluster's siblings use. **The behaviour that GOES AWAY, by name: searching a date as a string.** On the SQLite family — `driver-sql` on any SQLite connection, `driver-sqlite-wasm`, and `driver-turso`'s local transport — a `Field.date` / `Field.datetime` / `Field.time` column stores canonical ISO TEXT (ADR-0053), and a text operator matched that text. `{ signed_on: { $contains: '2026' } }` returned every 2026 row; `{ made_at: { $startsWith: '2026-01' } }` returned that January's rows; `{ shift_at: { $contains: ':30' } }` returned every half-past shift. **All three now return nothing**, and their `$notContains` mirrors now return every valued row. If you are relying on any of them, this is a row-set change and the replacement is a range filter — spelled out below. The behaviour was never declared by any contract row and it never worked outside SQLite: the same three filters were a `DATABASE_ERROR` 500 on live Postgres. Nothing that was refused becomes admitted, and no new error code is minted — the refusal reused is the one `NON_TEXT_STORED_VALUE_TYPES` already carried for the numeric and boolean classes. Maintainer ruling, 2026-09-05 on #15683, quoted rather than paraphrased: 「a text operator over a column whose DECLARED type is temporal is type-gated exactly like the numeric and boolean classes; the SQLite ISO-text match is not a contract」. ## What was wrong — one filter, three answers across one driver family `{ on_day: { $contains: '2026' } }` over a column declared `Field.date` holding `2026-01-05`: | face | before | mechanism | |:--|:--|:--| | `driver-sql` / `driver-sqlite-wasm` / `driver-turso` local (SQLite) | **the row** | the column stores canonical ISO TEXT (ADR-0053), so `GLOB '*2026*'` matched it | | `driver-sql` on live PostgreSQL 16.13 | **`DATABASE_ERROR` 500** | `operator does not exist: date ~~ unknown` (SQLSTATE 42883) — the same for `timestamptz` and `time` | | `driver-sql` on MySQL | **NOT MEASURED** | no server was provisionable; reads as coercion via `CAST(col AS BINARY) LIKE` | Three answers to one filter, and no face declared which was canonical. The SQLite answer was the accident of a storage form, not a capability: the same query against Postgres was a 500. ## What it does now The three temporal classes join `NON_TEXT_STORED_VALUE_TYPES` (`@objectstack/spec`), the set the SQL compilers consult at compile time because the stored value is not visible until run time. Every face that reads it — `SqlDriver` (and everything that inherits its compiler), `driver-turso`'s remote transport, `service-analytics`' three SQL lowerings — compiles the positive operators (`$contains` / `$startsWith` / `$endsWith` / `$icontains` / `$like` / `$ilike`) to the FALSE constant and `$notContains` to the TRUE constant. Postgres's 500 becomes that declared answer; complementarity holds; the constants compose with the existing NULL-safe rules and the `$not` rewrite unchanged. **The SQLite ISO-substring match is RETIRED.** A caller who was using it to ask for "records in 2026" writes a range instead, which every dialect has always answered the same way: ```ts // before — matched only on the SQLite family, 500 on Postgres { on_day: { $contains: '2026' } } // after — the prescription, identical on every backend { on_day: { $gte: '2026-01-01', $lt: '2027-01-01' } } ``` ## Boundaries, so a reader does not over-read this - **A MULTI-VALUED temporal field is untouched.** `multiple: true` stores a JSON TEXT array, where `$contains` is the MEMBERSHIP spelling #7398 left working on a JSON column — not a substring test. It keeps compiling exactly as before. - **The value-keyed JS evaluators do not move, and they DIVERGE — measured, not caveated.** `driver-memory` canonicalises a declared temporal write to ISO TEXT (#4047), for a `Date` input and a string input alike, so a positive text operator MATCHES there — the exact complement of the answer this changeset declares. That divergence is filed as #17348 and pinned by name in that driver's conformance suite, alongside a correction: the two rows previously read as pinning the no-match answer pass because their comparand omits the milliseconds, not because anything type-gates. `formula` and `having` cannot key on the declaration at all — `matchesFilterCondition(record, filter)` takes a bare record ("this evaluator sees a bare record and has no schema to consult", its own docblock), and `having` filters AGGREGATED rows whose columns carry no field declaration. ⛔ So "on every face" is NOT delivered by this change, and this changeset does not claim it: the SQL family answers the declared rule, the JS faces do not yet. - **`FILTER_TEXT_CASES` grows no temporal column**, deliberately. Every row there is keyed on the STORED value — which is why its non-string column is a number and not a date — so a temporal fixture would assert one stored form across all five drivers that import it, the stored-form guarantee the ruling refused option (b) for. - **MySQL is NOT MEASURED**, not "passing": no server was provisionable, so its cell rests on the compiled-shape pin, which reads the constant a statement would carry without executing one. ### Patch Changes - fc6ddb8: fix(driver-sqlite-wasm): a text value now round-trips byte-for-byte, as it does through `SqlDriver` on better-sqlite3 — an embedded U+0000 no longer cuts the stored value short, and a leading U+FEFF is no longer dropped when the value is read (#19978) Clause-②: no `SqliteWasmDriver` changed a text value without raising, at two points in sql.js (measured on sql.js 1.14.1, the version the lockfile installs, against better-sqlite3, which round-trips every value below): - **Write.** sql.js binds a string with a length of `-1`, so SQLite stores it only up to the first U+0000: `'a'` + U+0000 + `'b'` was stored as the single byte `61`, and `'ab'` + U+0000 as `6162`. - **Read.** sql.js decodes a text cell up to the first NUL byte, through a decoder that drops a leading byte-order mark: a stored `610062` read back as `'a'`, and a stored text beginning with U+FEFF read back without it. A U+FEFF was always stored, because the write keeps it. What changes: - Every text cell the driver reads is decoded from its stored bytes, so a U+0000 anywhere in it and a U+FEFF at its start come back as stored. This includes values already on disk: a stored text that begins with U+FEFF now reads back with it. - A string value holding U+0000 is bound as its UTF-8 bytes, and the parameter that receives it becomes `+CAST( AS TEXT)`, so SQLite stores the same TEXT value better-sqlite3 stores, and compares it the same way. Positional `?`, numbered `?NNN` and named parameters are all numbered as SQLite numbers them. A statement that binds no such string runs exactly as before. - An equality filter on such a value now compares the whole value. Before, the comparand was cut at the same U+0000 as the stored value, so `{ v: 'a' }` also matched a row written as `'a'` + U+0000 + `'b'`. It no longer does. - The local `Field.json` storage backfill (`SqlDriver.backfillCanonicalJsonEncoding`) now converges a legacy json text cell holding a leading U+FEFF or an embedded U+0000 on this driver too: measured on the next `initObjects`, a stored `EFBBBF78` becomes `22EFBBBF7822` and a stored `610062` becomes `22615C75303030306222`, the same bytes better-sqlite3 writes, where before this change both were left as stored because sql.js did not read them back verbatim. - If the loaded sql.js has no `Statement.getBlob` (the one sql.js read that carries a byte length), reading a text cell throws instead of decoding through the lossy path. sql.js 1.14.1 has it in its Node, browser and debug builds. What does not change: a value already stored cut short stays cut short. The bytes after the U+0000 were never written, so nothing can restore them. - 9d81af7: fix(driver-sql, driver-turso): on SQLite, a `$contains` / `$notContains` / `$icontains` / `$startsWith` / `$endsWith` comparand holding U+0000 is compared whole, against the whole stored value, instead of being cut at the U+0000 by `GLOB` (#19999) Clause-②: no On the SQLite faces these five operators compile to `GLOB`, and SQLite's `glob()` reads both the pattern and the stored value only up to their first U+0000. Nothing raised, and the filter answered a different question. Measured on `SqlDriver` over better-sqlite3 (SQLite 3.53.4), on `SqliteWasmDriver` over sql.js (3.49.1), and on `TursoDriver`'s remote transport over a local libSQL engine (3.45.1). All three answered alike. Over the values `'a'` + U+0000 + `'b'`, `'ab'` + U+0000, U+0000 + `'z'`, `'plain'` and `''`: - `$contains: U+0000` and `$endsWith: U+0000` returned all five rows; - `$contains: U+0000 + 'b'` returned all five rows, where the JavaScript answer is `'a'` + U+0000 + `'b'` only; - `$startsWith: U+0000` returned `''` and U+0000 + `'z'`, where the JavaScript answer is U+0000 + `'z'` only. What changes: a comparand holding U+0000 now compiles to a length-aware comparison instead. `$contains`, `$notContains`, `$icontains` and `$startsWith` use `instr()`, and `$endsWith` compares the value's trailing bytes over BLOB. Such a filter now returns the rows `driver-memory` and `@objectstack/formula` return for it. The comparand is bound as written, so `*`, `?` and `[` in it are literal, as they were before. `$icontains` still folds ASCII letters only, and `$notContains` still returns a row whose value is NULL. - `@objectstack/driver-sql`: the SQLite arm of `SqlDriver`'s text-operator compiler. `SqliteWasmDriver` and `TursoDriver`'s local mode inherit it. - `@objectstack/driver-sqlite-wasm`: none of its own code changes. It inherits the fix, and its exact-text bind reaches every parameter the new comparison binds. - `@objectstack/driver-turso`: the remote transport's own emitter, changed the same way. What does not change: a comparand without U+0000 compiles to the same `GLOB` with the same bound pattern as before. The Postgres and MySQL arms are untouched. `GLOB` still reads a stored value only up to its first U+0000, so for a comparand without U+0000, `$contains`, `$notContains`, `$icontains` and `$endsWith` over a stored value that holds one still compare only the part before it. - 57c2b73: fix(driver-sql, driver-turso): four filter-refusal doors stop naming a read scope's field and comparand unless the refused predicate is marked as the caller's own (#20020) Clause-②: no A read scope is the RLS, sharing or tenant predicate that `plugin-security` (ordinary reads) and `service-analytics` (the ObjectQL analytics face) AND into the caller's `where`. Both merges mark the scope `'policy'` and the caller's own predicate `'author'` (`markFilterSubtreeProvenance`, `@objectstack/spec/data`). When `SqlDriver` refused a scope at one of the four doors below, the `INVALID_FILTER` / 400 message named the scope's field, and for three of them its comparand too. It did not check the mark. Measured on both faces, through `POST /api/v1/analytics/query` and through an ObjectQL `find` under a merge shaped like `plugin-security`'s: - a column the table does not have. This is reachable from a real CEL rule on a field that is declared but has no column yet; - a retired operator (`$regex`, `$options`) or an operator outside the vocabulary; - `$and` / `$or` whose operand is not a list; - a `$null` / `$exists` whose comparand is not a boolean. Each of these doors now reads the mark on the node it refused, the same way the cross-field and target-field refusals already did: - **`'policy'`, unmarked or ambiguous:** same `INVALID_FILTER` / 400. The message says which kind of refusal fired, but names no field, operator, comparand or filter path. Those go to the server log. For the unresolvable column, the message is the unnamed wording the driver already used when it could not parse the dialect's message. - **`'author'`:** the full message, the same text the door answered before. To find the node, the unresolvable-column door looks up the column name the database reported. It discloses only when every node that names that column is marked `'author'`. A `$and` / `$or` with a primitive operand is judged by the node that carries the key. `SqliteWasmDriver` (`@objectstack/driver-sqlite-wasm`) and `TursoDriver` in local mode extend `SqlDriver`, so they inherit this change from it: the same four doors answer the same way there. **What an unmarked caller loses:** its own diagnostic from these four doors. Measured cases where the caller's own predicate reaches the driver unmarked: - no security plugin in the stack; - a system-context call; - an anonymous call; - a `where` that holds a `{placeholder}` token, which the engine rewrites before the merge. That caller gets the withheld wording with the same code and status. A member's plain `where` under `plugin-security` is marked `'author'` and keeps the full text. The same three door classes on the Turso REMOTE transport (`RemoteTransport`) now read the mark too: the retired or unknown operator (including a non-operator key in an operator map), the non-list combinator, and the non-boolean `$null` / `$exists`. The operands go to its diagnostic sink. `TursoDriver`'s remote mode rebuilds every filter node before the transport sees it, so no mark reaches the transport there, and these refusals keep the withheld wording for every caller in that mode. The unresolvable WHERE column has no refusal on the remote face (the transport answers `[]`) and is not changed here. Not changed: which filters are refused, and the code and status of every refusal. The engine's declared-type, temporal-comparand and filter-token doors are not changed here. - f09d412: fix(driver-sql, driver-turso): on SQLite, `$like` / `$ilike` read the whole stored value, instead of stopping at its first U+0000 (#20024) Clause-②: no On the SQLite faces `$like` and `$ilike` compiled to `GLOB`, and SQLite's `glob()` reads the stored value only up to its first U+0000. So a pattern without U+0000 answered a different question over a value holding one, and nothing raised. Measured on `SqlDriver` over better-sqlite3 (SQLite 3.53.4), on `SqliteWasmDriver` over sql.js (3.49.1), on `TursoDriver`'s local mode, and on its remote transport over a local libSQL engine (3.45.1). All four answered alike: - `$like: 'a'` returned a value stored as `'a'` + U+0000 + `'b'`, and `$like: ''` returned U+0000 + `'z'`; - `$like: '%b'`, `$like: 'a_b'` and `$ilike: 'A_B'` did not return `'a'` + U+0000 + `'b'`; - `$like: '_'` did not return a value that is a lone U+0000. Over 108 patterns and 22 `$not` / `$or` / `$and` compositions against 59 stored values, 359 of the 3380 cells over values holding U+0000 differed from `@objectstack/formula` on each face. What changes: a stored value holding U+0000 now has each U+0000 replaced by one stand-in character before `GLOB` reads it. The stand-in is never a literal character of the pattern, never an ASCII letter, and never U+0000. A U+0000 in the value can only be matched by `%` or `_`, and so can the stand-in, so the answer is the one the whole value gives. Such a filter now returns the rows `driver-memory` and `@objectstack/formula` return for it, under `$not`, `$or` and `$and` as well: 0 of those 3380 cells differ on any of the four faces. `$ilike` still folds ASCII letters only. - `@objectstack/driver-sql`: the SQLite arm of `SqlDriver`'s `$like` / `$ilike` compiler. `SqliteWasmDriver` and `TursoDriver`'s local mode inherit it. - `@objectstack/driver-sqlite-wasm`: none of its own code changes. It inherits the fix. - `@objectstack/driver-turso`: the remote transport's own emitter, changed the same way. What does not change: - A stored value without U+0000 gets the same answer as before: 0 of 16640 such cells moved on any face. - A pattern that is a literal prefix followed only by `%` (`'ab%'`, `'%'`) compiles to the same `GLOB` with the same bound pattern as before. Cutting the value at its first U+0000 cannot change that answer. - No index is lost. Under `EXPLAIN QUERY PLAN` over an indexed TEXT column on all three engines, each `$like` pattern measured that starts with a literal (`'ab%'`, `'ab_'`, `'ab%cd'`, `'abc'`, `'a%b%'`) keeps its covering-index search, and each one that starts with a wildcard still scans. A case-exact pattern with a literal prefix now leads with a `GLOB` on that prefix followed by `*`, which every matching value satisfies and which is what keeps that search. - `_` still matches one character, as `GLOB`'s `?` does. A character outside the Basic Multilingual Plane is one character to `_` on SQLite and two to `@objectstack/formula`, which counts UTF-16 units. That difference is older than this change, and this change does not alter it. - A pattern holding U+0000 is still refused (`INVALID_FILTER` / 400). - The Postgres and MySQL arms are untouched. Cost, measured over 10,000 rows on the three engines: against a value without U+0000 the new compile adds one `instr()` per row, and those queries took 1.1 to 2.4 times as long as `GLOB` alone, at most 4.5 ms. A value holding U+0000 pays the rewrite: 10,000 rows each holding one to three U+0000 took up to 35 ms, against at most 3 ms for `GLOB`. - adbbc5d: fix(driver-sql, driver-turso): on SQLite, `$contains` / `$notContains` / `$icontains` / `$endsWith` read the whole stored value, instead of stopping at its first U+0000 (#20024) Clause-②: no On the SQLite faces these four operators compiled to `GLOB` for a comparand without U+0000, and SQLite's `glob()` reads the stored value only up to its first U+0000. Nothing raised, and the filter answered a different question. Measured on `SqlDriver` over better-sqlite3 (SQLite 3.53.4), on `SqliteWasmDriver` over sql.js (3.49.1), on `TursoDriver`'s local mode, and on its remote transport over a local libSQL engine (3.45.1). All four answered alike: - `$contains: 'b'` did not return a value stored as `'a'` + U+0000 + `'b'`; - `$endsWith: 'a'` returned that value, and `$endsWith: 'b'` did not; - `$notContains: 'b'` returned it; - `$icontains: 'B'` did not return `'A'` + U+0000 + `'B'`. What changes: these four operators now compile to the length-aware comparisons a comparand holding U+0000 already used, for every comparand. `$contains`, `$notContains` and `$icontains` use `instr()`, and `$endsWith` compares the value's trailing bytes over BLOB. An empty `$endsWith` comparand uses `instr()` too, so it still matches every non-NULL value. Such a filter now returns the rows `driver-memory` and `@objectstack/formula` return for it, under `$not`, `$or` and `$and` as well. The comparand is bound as written, so `*`, `?` and `[` in it are literal, as they were before. `$icontains` still folds ASCII letters only, and `$notContains` still returns a row whose value is NULL. - `@objectstack/driver-sql`: the SQLite arm of `SqlDriver`'s text-operator compiler. `SqliteWasmDriver` and `TursoDriver`'s local mode inherit it. - `@objectstack/driver-sqlite-wasm`: none of its own code changes. It inherits the fix. - `@objectstack/driver-turso`: the remote transport's own emitter, changed the same way. What does not change: - `$startsWith` with a comparand without U+0000 compiles to the same `GLOB` with the same bound pattern as before. The stored value's cut cannot change its answer. - No index is lost. The SQL `SqlDriver` compiles, run under `EXPLAIN QUERY PLAN` over an indexed TEXT column on all three engines, scanned the table for these four operators under `GLOB` and still does; `$startsWith` keeps its index search. - The Postgres and MySQL arms are untouched. - `$like` and `$ilike` are outside this entry. Two other entries in this release cover them: on SQLite they now read the whole stored value as well, and every driver that answers `$like` refuses a pattern holding U+0000 (`INVALID_FILTER` / 400). - 8d76c2d: fix(driver-sql, driver-turso): every filter-compile refusal stops naming a read scope's field or literal unless the refused predicate is marked as the caller's own (#20039) Clause-②: no A read scope is the RLS, sharing or tenant predicate that `plugin-security` (ordinary reads) and `service-analytics` (the ObjectQL analytics face) AND into the caller's `where`. Both merges mark the scope `'policy'` and the caller's own predicate `'author'` (`markFilterSubtreeProvenance`, `@objectstack/spec/data`). Nine more `SqlDriver` filter-compile refusals did not check the mark, so when one of them refused a scope, its `INVALID_FILTER` / 400 message named the scope's field, and for most of them its literal too. Measured through an ObjectQL `find` under a merge shaped like `plugin-security`'s, with the scope in the `'policy'` arm: - an empty or non-string `$icontains` comparand; - a non-string `$like` / `$ilike` comparand; - a `$like` / `$ilike` pattern ending in a lone backslash; - an object or array comparand on `$contains`, `$notContains`, `$startsWith`, `$endsWith` or `$icontains`; - an `$in` / `$nin` / `$between` member that cannot be bound; - an `undefined` comparand, in any position; - an element of `$and` / `$or`, or the operand of `$not`, that is not a filter condition object; - a `$`-prefixed key in a node position that is not `$and`, `$or` or `$not`; - a `where` that reaches the driver as an array (the message printed the whole array). Each of them now reads the mark on the node it was raised from, as the other compile refusals already did: - **`'policy'`, unmarked or ambiguous:** same `INVALID_FILTER` / 400. The message says which kind of refusal fired, but names no field, operator variant, comparand, list position or filter path. Those go to the server log. - **`'author'`:** the full message, the same text the refusal answered before. With these nine, every refusal on `SqlDriver`'s filter-compile path goes through the same seam. `SqliteWasmDriver` (`@objectstack/driver-sqlite-wasm`) and `TursoDriver` in local mode extend `SqlDriver`, so they inherit this change from it: the same refusals answer the same way there. **What an unmarked caller loses:** its own diagnostic from these refusals. That is every caller whose predicate reaches the driver unmarked, for example with no security plugin in the stack, in a system-context or anonymous call, or with a `where` that holds a `{placeholder}` token (the engine rewrites it before the merge). That caller gets the withheld wording with the same code and status, and the full text is in the server log. A member's plain `where` under `plugin-security` is marked `'author'` and keeps the full text. The Turso REMOTE transport (`RemoteTransport`) compiles filters itself. Its copies of these refusals now read the mark the same way: the `$icontains`, `$like` / `$ilike`, lone-backslash, `undefined`, non-node element or operand, undeclared-key and non-object `where` refusals. So do its two other compile refusals that still named the field: an operator map with no operator in it, and a `$between` that reached the transport without being lowered. The operands go to its diagnostic sink. For six of these classes, the withheld sentence is the local one behind the `[RemoteTransport]` prefix. An object text comparand and an unbindable list member already answered there through its comparand refusal, which withholds. `TursoDriver`'s remote mode rebuilds every filter node before the transport sees it, so no mark reaches the transport there, and these refusals keep the withheld wording for every caller in that mode. Not changed: which filters are refused, and the code and status of every refusal. - Updated dependencies [863c7c4] - Updated dependencies [0f95f43] - Updated dependencies [825d70f] - Updated dependencies [6057357] - Updated dependencies [a60e04d] - Updated dependencies [abc4b83] - Updated dependencies [7382c5d] - Updated dependencies [ea2940d] - Updated dependencies [7d0f911] - Updated dependencies [48f5200] - Updated dependencies [245f360] - Updated dependencies [d0f1845] - Updated dependencies [9dcdb77] - Updated dependencies [6175da8] - Updated dependencies [0283cb9] - Updated dependencies [324968e] - Updated dependencies [7843663] - Updated dependencies [ce57857] - Updated dependencies [744a0a3] - Updated dependencies [c7d4825] - Updated dependencies [4844840] - Updated dependencies [fe71032] - Updated dependencies [74eaab8] - Updated dependencies [0b788da] - Updated dependencies [f7a3495] - Updated dependencies [97f4f8c] - Updated dependencies [482d34d] - Updated dependencies [7a25a3e] - Updated dependencies [839d1b0] - Updated dependencies [2fc092b] - Updated dependencies [2dfe070] - Updated dependencies [6059b29] - Updated dependencies [88a072e] - Updated dependencies [d4a1a28] - Updated dependencies [baf9745] - Updated dependencies [3d8779d] - Updated dependencies [0bd7dae] - Updated dependencies [d34f9b6] - Updated dependencies [57343f7] - Updated dependencies [271d6bb] - Updated dependencies [1e20f81] - Updated dependencies [38472ce] - Updated dependencies [8b48903] - Updated dependencies [2d235bc] - Updated dependencies [aaacf1d] - Updated dependencies [6548118] - Updated dependencies [9dacf61] - Updated dependencies [146c291] - Updated dependencies [4db1bf1] - Updated dependencies [e0e4a56] - Updated dependencies [7aae005] - Updated dependencies [bdb247d] - Updated dependencies [d5c91dd] - Updated dependencies [32be735] - Updated dependencies [0e51278] - Updated dependencies [48203ff] - Updated dependencies [ada2869] - Updated dependencies [d88a47d] - Updated dependencies [2f1a6f6] - Updated dependencies [23fc5d6] - Updated dependencies [2d34f32] - Updated dependencies [7b1e4a4] - Updated dependencies [d7c0241] - Updated dependencies [9e3c485] - Updated dependencies [82cb69f] - Updated dependencies [e1796ad] - Updated dependencies [8271c81] - Updated dependencies [c9eb773] - Updated dependencies [fbc12be] - Updated dependencies [ec2ede0] - Updated dependencies [4342c99] - Updated dependencies [132dd13] - Updated dependencies [d285bf0] - Updated dependencies [dfeba25] - Updated dependencies [9059a94] - Updated dependencies [0a88a80] - Updated dependencies [2c1011b] - Updated dependencies [12bb672] - Updated dependencies [97233b9] - Updated dependencies [c199772] - Updated dependencies [f5a7250] - Updated dependencies [1a2bb9e] - Updated dependencies [eea7ccc] - Updated dependencies [097d268] - Updated dependencies [182bbde] - Updated dependencies [5ce3705] - Updated dependencies [24d622b] - Updated dependencies [0252320] - Updated dependencies [2eb4724] - Updated dependencies [d46deba] - Updated dependencies [e04a0af] - Updated dependencies [6b97a20] - Updated dependencies [e7ff9c2] - Updated dependencies [75237a9] - Updated dependencies [920f887] - Updated dependencies [497655f] - Updated dependencies [7c2c5ae] - Updated dependencies [ada7012] - Updated dependencies [3a9ad22] - Updated dependencies [be5c602] - Updated dependencies [6d2571f] - Updated dependencies [2bf6ef1] - Updated dependencies [092d460] - Updated dependencies [09e16a5] - Updated dependencies [98bd798] - Updated dependencies [cbcae14] - Updated dependencies [8261ff7] - Updated dependencies [24489f1] - Updated dependencies [fc28c1d] - Updated dependencies [6d64785] - Updated dependencies [00c332b] - Updated dependencies [b3b43b6] - Updated dependencies [d93400f] - Updated dependencies [b1d3945] - Updated dependencies [9ccc417] - Updated dependencies [134b410] - Updated dependencies [84e6b05] - Updated dependencies [cb1f274] - Updated dependencies [5c28cc7] - Updated dependencies [b0eb9a5] - Updated dependencies [e233db9] - Updated dependencies [176b035] - Updated dependencies [a83dbb6] - Updated dependencies [d3a2331] - Updated dependencies [51297e9] - Updated dependencies [2d892dd] - Updated dependencies [156792e] - Updated dependencies [5ba2ec3] - Updated dependencies [abb01f1] - Updated dependencies [e64ae15] - Updated dependencies [02bdeaa] - Updated dependencies [66abef3] - Updated dependencies [25c9a83] - Updated dependencies [ee5812a] - Updated dependencies [68fea8b] - Updated dependencies [c049e74] - Updated dependencies [bb9794a] - Updated dependencies [d402e32] - Updated dependencies [63a8eb4] - Updated dependencies [9a910c4] - Updated dependencies [adabccf] - Updated dependencies [340b6dc] - Updated dependencies [fe0ae5c] - Updated dependencies [99fcb4a] - Updated dependencies [55095cc] - Updated dependencies [0f1cd83] - Updated dependencies [a3d4c59] - Updated dependencies [74832b6] - Updated dependencies [1aa5026] - Updated dependencies [2b80461] - Updated dependencies [2bdb81f] - Updated dependencies [b9d5422] - Updated dependencies [c7448dc] - Updated dependencies [627382b] - Updated dependencies [0b31d90] - Updated dependencies [4b58dcf] - Updated dependencies [c23cfb3] - Updated dependencies [559041d] - Updated dependencies [e0d0553] - Updated dependencies [5100c42] - Updated dependencies [596090e] - Updated dependencies [5380daa] - Updated dependencies [00b38d7] - Updated dependencies [47a9002] - Updated dependencies [7056ca5] - Updated dependencies [731f020] - Updated dependencies [5eebc9e] - Updated dependencies [72c1640] - Updated dependencies [5e5ec9f] - Updated dependencies [170fd83] - Updated dependencies [922923b] - Updated dependencies [2cac363] - Updated dependencies [fc91239] - Updated dependencies [e6c34f6] - Updated dependencies [062f5cd] - Updated dependencies [0318faf] - Updated dependencies [5d8319f] - Updated dependencies [43f4766] - Updated dependencies [8e8ea99] - Updated dependencies [a484966] - Updated dependencies [021755a] - Updated dependencies [b929e0a] - Updated dependencies [dbd4744] - Updated dependencies [14a762f] - Updated dependencies [b146102] - Updated dependencies [75c0dac] - Updated dependencies [9bb059d] - Updated dependencies [07c6f82] - Updated dependencies [502f179] - Updated dependencies [f20fe29] - Updated dependencies [362035c] - Updated dependencies [7e0bfce] - Updated dependencies [c120dbd] - Updated dependencies [32b5831] - Updated dependencies [74554a3] - Updated dependencies [e56112c] - Updated dependencies [aeaaa44] - Updated dependencies [43460b9] - Updated dependencies [44a2332] - Updated dependencies [f34dda6] - Updated dependencies [488f4f5] - Updated dependencies [15f9284] - Updated dependencies [a4ca69a] - Updated dependencies [1ff3a8f] - Updated dependencies [61dd96f] - Updated dependencies [b971924] - Updated dependencies [6afa59d] - Updated dependencies [e37ea4d] - Updated dependencies [8f6d831] - Updated dependencies [fa29803] - Updated dependencies [b01bdbc] - Updated dependencies [adbdbc5] - Updated dependencies [6cc8dcd] - Updated dependencies [ba77509] - Updated dependencies [408ca2e] - Updated dependencies [ec292cf] - Updated dependencies [dc0ab6a] - Updated dependencies [19e58e2] - Updated dependencies [7e1b048] - Updated dependencies [342808c] - Updated dependencies [b3615f1] - Updated dependencies [0b4022b] - Updated dependencies [a60c913] - Updated dependencies [5c5b67f] - Updated dependencies [3f9e2ea] - Updated dependencies [77f54bf] - Updated dependencies [ccccdcc] - Updated dependencies [48c91e9] - Updated dependencies [2b52a5b] - Updated dependencies [0f057b6] - Updated dependencies [3875ae6] - Updated dependencies [1c16889] - Updated dependencies [1912237] - Updated dependencies [fc29c74] - Updated dependencies [95fb417] - Updated dependencies [4ec3987] - Updated dependencies [5b9402d] - Updated dependencies [2cf9db7] - Updated dependencies [dc1b986] - Updated dependencies [655e8c0] - Updated dependencies [041c8cf] - Updated dependencies [e3277c3] - Updated dependencies [cc6dfd9] - Updated dependencies [7536721] - Updated dependencies [9df3934] - Updated dependencies [0b83e01] - Updated dependencies [ebc6afe] - Updated dependencies [6696056] - Updated dependencies [0e06f3b] - Updated dependencies [c1dfa52] - Updated dependencies [2548ba5] - Updated dependencies [9282578] - Updated dependencies [ecf90b2] - Updated dependencies [90ff10a] - Updated dependencies [2bbebf5] - Updated dependencies [369bcbe] - Updated dependencies [3bd28e2] - Updated dependencies [beac798] - Updated dependencies [9347c1f] - Updated dependencies [c164186] - Updated dependencies [e7344f0] - Updated dependencies [4d7e740] - Updated dependencies [de091b5] - Updated dependencies [6aa3188] - Updated dependencies [ae7a35a] - Updated dependencies [9bfbacb] - Updated dependencies [cf55914] - Updated dependencies [17bd318] - Updated dependencies [681868c] - Updated dependencies [a9fb83e] - Updated dependencies [2274894] - Updated dependencies [e462186] - Updated dependencies [b5853da] - Updated dependencies [4ac9319] - Updated dependencies [560b724] - Updated dependencies [16c5473] - Updated dependencies [b276d44] - Updated dependencies [3f86dc5] - Updated dependencies [172b4cf] - Updated dependencies [67c98f6] - Updated dependencies [b98fbc2] - Updated dependencies [9d81af7] - Updated dependencies [e7f69db] - Updated dependencies [84156c7] - Updated dependencies [57c2b73] - Updated dependencies [f09d412] - Updated dependencies [adbbc5d] - Updated dependencies [e0f17a3] - Updated dependencies [0bf85ea] - Updated dependencies [1df29df] - Updated dependencies [8d76c2d] - Updated dependencies [8a44ce7] - Updated dependencies [ca753c0] - Updated dependencies [8ecbe0f] - Updated dependencies [6a4aec7] - Updated dependencies [e4471e6] - Updated dependencies [e8fcf55] - Updated dependencies [fe677ae] - Updated dependencies [8d1f7ab] - Updated dependencies [e01d347] - Updated dependencies [cfc3bcf] - Updated dependencies [dd1b803] - Updated dependencies [03d6cb0] - Updated dependencies [9e7824a] - Updated dependencies [437bb0d] - Updated dependencies [49144fc] - Updated dependencies [e2c4e12] - Updated dependencies [08c8484] - Updated dependencies [93cfc3f] - Updated dependencies [6ac33a5] - Updated dependencies [443b2f4] - Updated dependencies [7e7fab7] - Updated dependencies [b09ce67] - Updated dependencies [4df101c] - Updated dependencies [6a6a17b] - Updated dependencies [733822c] - Updated dependencies [e5cf27d] - Updated dependencies [a91d12a] - Updated dependencies [bea6d2e] - Updated dependencies [f415bcf] - Updated dependencies [615c468] - Updated dependencies [5f9d7d7] - Updated dependencies [31d281d] - Updated dependencies [569d4d2] - Updated dependencies [9e9bb46] - Updated dependencies [0d7ed5a] - Updated dependencies [2aa25ef] - Updated dependencies [0e1afe8] - Updated dependencies [288611e] - Updated dependencies [dfd8e39] - Updated dependencies [89f87f2] - Updated dependencies [28ad7e4] - Updated dependencies [e6b7d8c] - Updated dependencies [3062e50] - Updated dependencies [40b315b] - Updated dependencies [d3958ba] - Updated dependencies [f2c7eef] - Updated dependencies [7e36a3c] - Updated dependencies [5a6267f] - Updated dependencies [0bbe400] - Updated dependencies [862b6ce] - Updated dependencies [80153f5] - Updated dependencies [26daf0b] - Updated dependencies [826f327] - Updated dependencies [7e5246d] - Updated dependencies [b810ddb] - Updated dependencies [7dc45eb] - Updated dependencies [17e4f52] - Updated dependencies [dcd3bce] - Updated dependencies [2d91c9a] - Updated dependencies [15bf186] - Updated dependencies [b285508] - Updated dependencies [2c31070] - Updated dependencies [7db1332] - Updated dependencies [aeb0557] - Updated dependencies [1c1b8c8] - Updated dependencies [05077d4] - Updated dependencies [ba5927f] - Updated dependencies [75b2169] - Updated dependencies [de8c973] - Updated dependencies [fc0db22] - Updated dependencies [65352b7] - Updated dependencies [e956924] - Updated dependencies [2304b16] - Updated dependencies [5b674f5] - Updated dependencies [c7ad16f] - Updated dependencies [48efe91] - Updated dependencies [fb38607] - Updated dependencies [dc07593] - Updated dependencies [e967cbd] - Updated dependencies [8255a51] - Updated dependencies [d1c01ff] - Updated dependencies [9e1689f] - Updated dependencies [b057434] - Updated dependencies [f6ceddc] - Updated dependencies [40626bd] - Updated dependencies [4c42fd1] - Updated dependencies [5f392f0] - Updated dependencies [a362e0e] - Updated dependencies [f26fb8e] - Updated dependencies [bc2ec80] - Updated dependencies [0da638c] - Updated dependencies [041d9fd] - Updated dependencies [f03f6c7] - Updated dependencies [b8ec127] - Updated dependencies [cf79182] - Updated dependencies [e81c4e5] - Updated dependencies [28f9277] - Updated dependencies [929d9e3] - Updated dependencies [8a5240a] - Updated dependencies [c1d54db] - Updated dependencies [c7af6bd] - Updated dependencies [1f0b565] - Updated dependencies [23aa83c] - Updated dependencies [357f499] - Updated dependencies [80aef80] - Updated dependencies [65ad77d] - Updated dependencies [88a9330] - Updated dependencies [3cbcedb] - Updated dependencies [a61ae59] - Updated dependencies [fb59fb5] - Updated dependencies [a54ecaa] - Updated dependencies [854639b] - Updated dependencies [44c917a] - Updated dependencies [613d35a] - Updated dependencies [e08c8b0] - Updated dependencies [0ee32ed] - Updated dependencies [2bed4c3] - Updated dependencies [77c801e] - Updated dependencies [58b36fa] - Updated dependencies [4792049] - Updated dependencies [53ec0b1] - Updated dependencies [71629a1] - Updated dependencies [0a56d3b] - Updated dependencies [f8e5790] - Updated dependencies [d2c1d19] - Updated dependencies [681871e] - Updated dependencies [54e8234] - Updated dependencies [d127f9b] - Updated dependencies [4bbf766] - Updated dependencies [c17b494] - Updated dependencies [d414e2b] - Updated dependencies [af98a04] - Updated dependencies [43cbe14] - Updated dependencies [c86d351] - Updated dependencies [6e3e546] - Updated dependencies [c4d1759] - Updated dependencies [f7a9740] - Updated dependencies [96451ec] - Updated dependencies [0f38ab0] - Updated dependencies [9cdffbe] - Updated dependencies [331a1a2] - Updated dependencies [9788f1e] - Updated dependencies [3cf6449] - Updated dependencies [3cf6449] - Updated dependencies [2bd53f1] - Updated dependencies [5f9f846] - Updated dependencies [5a95b0e] - Updated dependencies [5d527f7] - Updated dependencies [5bf2330] - Updated dependencies [9165d5c] - Updated dependencies [d9e1587] - Updated dependencies [07150b3] - Updated dependencies [143c715] - Updated dependencies [fb2bccf] - Updated dependencies [d2badf7] - Updated dependencies [d64bcb6] - Updated dependencies [d4f5232] - Updated dependencies [396eae3] - Updated dependencies [ecdfc94] - Updated dependencies [f04be62] - Updated dependencies [de1a611] - Updated dependencies [4fba503] - Updated dependencies [db76982] - Updated dependencies [5cf58eb] - Updated dependencies [66e266c] - Updated dependencies [3b1dab9] - Updated dependencies [7607076] - Updated dependencies [1555ed4] - Updated dependencies [776d64c] - Updated dependencies [03b19d9] - Updated dependencies [6154165] - Updated dependencies [199002b] - Updated dependencies [ab450f4] - Updated dependencies [21ab410] - Updated dependencies [025588a] - Updated dependencies [a49e8ae] - Updated dependencies [f3e3d59] - Updated dependencies [9bd4344] - Updated dependencies [51efbf1] - Updated dependencies [9c44eed] - Updated dependencies [bbca441] - Updated dependencies [7cd5874] - Updated dependencies [3cb84d0] - Updated dependencies [119a02b] - Updated dependencies [eea8787] - Updated dependencies [7887077] - Updated dependencies [29dd1a6] - @objectstack/spec@17.5.0 - @objectstack/core@17.5.0 - @objectstack/driver-sql@17.5.0 ## 17.4.0 ### Minor Changes - 7862fb7: `SqliteWasmDriver.initObjects` accepts `tenancy`, `indexes` and `lifecycle` in a **fresh object literal**, inherited from the widened `SqlDriver` — and that inheritance is now asserted rather than assumed. This package overrides neither `initObjects` nor `registerObjectMetadata`, so its published `.d.ts` re-declares none of them and the door it exposes is `SqlDriver`'s, imported from `@objectstack/driver-sql`. Measured on the built declarations: zero re-declarations of `initObjects`, `registerObjectMetadata`, `rotateShards`, `ensureShardTable` or `registerManagedObjectMetadata`. That is the opposite direction of the defect the sibling packages carried — `TursoDriver` overrode `initObjects` with a narrower literal and shadowed a base-class fix for five weeks — and it is recorded here because a consumer reading only this package's changelog would otherwise never learn its accept set moved. `src/sqlite-wasm-16711-inherited-object-def-keys.test.ts` pins the inheritance inside this package's own tsc program: the inherited parameter is not `any`, each key is present on the element type, a fresh literal carrying them compiles and is read at run time, and a misspelling is still `TS2353`. It goes red both ways — if the base narrows again, and if a future override here re-declares the door more narrowly. - b72226f: `SqlDriver.initObjects()` and `SqlDriver.registerObjectMetadata()` now declare the `indexes` key they have always read. Both entry points took `Array<{ name; fields?; tenancy? }>`, with no `indexes` in the type. The key was read out of those very objects one call deep anyway, through an `as any`, in `registerManagedObjectMetadata` — and the map it fills, `managedObjectIndexes`, is what `syncDeclaredIndexes` renders every declared UNIQUE from. So the driver's whole index-sync path was driven by a key its own signature said did not exist, while the sibling `detectManagedDrift` on the same class had always declared `indexes?: any[]`: the two halves of one class disagreed about the shape of the same input. That is the shape #4311 already addressed for `tenancy`, one key over, and the comment it left above `initObjects` described `indexes` word for word. **Why nothing tripped over it.** TypeScript's excess-property check fires on a fresh object literal and not on one bound to a variable first, so the same object was accepted or rejected by nothing but where it was spelled — `await driver.initObjects([{ ...bare, indexes: [] }])` was rejected with TS2353, `const o = { ...bare, indexes: [] }; await driver.initObjects([o])` was accepted, and the index was synced either way. Every caller happened to bind first, so the package typechecked green for a reason unrelated to correctness. **Why this matters beyond a compile error.** The loud symptom was a rejected correct call. The quiet one is the reachable branch: an author — or an AI — reading the signature concludes `indexes` is not accepted and drops the key, and a declared UNIQUE is then never synced, with no error at authoring time and no error at boot. The schema says those rows cannot collide; they can. What changed, all inside `SqlDriver`: - `registerObjectMetadata(objects)`, `initObjects(objects)` and the shared `registerManagedObjectMetadata(obj)` helper each gained `indexes?: any[]`, spelled exactly as `detectManagedDrift` already spells it. - Every `(obj as any)` cast reading `indexes` off those parameters is gone — the one at the `managedObjectIndexes.set` site and the two inside `initObjects`' own create/alter path. The cast was the evidence that the declaration and the read disagreed; leaving any of them would have fixed the signature while keeping the "the type does not admit me but I read it anyway" path alive. That path is now closed on this parameter. **What the accept set does, precisely — it moves in both directions.** For a **fresh object literal**, which is what an author writes and what the excess-property check judges, this is purely a widening: `{ ...bare, indexes: [...] }` was rejected and is now accepted. For a **variable-bound** argument, which bypasses that check and is judged by ordinary assignability, it is a narrowing: `indexes` spelled as a record, as a `readonly` tuple (`as const`), or as `null` compiled under the previous signatures and is now rejected with TS2322. Measured in both directions, all three shapes, on this package's own `tsc`. That narrowing is deliberate, and the three shapes did **not** all behave the same way before it — the difference is worth stating exactly, because only one of them ever worked: - A **record** and **`null`** never survived the `Array.isArray(obj.indexes)` guard the driver has always applied. That author got no index and no diagnostic — silently, at run time. Rejecting those two at compile time is precisely the failure this change exists to make impossible. - A **`readonly` tuple (`as const`)** is a different case, and the only one with anything to lose. `as const` is type-only: at run time the value is a plain array, `Array.isArray` returns `true`, and the index **was** synced. That caller compiled and worked, and is now rejected at compile time. Nothing about its run-time behaviour changed — the rejection is entirely on the type surface. No migration is owed even so. No caller in this repository is affected, and the shape could never have reached `detectManagedDrift` on the same class either, which publishes the very same `any[]` spelling for the very same key — so a `readonly` caller was already unable to use half of this driver's declared-index surface. A caller in that position spells the array without `as const`, or widens it at the call site. The disposition on that corrected ground, recorded here because the ground itself moved: **no `BREAKING` banner and no ADR-0087 disposition**, resting on grounds (i) and (iii) alone — zero affected callers, and the `any[]` spelling already published on `detectManagedDrift` for the same key on the same class. The ground that every newly rejected shape had already been discarded at run time is **not** among them: it is false for the `readonly` tuple, and nothing here leans on it. `@objectstack/driver-sqlite-wasm` is named because `SqliteWasmDriver extends SqlDriver` and overrides neither method, so both widened signatures land in its own published `.d.ts` and its consumers see the identical change. The two packages are in the same fixed version group, so this is a CHANGELOG effect rather than a version one. The `IDataDriver` contract itself did not move: `registerObjectMetadata?(schemas: unknown[])` in `@objectstack/spec` already accepted `unknown[]`, and `SqlDriver` narrowed it on its own. What grew is `SqlDriver`'s own published accept set. ### Patch Changes - Updated dependencies [fe0d9a4] - Updated dependencies [ecd2158] - Updated dependencies [f2b5e46] - Updated dependencies [2ed6be6] - Updated dependencies [ed7243d] - Updated dependencies [6ba0db4] - Updated dependencies [625b0c3] - Updated dependencies [233222e] - Updated dependencies [07f40e5] - Updated dependencies [54bb2f1] - Updated dependencies [ceb4877] - Updated dependencies [e9fcd6b] - Updated dependencies [90e7e6d] - Updated dependencies [2bdabe6] - Updated dependencies [ca326b5] - Updated dependencies [8f404a5] - Updated dependencies [68437d4] - Updated dependencies [abb140c] - Updated dependencies [8333a6c] - Updated dependencies [3e3ecb0] - Updated dependencies [3030369] - Updated dependencies [d5d8d50] - Updated dependencies [e08892d] - Updated dependencies [ae05f2e] - Updated dependencies [b548e43] - Updated dependencies [c463d03] - Updated dependencies [64bd6a3] - Updated dependencies [13c48c2] - Updated dependencies [b0529e1] - Updated dependencies [66dc6ab] - Updated dependencies [6f94458] - Updated dependencies [6e67b86] - Updated dependencies [132742f] - Updated dependencies [85a2459] - Updated dependencies [50dc214] - Updated dependencies [e89fa92] - Updated dependencies [e9fcd6b] - Updated dependencies [8976ea1] - Updated dependencies [56fe8c2] - Updated dependencies [acabd24] - Updated dependencies [ab50c8f] - Updated dependencies [6491463] - Updated dependencies [89cf4d6] - Updated dependencies [21c5dcb] - Updated dependencies [001a83b] - Updated dependencies [6d4d5d3] - Updated dependencies [45cfa1b] - Updated dependencies [7862fb7] - Updated dependencies [1ca95df] - Updated dependencies [a646120] - Updated dependencies [2200f8e] - Updated dependencies [ed5d557] - Updated dependencies [bca21f7] - Updated dependencies [e9fcd6b] - Updated dependencies [2025b1f] - Updated dependencies [1a7a7c9] - Updated dependencies [e9fcd6b] - Updated dependencies [ef3a138] - Updated dependencies [68d5dfd] - Updated dependencies [3e21cf0] - Updated dependencies [4cfc93b] - Updated dependencies [efd6b43] - Updated dependencies [859ded3] - Updated dependencies [fa125f3] - Updated dependencies [74628d9] - Updated dependencies [a646120] - Updated dependencies [6f1ce7d] - Updated dependencies [7778115] - Updated dependencies [2c753fe] - Updated dependencies [52804cd] - Updated dependencies [3f89967] - Updated dependencies [53cf263] - Updated dependencies [21aabbc] - Updated dependencies [9c270bb] - Updated dependencies [76c8c5a] - Updated dependencies [8f2ecb3] - Updated dependencies [a84e1ce] - Updated dependencies [bf1054a] - Updated dependencies [d8d2776] - Updated dependencies [222dc0f] - Updated dependencies [e9fcd6b] - Updated dependencies [32c917d] - Updated dependencies [f9a3c32] - Updated dependencies [f502898] - Updated dependencies [51ae731] - Updated dependencies [af7edfe] - Updated dependencies [b60f48b] - Updated dependencies [c78c918] - Updated dependencies [cf9bda4] - Updated dependencies [784cb92] - Updated dependencies [7629f4d] - Updated dependencies [51df9fd] - Updated dependencies [a7da4de] - Updated dependencies [de0bcdd] - Updated dependencies [70f7d6d] - Updated dependencies [c677cda] - Updated dependencies [554a160] - Updated dependencies [f7da71e] - Updated dependencies [7f745c3] - Updated dependencies [61821e5] - Updated dependencies [5eb24f8] - Updated dependencies [2a3decc] - Updated dependencies [cc00df2] - Updated dependencies [cc00df2] - Updated dependencies [f4e6adf] - Updated dependencies [ee4a59b] - Updated dependencies [4db3c61] - Updated dependencies [5ca314a] - Updated dependencies [e0af1a8] - Updated dependencies [4771bd9] - Updated dependencies [414c1fc] - Updated dependencies [22c0279] - Updated dependencies [0db2947] - Updated dependencies [92b5d7f] - Updated dependencies [613bfbd] - Updated dependencies [abae16a] - Updated dependencies [094b8fd] - Updated dependencies [c7aca0d] - Updated dependencies [33e939f] - Updated dependencies [c1d8f98] - Updated dependencies [8e0b297] - Updated dependencies [d4f9b2a] - Updated dependencies [5f7fa1d] - Updated dependencies [87f0ccc] - Updated dependencies [aedbaef] - Updated dependencies [a727043] - Updated dependencies [c5d6803] - Updated dependencies [10d05bb] - Updated dependencies [69602e5] - Updated dependencies [c3ce76c] - Updated dependencies [7936b29] - Updated dependencies [46803fa] - Updated dependencies [c2a336c] - Updated dependencies [9f890d3] - Updated dependencies [0bb2318] - Updated dependencies [b72226f] - Updated dependencies [f7db8f4] - Updated dependencies [1ecee3e] - Updated dependencies [9408b7f] - Updated dependencies [e9fcd6b] - Updated dependencies [9bcd9be] - Updated dependencies [b398ad2] - Updated dependencies [99261a7] - Updated dependencies [81b426f] - Updated dependencies [001af1c] - Updated dependencies [fb77aa5] - Updated dependencies [581d8f8] - Updated dependencies [f81afe3] - Updated dependencies [40a44b9] - Updated dependencies [f89812e] - Updated dependencies [7a7fb03] - Updated dependencies [8fd246d] - Updated dependencies [78bc4ad] - @objectstack/spec@17.4.0 - @objectstack/driver-sql@17.4.0 - @objectstack/core@17.4.0 ## 17.3.0 ### Minor Changes - 9f4a6d5: feat(driver-sql,driver-turso,driver-sqlite-wasm): SQLite-family JSON columns declare `TEXT`; server dialects keep native JSON (#12738) A `Field.json` column — and any field with `multiple: true` — is now declared as the JSON column type the **target dialect actually has**. Postgres and MySQL are untouched: their native `json`/`jsonb` and `JSON` types are correct and stay. The SQLite family (plain `SqlDriver` on `sqlite3`/`better-sqlite3`, `TursoDriver` in all three transport modes, and `SqliteWasmDriver`) now declares `text`. **Why.** SQLite has no JSON type. It derives a column's *affinity* from substrings of the declared type name, and `json` contains none of the markers (`INT`, `CHAR`/`CLOB`/`TEXT`, `BLOB`, `REAL`/`FLOA`/`DOUB`), so it fell through to **NUMERIC** and converted number-like input on the way in — measured through raw SQL, a bare `'0123'` was stored as the integer `123`. `text` takes TEXT affinity, converts nothing, and is what SQLite's own JSON1 functions operate on. It is also what `RemoteTransport.mapFieldTypeToSQL` had spelled all along, so turso's two transports now agree instead of diverging on one column. ## The migration shape - **New columns only.** The change is to the DDL emitter. Schema sync is additive, so no existing column is altered, dropped or rewritten. - **Existing columns keep their declared type.** A column created before this release stays `json` and keeps NUMERIC affinity — including through an unrelated SQLite drift rebuild, which re-declares an introspected `json` column as `json` rather than converting it. - **Platform write-path behaviour is unchanged.** The `Field.json` codec stays injective and stays in force: what the platform writes and reads back is identical before and after, on legacy and new columns alike. Nothing on the read path consults the physical column type — `isJsonField` answers from metadata — so decoding is the same on both spellings. - **No new schema-drift findings.** The multi-value base-type finding is gated on the dialect where the column type is load-bearing (Postgres and MySQL); SQLite was already excluded, and the emitter now agrees with the differ instead of merely being excused by it. - **The visible difference is raw-SQL-only, and in the safe direction.** A value written to a JSON column by raw SQL (bypassing the driver) is preserved as text on a new column where it would previously have been coerced to a number. Nothing that was preserved before is coerced now. ### Patch Changes - Updated dependencies [809d417] - Updated dependencies [387e231] - Updated dependencies [f794e4e] - Updated dependencies [cae2169] - Updated dependencies [b812a54] - Updated dependencies [2d4fa75] - Updated dependencies [0e4e51b] - Updated dependencies [e84bbf6] - Updated dependencies [effae80] - Updated dependencies [efb3513] - Updated dependencies [d62f990] - Updated dependencies [c45d8e6] - Updated dependencies [2e3e8c7] - Updated dependencies [e621291] - Updated dependencies [655b106] - Updated dependencies [40a93b5] - Updated dependencies [ef52884] - Updated dependencies [d5b330d] - Updated dependencies [9e1b2de] - Updated dependencies [dda969c] - Updated dependencies [1f45690] - Updated dependencies [277948f] - Updated dependencies [8bdd955] - Updated dependencies [f3bbbef] - Updated dependencies [4f24e9d] - Updated dependencies [e27583e] - Updated dependencies [4bd6faa] - Updated dependencies [86cbe37] - Updated dependencies [6a180e4] - Updated dependencies [474242f] - Updated dependencies [63cd487] - Updated dependencies [bd4aa4e] - Updated dependencies [803eaab] - Updated dependencies [f8e8f03] - Updated dependencies [983edf1] - Updated dependencies [eae824e] - Updated dependencies [178f90c] - Updated dependencies [f6fa22c] - Updated dependencies [8a483b3] - Updated dependencies [84de7e3] - Updated dependencies [3bc2e38] - Updated dependencies [97bcd99] - Updated dependencies [df59de0] - Updated dependencies [96e25a8] - Updated dependencies [f75a38a] - Updated dependencies [7a25e7d] - Updated dependencies [1fa05a6] - Updated dependencies [c85a265] - Updated dependencies [dcb10a5] - Updated dependencies [773a999] - Updated dependencies [35dffea] - Updated dependencies [d8024f0] - Updated dependencies [8120808] - Updated dependencies [0010797] - Updated dependencies [776a098] - Updated dependencies [5060877] - Updated dependencies [4f6325d] - Updated dependencies [52954c0] - Updated dependencies [2aa8456] - Updated dependencies [93809a3] - Updated dependencies [7c0d0c3] - Updated dependencies [daae7aa] - Updated dependencies [8dc22d6] - Updated dependencies [279431e] - Updated dependencies [948dd6b] - Updated dependencies [3b4c56c] - Updated dependencies [ae8edd2] - Updated dependencies [e25403c] - Updated dependencies [f9ffd01] - Updated dependencies [64baa68] - Updated dependencies [9fa70d7] - Updated dependencies [09db64a] - Updated dependencies [92916e7] - Updated dependencies [a84f3ea] - Updated dependencies [f2eaae8] - Updated dependencies [09f9361] - Updated dependencies [c804f0c] - Updated dependencies [34d3011] - Updated dependencies [c09451b] - Updated dependencies [ba64877] - Updated dependencies [9d3c04d] - Updated dependencies [d29e42f] - Updated dependencies [87ad30c] - Updated dependencies [fcd0efc] - Updated dependencies [d0e3a88] - Updated dependencies [3f42920] - Updated dependencies [dd4113e] - Updated dependencies [992161b] - Updated dependencies [ebcc34e] - Updated dependencies [64505a5] - Updated dependencies [7345308] - Updated dependencies [79b6a22] - Updated dependencies [30d96ab] - Updated dependencies [f658793] - Updated dependencies [c95ad19] - Updated dependencies [e58ea8b] - Updated dependencies [4a17645] - Updated dependencies [3795c5f] - Updated dependencies [8ab926b] - Updated dependencies [7317cf2] - Updated dependencies [e25e839] - Updated dependencies [5997207] - Updated dependencies [8b13cc8] - Updated dependencies [4a4a35d] - Updated dependencies [4a4a35d] - Updated dependencies [86e765a] - Updated dependencies [1d7e76a] - Updated dependencies [53dc739] - Updated dependencies [fd289be] - Updated dependencies [03bf7b1] - Updated dependencies [f90e820] - Updated dependencies [18d816a] - Updated dependencies [e8bd715] - Updated dependencies [b91c351] - Updated dependencies [a28a3c0] - Updated dependencies [daeaaf9] - Updated dependencies [c459da6] - Updated dependencies [e914733] - Updated dependencies [f887e52] - Updated dependencies [881f8d8] - Updated dependencies [3bfa1e6] - Updated dependencies [0a8ebf3] - Updated dependencies [901355c] - Updated dependencies [107bb4b] - Updated dependencies [34ce8e7] - Updated dependencies [33681ea] - Updated dependencies [4635f3e] - Updated dependencies [fd289be] - Updated dependencies [ee3595c] - Updated dependencies [b2eab95] - Updated dependencies [93940d4] - Updated dependencies [3a04b01] - Updated dependencies [45b9051] - Updated dependencies [b9e9227] - Updated dependencies [d395692] - Updated dependencies [5894d30] - Updated dependencies [a3765f6] - Updated dependencies [2d5cee3] - Updated dependencies [e22158f] - Updated dependencies [7404925] - Updated dependencies [0c2334f] - Updated dependencies [778c59f] - Updated dependencies [d2619fd] - Updated dependencies [af56546] - Updated dependencies [6acb11a] - Updated dependencies [33c5fd3] - Updated dependencies [20b0fdb] - Updated dependencies [905019b] - Updated dependencies [a286411] - Updated dependencies [98c0d33] - Updated dependencies [368a82e] - Updated dependencies [a3d5724] - Updated dependencies [93ea19b] - Updated dependencies [9ee2dcf] - Updated dependencies [8cb96ec] - Updated dependencies [8f10a79] - Updated dependencies [6269a55] - Updated dependencies [a17da05] - Updated dependencies [a8c00e2] - Updated dependencies [0fb8760] - Updated dependencies [e5ce2ed] - Updated dependencies [be21955] - Updated dependencies [bc56e18] - Updated dependencies [be21955] - Updated dependencies [a9ee989] - Updated dependencies [4d0d944] - Updated dependencies [15d58db] - Updated dependencies [d63b014] - Updated dependencies [9abe4e4] - Updated dependencies [2cc7122] - Updated dependencies [50d6c92] - Updated dependencies [9e0ba21] - Updated dependencies [311433f] - Updated dependencies [0e5bea6] - Updated dependencies [3e5ad08] - Updated dependencies [9abe4e4] - Updated dependencies [b7131f3] - Updated dependencies [e5812fa] - Updated dependencies [7085f90] - Updated dependencies [dee4dd4] - Updated dependencies [e40a28c] - Updated dependencies [7e83932] - Updated dependencies [ce7e497] - Updated dependencies [51ecb2f] - Updated dependencies [9086761] - Updated dependencies [42a117b] - Updated dependencies [1401ae7] - Updated dependencies [4297fe7] - Updated dependencies [e398863] - Updated dependencies [d16df74] - Updated dependencies [f11fc61] - Updated dependencies [e808890] - Updated dependencies [8f79379] - Updated dependencies [e6ca40e] - Updated dependencies [0c77ea4] - Updated dependencies [52954c0] - Updated dependencies [89eb997] - Updated dependencies [7131f12] - Updated dependencies [aa5994e] - Updated dependencies [be93457] - Updated dependencies [a65db76] - Updated dependencies [15eb2c9] - Updated dependencies [5691b07] - Updated dependencies [431d2fb] - Updated dependencies [2a6122b] - Updated dependencies [225e769] - Updated dependencies [8af88dd] - Updated dependencies [fb5fbb8] - Updated dependencies [c05b40b] - Updated dependencies [80f1dcd] - Updated dependencies [6c6157a] - Updated dependencies [d7b3963] - Updated dependencies [33184fd] - Updated dependencies [7c41693] - Updated dependencies [b72db01] - Updated dependencies [dce5cd4] - Updated dependencies [9688f58] - Updated dependencies [556ebc1] - Updated dependencies [177ebdc] - Updated dependencies [8d237b4] - Updated dependencies [2d2e6f0] - Updated dependencies [2d8dd8d] - Updated dependencies [22d573e] - Updated dependencies [b5a2398] - Updated dependencies [348860c] - Updated dependencies [5383fa6] - Updated dependencies [5b3ff63] - Updated dependencies [1a6a19c] - Updated dependencies [527e050] - Updated dependencies [dd33bf9] - Updated dependencies [4cb2a90] - Updated dependencies [6757eb2] - Updated dependencies [74a7804] - Updated dependencies [53d3689] - Updated dependencies [b3a63d3] - Updated dependencies [1c66fe4] - Updated dependencies [49f0dcf] - Updated dependencies [033a34c] - Updated dependencies [4d25d22] - Updated dependencies [1ffee51] - Updated dependencies [b826390] - Updated dependencies [5ae4303] - Updated dependencies [ece4dad] - Updated dependencies [e9b377e] - Updated dependencies [146f448] - Updated dependencies [735f5c7] - Updated dependencies [a7e18de] - Updated dependencies [366f895] - Updated dependencies [dc75ba8] - Updated dependencies [cce0aa9] - Updated dependencies [e764507] - Updated dependencies [cff17af] - Updated dependencies [39404f3] - Updated dependencies [ca1965f] - Updated dependencies [8619f95] - Updated dependencies [b706af9] - Updated dependencies [add4360] - Updated dependencies [cd13488] - Updated dependencies [df1c75c] - Updated dependencies [fc9ba76] - Updated dependencies [0f94cc7] - Updated dependencies [a11c1a5] - Updated dependencies [71f9cd1] - Updated dependencies [ee17d86] - Updated dependencies [cdbd920] - Updated dependencies [18c432e] - Updated dependencies [3c418c4] - Updated dependencies [fa8715a] - Updated dependencies [a933ed7] - Updated dependencies [b3ca463] - Updated dependencies [a933ed7] - Updated dependencies [0d4a6a8] - Updated dependencies [518d5e5] - Updated dependencies [6643ba1] - Updated dependencies [eeba2ef] - Updated dependencies [ec4c4d2] - Updated dependencies [424f73c] - Updated dependencies [cccbe51] - Updated dependencies [a8d6b1d] - Updated dependencies [e4a7695] - Updated dependencies [87075b1] - Updated dependencies [fc58a99] - Updated dependencies [14cfc00] - Updated dependencies [1c6f7b4] - Updated dependencies [e854a53] - Updated dependencies [07cced5] - Updated dependencies [3956069] - Updated dependencies [dfebfc8] - Updated dependencies [5dd3bc9] - Updated dependencies [9f4a6d5] - Updated dependencies [4045b95] - Updated dependencies [7adcd07] - Updated dependencies [f5a7f9c] - Updated dependencies [d028b37] - Updated dependencies [c49afd0] - Updated dependencies [f7b25c5] - Updated dependencies [122ef38] - Updated dependencies [4a37870] - Updated dependencies [428f9b2] - Updated dependencies [aa7ff56] - Updated dependencies [c41b42e] - Updated dependencies [c4db311] - Updated dependencies [750fff5] - Updated dependencies [c19035e] - Updated dependencies [ececf7a] - Updated dependencies [d173125] - Updated dependencies [8eeca27] - Updated dependencies [8425c17] - Updated dependencies [a5ef1d8] - Updated dependencies [772d5de] - Updated dependencies [ce80ec2] - Updated dependencies [f24c90d] - Updated dependencies [b372318] - Updated dependencies [97a2263] - Updated dependencies [29d0676] - Updated dependencies [0169d49] - Updated dependencies [6bd3231] - Updated dependencies [1246b4c] - Updated dependencies [d2b5ba8] - Updated dependencies [b799ac5] - Updated dependencies [8f74307] - Updated dependencies [d23dc08] - Updated dependencies [644ad50] - Updated dependencies [0da7cd2] - Updated dependencies [28a5c3e] - Updated dependencies [4bc18e5] - @objectstack/spec@17.3.0 - @objectstack/core@17.3.0 - @objectstack/driver-sql@17.3.0 ## 17.2.0 ### Patch Changes - 6ceaa4b: docs: name packages that exist in seven published documents, and gate the class (#10893) A published README ships inside the npm tarball, so an install instruction in one reaches every reader of the package. Nine `@objectstack/` names across seven published documents named a package that is in **no directory of this repo**, and five of those sat on `import` lines inside runnable fences. `check:published-readme-exports` could not see any of it, by construction. It resolves a documented import against the package's built type surface through the workspace member map, so a specifier that is not a member has no type entry to compare against and the gate reads no further — strict about a member that exists, silent about one that does not. The gate now makes the member-existence claim first: an `@objectstack/`-scoped specifier that names no workspace member is a finding, and the run header prints the scoped population as `N/N` so a recogniser that stops matching shows up as a denominator that fell. What each dead claim now says, and why: - **`@objectstack/trigger-schedule`** and **`@objectstack/trigger-record-change`** each misnamed **themselves**. Both READMEs — including their `# ` titles and every fenced import — said `@objectstack/plugin-trigger-…`, a name that has never been published. The exported class names (`ScheduleTriggerPlugin`, `TimeRelativeTriggerPlugin`, `RecordChangeTriggerPlugin`) were correct all along; only the package name was wrong, so this is a rename pinned by each package's own `name` field. - **`@objectstack/plugin-security`** told readers to `install @objectstack/plugin-org-scoping` and register an `OrgScopingPlugin` from it. No such package exists. The organization wall ships as the enterprise `@objectstack/organizations` runtime, whose `OrganizationsPlugin` registers the `org-scoping` service this plugin probes — the name `objectstack serve` and `objectstack doctor` both print. Asking for the wall without it is a refusal to boot (ADR-0093 D5), not a silent downgrade, and the page now says so. The tenant-isolation bullet pointed at `@objectstack/service-tenant`, which is the cloud control-plane runtime from the separate `cloud` repository and not where the wall comes from either. - **`@objectstack/service-package`** described packages being "delivered to runtime kernels that load them through `@objectstack/service-marketplace`". That package was never built: ADR-0003, ADR-0016 and ADR-0025 all name it as future work. The loading half that does exist here is `@objectstack/cloud-connection`'s `MarketplaceInstallLocalPlugin`. - **`@objectstack/embedder-openai`** had a fenced example importing `KnowledgeTursoPlugin` from `@objectstack/knowledge-turso` — the worst shape, because a reader pastes it. No knowledge adapter in this repository consumes an `IEmbedder` at all: `knowledge-memory` and `knowledge-ragflow` take no embedder option, and the adapters the contract is written for are not here. The example is now the `embed()` surface that does exist, with the gap stated rather than papered over with a substitute package name. - **`@objectstack/driver-sqlite-wasm`**'s "When to use" table compared it against `@objectstack/driver-sqlite` and `@objectstack/driver-postgres`. Neither has ever existed; `@objectstack/driver-sql` covers PostgreSQL, MySQL and SQLite through Knex, choosing the client from its optional peers. - **`@objectstack/spec`**'s published `prompts/architecture.md` instructed code generators to write `import { User } from '@objectstack/protocol'`. The package is `@objectstack/spec`, which the same sentence names as the path being replaced. Four `@objectstack/` names that are **not** in this repo are deliberately left as they are, because prose may name a package this repo does not build and a runnable import may not: `@objectstack/security-enterprise` (the enterprise edition, whose install hint the CLI prints and a CLI test pins), `@objectstack/service-tenant` (the cloud runtime), `@objectstack/framework` (the umbrella install name), and the two names `service-datasource`'s README recalls as its own past. - Updated dependencies [6936d07] - Updated dependencies [59eb04d] - Updated dependencies [9f05b7d] - Updated dependencies [3b2af5e] - Updated dependencies [7d2d112] - Updated dependencies [5fa0d72] - Updated dependencies [02b3b07] - Updated dependencies [95437e7] - Updated dependencies [824a996] - Updated dependencies [9cc1940] - Updated dependencies [9cc1940] - Updated dependencies [9cc1940] - Updated dependencies [46cfa5b] - Updated dependencies [479fba5] - Updated dependencies [914c413] - Updated dependencies [55809a0] - Updated dependencies [927ccbb] - Updated dependencies [ee2ff45] - Updated dependencies [47cd3ec] - Updated dependencies [52db1d1] - Updated dependencies [5649efb] - Updated dependencies [9d7d2de] - Updated dependencies [c815c50] - Updated dependencies [795ea05] - Updated dependencies [2306a76] - Updated dependencies [e5ea701] - Updated dependencies [a40dcc1] - Updated dependencies [def0d3e] - Updated dependencies [8d0bb79] - Updated dependencies [5acb58d] - Updated dependencies [2e3cf95] - Updated dependencies [4c93387] - Updated dependencies [504c8d5] - Updated dependencies [a037f7c] - Updated dependencies [3ee8ddf] - Updated dependencies [16cef97] - Updated dependencies [a79bd35] - Updated dependencies [6ceaa4b] - Updated dependencies [15ea214] - Updated dependencies [de19489] - Updated dependencies [c684d00] - Updated dependencies [923c424] - Updated dependencies [1ec36b7] - Updated dependencies [5f2e54c] - Updated dependencies [189373b] - Updated dependencies [f59035c] - Updated dependencies [35ad101] - Updated dependencies [ceb33a9] - Updated dependencies [73d9795] - Updated dependencies [8012960] - Updated dependencies [f34f56b] - Updated dependencies [f399618] - Updated dependencies [75e9301] - Updated dependencies [2810695] - @objectstack/spec@17.2.0 - @objectstack/driver-sql@17.2.0 - @objectstack/core@17.2.0 ## 17.1.0 ### Patch Changes - 7337f30: chore(deps): production-dependency patch bumps from the weekly Dependabot group (#9212) Routine dependency-range refresh, no behavior change: `@oclif/core` 4.13.2→4.13.3, `esbuild` 0.28.1→0.28.2 and `better-sqlite3` ^13.0.2→^13.0.3 (optional) on `@objectstack/cli`; `mingo` 7.2.2→7.2.4 on `@objectstack/driver-memory`; `nanoid` 6.0.0→6.0.1 on `@objectstack/driver-mongodb`, `@objectstack/driver-sql`, `@objectstack/driver-sqlite-wasm` and `@objectstack/driver-turso`, plus `better-sqlite3` ^13.0.2→^13.0.3 (optional on `@objectstack/driver-sql`, peer on `@objectstack/driver-turso`); `js-yaml` 5.2.2→5.2.3 on `@objectstack/metadata`; `@noble/hashes` 2.2.0→2.3.0 and `jose` 6.2.5→6.2.8 on `@objectstack/plugin-auth`; `nodemailer` 9.0.3→9.0.5 on `@objectstack/plugin-email`; `@hono/node-server` 2.0.12→2.1.1 and `hono` 4.12.34→4.13.2 on `@objectstack/plugin-hono-server`; `pinyin-pro` 3.28.2→3.29.1 on `@objectstack/plugin-pinyin-search`; and `@noble/ciphers` 2.2.0→2.3.0 on `@objectstack/service-settings`. Every entry above changed a `dependencies`, `optionalDependencies` or `peerDependencies` range in the published manifest — the only kind of change that reaches a consumer's install. The same Dependabot group also bumped `devDependencies` on `@objectstack/hono`, `@objectstack/client`, `@objectstack/core`, `@objectstack/plugin-sharing` and `@objectstack/spec` (none consumer-facing), and touched the private `apps/docs`, `examples/app-todo` and workspace-root manifests (none published) — none of those get an entry here. - Updated dependencies [56656aa] - Updated dependencies [07e630e] - Updated dependencies [2f65b1b] - Updated dependencies [720ee95] - Updated dependencies [f287435] - Updated dependencies [2782805] - Updated dependencies [e43d63a] - Updated dependencies [9aa8890] - Updated dependencies [7c9c1dd] - Updated dependencies [8bbf459] - Updated dependencies [75b7c24] - Updated dependencies [d5552ca] - Updated dependencies [d9813a9] - Updated dependencies [8640fb2] - Updated dependencies [2420641] - Updated dependencies [2ad91c3] - Updated dependencies [f57fb38] - Updated dependencies [00777a0] - Updated dependencies [d491625] - Updated dependencies [2c570f3] - Updated dependencies [7337f30] - Updated dependencies [420804d] - Updated dependencies [cbf4b40] - Updated dependencies [9c4d096] - Updated dependencies [86431f7] - Updated dependencies [716ac9b] - Updated dependencies [a38408a] - Updated dependencies [62b1427] - Updated dependencies [7ea1372] - Updated dependencies [23abe27] - Updated dependencies [985a9cd] - Updated dependencies [5f5e234] - Updated dependencies [a8189ae] - Updated dependencies [26e70fb] - Updated dependencies [42b05af] - Updated dependencies [2b292ce] - Updated dependencies [abcf853] - Updated dependencies [8b9eba5] - Updated dependencies [d575779] - Updated dependencies [94f7ef8] - Updated dependencies [c5ac5e4] - Updated dependencies [a777944] - Updated dependencies [dd88e1c] - Updated dependencies [856527c] - Updated dependencies [870f710] - Updated dependencies [79c46da] - Updated dependencies [7ff3975] - Updated dependencies [29d055b] - Updated dependencies [65589d6] - Updated dependencies [2c86fe3] - Updated dependencies [e196c6a] - Updated dependencies [24173e9] - Updated dependencies [4ab7523] - Updated dependencies [19539b4] - Updated dependencies [a9df51c] - Updated dependencies [f8eb736] - Updated dependencies [11b779e] - Updated dependencies [ab8b10f] - Updated dependencies [739fe5b] - Updated dependencies [4bfe1a5] - Updated dependencies [2065e31] - Updated dependencies [b69d0f5] - Updated dependencies [4d47afe] - Updated dependencies [e4e5c6e] - Updated dependencies [9a56784] - Updated dependencies [c8806ae] - Updated dependencies [bb96297] - Updated dependencies [d00d2f6] - Updated dependencies [df0c12d] - Updated dependencies [d31785f] - Updated dependencies [c308a4f] - Updated dependencies [3b3f67d] - Updated dependencies [e2899f6] - Updated dependencies [3851f87] - Updated dependencies [2a29caa] - Updated dependencies [09a6eee] - Updated dependencies [1a7f907] - Updated dependencies [cd455c8] - Updated dependencies [e1bb0ca] - Updated dependencies [30d3752] - Updated dependencies [c80e7ae] - Updated dependencies [09a9a8a] - Updated dependencies [07026cf] - Updated dependencies [5d4f3d5] - Updated dependencies [4d80e8b] - Updated dependencies [30b1c63] - Updated dependencies [079b457] - Updated dependencies [e43b211] - Updated dependencies [890b38f] - Updated dependencies [8bee54b] - Updated dependencies [7a537ce] - Updated dependencies [593c4bf] - Updated dependencies [ff08691] - Updated dependencies [60e0f90] - Updated dependencies [90c5285] - Updated dependencies [402c125] - Updated dependencies [7901b2d] - Updated dependencies [56bca91] - Updated dependencies [79394d7] - Updated dependencies [730fd9a] - Updated dependencies [44bc51d] - Updated dependencies [73cfddf] - Updated dependencies [a4acb8d] - Updated dependencies [d634e66] - Updated dependencies [682b86b] - Updated dependencies [6a1b45e] - @objectstack/spec@17.1.0 - @objectstack/core@17.1.0 - @objectstack/driver-sql@17.1.0 ## 17.0.0 ### Major Changes - d367f03: refactor(drivers)!: 五个驱动的 query 参数跟进 `DriverQuery`，休眠的类型谎言就此没有藏身处 (#6075) #5181（PR #6076）把 `IDataDriver.find/findOne/count/updateMany/deleteMany/explain` 的 query 参数收窄为 `DriverQuery`（`Omit`），并在同一条 changeset 里写明：「把驱动签名一并迁到 `DriverQuery` 是后续的机械收尾」。这就是那次收尾。 在此之前，五个驱动的实现仍旧声明 `query: QueryAST`（turso 侧是 `query: any`）。**它不红，也不会红** —— 方法参数按双变比较，实现声明得比契约宽照样满足契约。但调用方现在**有权**省略 `object`，于是这些实现的类型说 `query.object` 是 `string`，运行期却可能是 `undefined`：一句休眠的谎言，没有任何门拦得住下一个照着它写代码的人。 收尾之后，「驱动读 `query.object`」直接变成编译错误： ```ts // 收窄前：编译通过，运行期可能是 undefined —— 谎言 // 收窄后：error TS2339: Property 'object' does not exist on type 'DriverQuery'. const name = query.object; ``` **零运行时改动。** 本次改的全部是类型注解：五个驱动的六个契约方法签名，以及为让类型自洽而必须跟进的少量私有辅助方法参数（mongodb 的 `buildFindOptions` / `buildSortSpec`，sql 的 `findRows` / `orderKeysFor`，turso 的 `toRemoteQuery` / `toRemoteReadQuery`，memory 的 `performAggregation`）—— 它们都只转发或读取 `where` / `orderBy` / `groupBy` 这些字段，本来就不读 `object`。turso 的几处 `query: any` 一并收紧，多拿回一批本已放弃的检查。emit 无差异，测试全绿（memory 524、mongodb 206、sql 906、sqlite-wasm 254、turso 788）。 **迁移面：删掉驱动调用字面量里的 `object:` 键**，与 #5181 是同一句话，只是现在也覆盖了直接按具体驱动类（`SqlDriver` / `MemoryDriver` / …）而非按 `IDataDriver` 取类型的调用方。编译器会逐处指出来（TS2353 `'object' does not exist in type 'DriverQuery'`）。本仓下游 25 个包实测零处需要改动，改动只落在五个驱动自己的测试里。 标 major 的依据与 #5181 一致：**源码级破坏性**（调用点内联字面量），运行时行为零变化。`check:api-surface` 只记录导出的存在与否、不记录签名，因此这条说明同样是该变更唯一的下游载体。 `aggregate` / `distinct` / `syncSchemasBatch` 不在本次范围内 —— 它们不是 `IDataDriver` 收窄的那六个方法，其中 `syncSchemasBatch` 的条目里 `object` 是被真实读取的必填键，`expand` 条目里的 `object` 同理命名的是关联对象，都不是冗余。 - 62159bd: refactor(driver-sql)!: `SqlDriver.distinct` 的第三参收成裸 `FilterCondition`，一个静默返回全集的写法就此编译不过 (#6320) `distinct` 不在 `IDataDriver` 上，所以 #5181（PR #6076）与 #6075（PR #6210）的收窄都没走到它，#6212 批 A+E（#6355）收的是 `analyzeQuery` / `findWithWindowFunctions`，也没覆盖它。它的方法体一直说得很清楚——`applyFilters(builder, filters)` 拿的是**实参本身**，因此它要的是 `find()` 放在 `query.where` 里的那个值，**不是 query 信封**；`filters?: any` 只是没把这句话写进类型里。 ```ts // 收窄前后都成立，一处调用点都不用改 await driver.distinct("orders", "product", { status: "completed" }); ``` **收窄真正买到的东西，是实测出来的，不是推断的。** 三行数据（`Laptop`/`Mouse` 为 `completed`，`Ghost` 为 `pending`），逐个形状喂给 `distinct('orders','product', …)`： | 第三参 | 收窄前 | 收窄后 | | :--------------------------- | :--------------------------------- | :----------- | | `{ status: 'completed' }` | 返回 `["Laptop","Mouse"]` | 不变 | | 省略 | 返回全集 | 不变 | | `'completed'`（标量） | **编译通过，返回全集** | **编译错误** | | `{ object, where }`（信封） | 抛 `INVALID_FILTER` / 400 | 不变 | | `['status','=','completed']` | 抛 `INVALID_FILTER` / 400（#5158） | 不变 | 第三行就是本次消掉的那一格：一个真心想问「completed 订单里有哪些商品」的调用，编译通过，然后拿到**每一个**商品。`applyFilters` 对「真值但非对象、非数组」的 filter 不发射任何谓词（该方法尾注写着这件事），于是过滤条件被整条丢掉。方向是**放宽**——这正是 #6320 与 #5234 同族的那类「静默错答案」。 **有一格是任何类型都关不上的，本次如实写进注释而不是假装关上了。** `FilterCondition` 的键**就是字段名**，所以它是开放映射（`[key: string]: any`）：`{ object, where }` 在结构上是一个完全合法的 filter——约束两个分别叫 `object` 和 `where` 的列。没有任何注解能把它和正当 filter 分开。#6320 提出的「让反向错配也编译不过」在这个参数上**不可达**，实测确认；能拿到的保证是**运行期响亮失败**：信封里的 `where` 是对象，而没有任何比较值可以是对象，于是 `assertCompilableComparand` 抛 `INVALID_FILTER` / 400。这半边 driver-sql 从来就不是静默的；`driver-memory` 那半边（裸 filter 交给它会静默返回全集）留在 #5499 冻结面内，本次不碰。 **零运行时改动**：非测试改动 100% 是一个类型注解加一段注释，无逻辑、无行为、无 emit 差异。 **逐处复核了全部 14 个调用点**（本单正文记的是 3 处，实测偏低）：driver-sql 11 处、driver-sqlite-wasm 3 处、driver-turso 0 处；其中真正传第三参的是 4 处（driver-sql 2 + driver-sqlite-wasm 2），全部本来就写的裸 filter，**零报错、零 fixture 改动**。 **driver-sqlite-wasm 也标 major**：`SqliteWasmDriver extends SqlDriver` 且不覆写 `distinct`，所以它**已发布的 `.d.ts`** 里这个方法的签名同样收窄，它的使用者看到的是同一个变化。该包读的是 driver-sql 构建后的 `dist/*.d.ts` 而非源码，是一处已知门禁盲区，本次用「往参数类型里临时塞一个调用方不可能满足的成员、重建、看调用点是否逐一变红」证明它确实读到了新 d.ts：driver-sql 6 处红、driver-sqlite-wasm 3 处红，与预判逐一相符。 ### 迁移 调用点若把**标量**（或任何非 `FilterCondition` 值）交给第三参，编译器会指出来： ``` error TS2345: Argument of type 'string' is not assignable to parameter of type 'FilterCondition'. ``` 改法是把它写成它本来就该是的裸 filter 对象（`'completed'` → `{ status: 'completed' }`）。⚠️ 这类调用点在收窄前拿到的是**未过滤的全集**，所以这不是一次等价改写：修完之后返回值会变，而变化后的那个才是调用方本来想要的答案。本仓零处这样的调用点。 ⚠️ 无类型的 JS 调用方**既不会拿到编译错误、也不会有任何行为变化**（本次零运行时改动）。对他们而言，上面那条是「你一直没在过滤」的**唯一通知渠道** —— 这也是本次记台账条目的理由，见下。 ### Minor Changes - 92a67f2: feat(drivers,spec)!: `GroupByNode.alias` is honoured by the SQL faces — one aggregate, one column key (#6401) `GroupByNodeSchema` has declared `alias` ("Alias for the projected group value", defaulting to `field`) for as long as the structured `groupBy` entry has existed. Exactly one execution path read it. The result: the SAME query came back with a different result-column key depending on which path the engine happened to take. ```ts groupBy: [{ field: "closed_at", dateGranularity: "month", alias: "qtr" }]; ``` - pushed down to a driver ⇒ rows keyed **`closed_at`** - run through the in-memory fallback ⇒ rows keyed **`qtr`** And the choice between them is `engine.ts`'s `allStructuredSupported && !tzRequiresInMemory` — a driver capability bit and a `timezone`, neither of which the caller can see. That is the multi-face consistency invariant broken in its quietest form: both answers are valid rows, so nothing throws and nothing looks wrong. **Resolved to ENFORCE**, and the leg was chosen by measurement rather than taste. ADR-0049 splits on whether the feature already exists: a _dangling_ promise is removed, a _live_ one with a missing gate is enforced. `alias` is live — three consumers read it and change behaviour (`in-memory-aggregation.ts`, `MemoryDriver.performAggregation`, and `chartAggregateCategoryKey`), and the publish gate _compels_ it: `validate-react-page-props.ts` errors `REACT_CHART_AXIS_UNKNOWN` unless a chart's category axis is bound to `alias ?? field`, telling the author in so many words to "bind it to" the alias. A key the build gate makes you write is not a dangling promise. The count of real non-test producers is **zero**, which is what makes enforcing safe rather than what argues against it: no shipped payload changes its result keys. **What changed, on every SQL face at once** — a fix landing on one and not its twin is the #6203 shape, and `TursoDriver` picks its face from `url`: - **`driver-sql`** — both limbs of the structured `groupBy` branch project `alias ?? field`: the date-bucket limb aliases the bucket expression to it, and the plain limb emits `?? as ??` (only when the name actually moves — an alias equal to the field emits no self-rename). `presentedOutput` is now keyed by the OUTPUT column, matching how the aggregation branch beside it has always worked; an aliased group value went unpresented before. - **`driver-turso` REMOTE** — the same projection, `"field" AS "alias"`. The alias reaches the statement as a quoted identifier and is therefore held to `assertSafeIdentifier`, exactly like `field`. - **`driver-sqlite-wasm`** — inherits `SqlDriver`'s compiler; covered by its own conformance suite rather than by assumption. **GROUP BY still keys on the FIELD** on every face. Only the projection is renamed, so the buckets are unchanged. This is deliberate and pinned: SQLite resolves output names in `GROUP BY`, so a face that grouped by the alias would look correct here and diverge on a dialect that does not. `having` needed no change and now means one thing: it is applied over the aggregated row's own columns, so a filter on a group projection references the alias on every path — previously the alias on one path and the field on the other. **Conformance.** `AGGREGATION_CASES` (#6409) gains a `groupByAlias` axis and two cases. Their VALUES are an existing case verbatim — only the key moves — so they can fail only on the key, which is the point: every wrong answer in this area is a valid query returning plausible rows. `objectql`'s in-memory fallback is now **enrolled** as a fourth face, answering #6409's open question ②: it is the face the SQL three were converged onto, so the new behaviour would otherwise be pinned against nothing, and reaching it needs no engine at all — `applyInMemoryAggregation` is a pure function of rows and an AST. **Reverse verification**, predicted before running. Reverting the in-memory face to `g.field`: only the two alias cases move and only ONE fails — the degenerate `alias === field` case stays green, which is why both are in the table. Reverting the harness to read `c.groupBy` instead of `c.groupByAlias ?? c.groupBy` — the copied-neighbour mistake: everything passes on an unmodified face, a false GREEN, which is the failure mode that would have made the axis vacuous. **Frozen drivers (#5499), measured from source, not flipped.** `driver-memory` already returned `{ field, alias: node.alias ?? node.field }` and projects under the alias — it had independently reached the enforce answer, so it needed no alignment. `driver-mongodb` is a recorded DEBT row and the defect is wider than `alias`: `buildAggregationPipeline` types `groupBy` as `string[]` and builds `groupId[field] = '$' + field`, so a structured node — aliased or not — becomes the literal key `"[object Object]"`. It cannot take a structured `GroupByNode` at all; `mongodb-driver.ts` passes `(query as any).groupBy`, which is why `tsc` never saw it. Tracked on #6814. **Compatibility.** A caller who writes `alias` and reads the result under `field` on a pushdown path will now find the value under `alias` — which is what the key has always meant on the fallback path, and what the chart gate already required. Callers who never write `alias` are unaffected: the emitted SQL is byte-identical. - 82397b6: feat(drivers,objectql): `$regex` / `$options` are refused everywhere, and `$icontains` is implemented on the SQL family (#5702) The driver half of the #4706 ruling. #5701 landed the contract (the vocabulary, the `RETIRED_FILTER_OPERATORS` prescriptions, the shared text case-set) and #5710 flipped the last live producer — `plugin-auth`'s ObjectQL adapter, which emitted `$regex` on the authentication path — so the refusal can now land without breaking sign-in. **BREAKING for anyone writing `$regex` or `$options` in a filter.** Both are refused on every backend with `INVALID_FILTER` / 400 and a message that names the replacement. `$regex` was never a declared operator: `driver-sql` compiled it to a LIKE-escaped substring (so `a.b` matched only the literal `a.b`), `driver-memory` ran it as a real `RegExp` (so the same filter also matched `axb`, and an _invalid_ pattern was caught and answered `false` — zero rows, in silence), and `objectql`'s `having` did the same. Write `$icontains` for the case-insensitive substring search this was almost always used for, `$contains` for a case-sensitive one; a pattern that genuinely needs a regex has no filter-level replacement. **`$icontains` now runs on the SQL family** — `driver-sql`, `driver-sqlite-wasm`, and both of `driver-turso`'s transports (the remote one does not go through knex, so it needed its own). It compiles to `LOWER(col) LIKE LOWER(?) ESCAPE ?` through the same `applyLike` / `pushLike` that carries the `%` / `_` / `\` escaping, as a `fold` parameter rather than a second emitter — a copied emitter is where the escape class would have been dropped, and an unescaped `%` matches every row. An empty or non-string comparand is refused on the validating walk (an empty one matches every row, which widens rather than narrows). On SQLite `lower()` folds ASCII only, which IS the contract (#4706 Q1 = A): `$icontains: 'café'` does not match `CAFÉ`. `driver-mongodb`'s unknown-operator arm was throwing a bare `Error` with no `code` and no `status`, three lines from the helper in its own file that sets `INVALID_FILTER` / 400 — a 500-shaped body for a 400-class client mistake. It now speaks the same envelope as its three siblings. Two parts of the ruling are deliberately NOT in this change and stay tracked in `scripts/check-driver-conformance.mjs`'s ledger: the `$contains` family's case-sensitivity (#4706 Q2 = A) needs SQLite's `LIKE` replaced by a case-exact construct in the driver, the RLS lowering and the analytics lowering together, or one permission rule compiles to two row sets (#6518); and `$icontains` on the JS evaluation faces needs the spec vocabulary to take the operator, which cannot happen before `driver-memory` has an arm for it (#6520). - f1544e2: feat(driver-sql): compile `$field` to a column-to-column comparison on SQL push-down (#5222) `FieldReferenceSchema` (`{ $field: 'other_column' }`) is declared in the spec and genuinely PRODUCED — `compileCelToFilter` emits it whenever a CEL permission/RLS rule compares one field to another — but its only implementation was the in-memory evaluator. #5041 measured the consequence and installed a loud refusal (`INVALID_FILTER` / 400, replacing a bare `TypeError` and, inside an `$in` list, a silent zero-row answer), deliberately leaving the capability itself to this change. Until now, therefore, one permission rule had two behaviours chosen by whether the query reached a database. The six scalar comparison operators — `$eq` / `$ne` / `$gt` / `$gte` / `$lt` / `$lte`, including the array-triple authorings that lower to them — now compile `{ $field: 'col' }` into a real column reference: ```js { amount: { $gt: { $field: "budget"; } } } // → where "amount" > "budget" ``` **Nothing that worked before changes.** This is additive: every shape that compiled still compiles identically, and the refusal gate was NARROWED, never removed. A minor bump because a previously-400 filter now returns rows. **The refused arm, and why each entry is there** (all keep `INVALID_FILTER` / 400): - **Dotted paths** (`{ $field: 'account.owner_id' }`) — maintainer ruling: v1 is same-table columns only. No JOIN planning, no alias-qualified columns. - **Undeclared columns**, on either side — the `$field` value lands in a SQL identifier position, so only fields the object declares are accepted, refused at COMPILE time rather than by the database. Federated/external tables (ADR-0015), whose column set this driver does not own, are refused wholesale. - **The tenant-isolation column**, on either side — a privilege-escalation comparison surface. Closed on both sides because the operands of `=` commute. - **Cross-class comparisons** (a number against text, a date against text) — SQLite orders by storage class first while the in-memory evaluator applies JS coercion, so the two paths genuinely disagree and neither answer can be made the other. Refused rather than shipped as a silent divergence. - **`$in` / `$nin` / `$between` list members** — the in-memory evaluator does not resolve a reference inside a list either (`resolveValue` returns an array unchanged), so there is no correct semantics for SQL to be equivalent to. - **The string operators** (`$contains`, `$startsWith`, …) — a column-side LIKE pattern cannot be metacharacter-escaped portably, and an unescaped one is the `%`-matches-every-row filter bypass. - **The bare `{ field: { $field: 'other' } }` spelling** — what `parseFilterAST(['a', '=', { $field: 'b' }])` lowers to. Still refused, because the in-memory evaluator answers `false` for it rather than reading it as an equality; the refusal now names `$eq` as the spelling that compiles instead of falling through to a generic operator list. **Equivalence is proven, not asserted.** A cross-path conformance suite runs each supported shape through the in-memory evaluator AND through SQL push-down against the same seeded rows, holding both to the same declared id list. Its fixture carries every NULL arrangement two columns can be in — target NULL, referent NULL, and BOTH NULL — because three-valued SQL against a two-valued JS matcher is the one place these paths can genuinely diverge. Every emitted predicate is therefore written TOTAL: `{ a: { $eq: { $field: 'b' } } }` matches a row where both columns are NULL, which a plain `a = b` would drop, and `$not` over any cross-field leaf is its exact complement. The suite runs the full driver axis — SQLite always, live Postgres and MySQL when the runner provisions them — and on both SQL drivers: `driver-sqlite-wasm` inherits the compiler but executes through its own sql.js dialect, which binds the identifier list itself. The dialect axis is not ceremony here: a cross-field predicate is the one filter shape whose SQL carries two identifiers and no bound value, and the class rule has a different failure per backend — comparing text to a number is a silent wrong answer on SQLite (storage classes order before values) but `operator does not exist: text > integer` on Postgres. The guard is what keeps either from being reached. - 3172831: fix(drivers): text-operator case folding is the CONTRACT's answer, not the dialect's (#6518) The `$contains` family and `$icontains` returned **different rows on different databases** for the same filter, because case sensitivity was decided by whatever `LIKE` happened to mean on the dialect underneath. Both directions **over-matched** — they returned rows the filter excludes, which on an ADR-0021 RLS read scope is over-reach rather than a loose filter (#3948): | | `$contains` / `$notContains` / `$startsWith` / `$endsWith` — case-SENSITIVE (#4706 Q2 = A) | `$icontains` — folds ASCII ONLY (#4706 Q1 = A) | | :--------------------------- | :----------------------------------------------------------------------------------------- | :--------------------------------------------- | | SQLite / turso / sqlite-wasm | ❌ `LIKE` folds ASCII | ✅ `lower()` is ASCII-only | | Postgres | ✅ `LIKE` is case-exact | ❌ `LOWER()` folds all of Unicode | | MySQL | ❌ follows the column's collation | ❌ `LOWER()` folds all of Unicode | Read across: **each dialect was already right on the half another one got wrong**, which is why neither half could be found from one backend alone. ## What now runs The construct is chosen per dialect, in one emitter, so the escaping and the fold stay a single code path (an unescaped wildcard is a filter bypass, P0 — #5567): - **SQLite family → `GLOB`.** `LIKE`'s ASCII fold cannot be switched off per statement (`PRAGMA case_sensitive_like` is connection-global, so one query would redefine every other query on the connection), and `CAST(col AS BLOB) LIKE ?` was measured to match _nothing at all_. `GLOB` is case-exact and brings its own escaped class — `*`, `?`, `[` as the self-closing classes `[*]`, `[?]`, `[[]`, because SQLite's grammar gives `GLOB` no `ESCAPE` clause. `$icontains` keeps `lower()` on both operands, still ASCII-only. - **Postgres → `LIKE`, unchanged.** Only the fold moved, from `LOWER()` to an explicit `translate()` over the 26 ASCII letters. Measured on a live PostgreSQL 16 (ICU database): `LOWER('CAFÉ')` is `'café'` — the over-fold — while the `translate()` form leaves `É` alone. - **MySQL → `LIKE` over `CAST(… AS BINARY)`**, so the comparison is byte-wise and no collation decides the case; `$icontains` folds byte-wise over the same binary rendering, which is ASCII-only because UTF-8 is self-synchronising. - **Any other client** keeps the previous `LIKE` / `LOWER()` shape — it is the only form that still runs there — and is recorded as residue rather than left to be discovered. `driver-turso`'s remote transport carries the twin (it compiles filters itself and inherits nothing), and the two transports are now held to the same rows by a parity suite that runs the shared `FILTER_TEXT_CASES` on both. ## Behaviour change — read this before upgrading A filter whose comparand's case did not match the stored text used to match on SQLite/turso/sqlite-wasm and may have matched on MySQL. It no longer does: ```ts // rows: { id: '1', name: 'ACME Corp' }, { id: '2', name: 'acme corp' } { name: { $contains: "acme"; } } // was ['1','2'] on SQLite → now ['2'] everywhere { name: { $icontains: "acme"; } } // ['1','2'] — unchanged, and now correct on PG/MySQL too { name: { $icontains: "café"; } } // was ['3','4'] on PG/MySQL → now ['4'] everywhere ``` If you were relying on `$contains` to ignore case, **write `$icontains`** — that is the operator for it, and it now folds the same ASCII-only range on every backend. Result sets only ever get NARROWER, never wider, so a filter that was already correct stays correct. ## Why `minor` rather than `major` No declared surface moves. `$contains` still exists, still takes the same comparand, and `filter.zod.ts` is untouched — the case-sensitivity this delivers was **already published** as the contract by #5701 (`FILTER_TEXT_CASES`, one release earlier in this same v17 major), and the drivers were the half that had not caught up. This is Prime Directive #12 applied in the direction it points: declared = enforced. It is graded the way its sibling #5702/#6549 was graded for the same operator family in the same rc cycle, and it registers nothing in the ADR-0087 registries because it retires no authorable key. ## What is deliberately NOT in this change `driver-memory` and `driver-mongodb` still fold case on their query paths — they are the #5499 frozen family, so their `FILTER_TEXT_CASES` cells stay honest DEBT and are tracked as #6682 (case sensitivity) and #6520 (`$icontains`). The `service-analytics` SQL compilers were measured already compliant: they emit Postgres-shaped statements, where `LIKE` is case-exact, and that assumption is now written down and pinned rather than implied. ### Patch Changes - 0af50a3: fix(driver-sql,service-analytics): a bare-day upper bound covers the whole day on `Field.datetime` (#3777) A bare `YYYY-MM-DD` comparand anchors to midnight UTC. That is right for a lower bound and was silently wrong for an upper one: the dashboard date-range filter compiles `{ $gte: from, $lte: to }` with bare-day bounds, so on a `datetime` column every row created after 00:00 of the `to` day vanished from the result — no error, the chart renders, the numbers are just smaller. The default configuration hit it: the filter's default field is `created_at` (a system-injected `Field.datetime`) and 7 of the 13 presets end "today". The translation is operator-sensitive and half-open, applied at every comparison emitter: - `SqlDriver` (and `SqliteWasmDriver` by inheritance): `$lte`/`<=` with a bare-day comparand on a `datetime` column compiles to `< next-day-midnight` in the column's storage form; `$between [min, max]` with a bare-day max decomposes to `>= min AND < next-day(max)`. Both the plain and the legacy-repair (mixed-storage) column paths, both `where` spellings. - `NativeSQLStrategy`: `dateRange` windows and `lte` filters bind `< next-day` instead of an inclusive `BETWEEN`/`<=` when the bound is a bare day. - The `/analytics/sql` rendering and the dataset preview evaluator apply the same rule, so the echoed SQL and drafted numbers reproduce execution. `@objectstack/core` gains the shared primitive `nextUtcCalendarDay(value)`: the next calendar day of a valid bare `YYYY-MM-DD` (else `null` — instants, `Date`s and impossible days are never widened). Unchanged on purpose, per the semantics table on #3777: `date`/`time` columns (`<= day` is already whole-day-correct there), full-ISO/`Date` comparands (instant semantics), and `$gte`/`$gt`/`$lt` (midnight anchoring is correct for those). No authored metadata changes: a dashboard's existing `{ $gte, $lte }` window now simply includes its final day. - 2e836de: chore(packaging): CHANGELOG.md ships in every npm tarball (#4261) The AGENTS.md post-task checklist requires breaking changesets to carry their FROM → TO migration because "this text ships to consumers as `CHANGELOG.md` inside the npm package and is what an upgrading agent greps after the tombstone error." That delivery path was severed for 68 of the 69 publishable packages: npm packs `package.json` / `README*` / `LICENSE*` unconditionally but — unlike older npm versions — not `CHANGELOG.md`, and the canonical `"files": ["dist", "README.md"]` whitelist never named it. Measured on npm 10.9.7: `npm pack --dry-run` on `@objectstack/types` shipped 3 files while its 70KB `CHANGELOG.md` stayed behind. Only `@objectstack/spec` listed it explicitly. The tombstone-error scenario is precisely the one where the repo is out of reach — the upgrading agent has `node_modules` and nothing else — so the migration text has to ride in the tarball. Every publishable package now declares `CHANGELOG.md` in `files`, and the canonical whitelist is `["dist", "README.md", "CHANGELOG.md"]`. The other half is the gate: `check:published-files` gains a fifth invariant, COMPLETE — a whitelist that fails to cover `CHANGELOG.md` fails the always-required lint job, so the next package cannot silently sever the path again. `@objectstack/spec`'s per-package EXTRA_ENTRIES exemption dissolves into the canonical set. Consumer-visible change: one more file per install (the package's changelog, e.g. 70.8KB for `@objectstack/types`), and `grep -r "removed key" node_modules/@objectstack/*/CHANGELOG.md` now finds the migration it was promised. - 9881074: test(drivers): the "held to by a gate" claim now has a gate behind it (#4363) Three changesets — filter combinator semantics (#3774), temporal storage form (ADR-0053), deterministic paged reads (objectui#3106 / #4363) — each introduced a shared case-set in `@objectstack/spec/data` with some version of the claim that a future driver "is held to this by a gate rather than by remembering it". There was no gate. The case-sets are exports sitting in a package; nothing obliged a driver to import them. Measured on `main`, the matrix had three holes: `driver-sqlite-wasm` ran neither pagination case-set, and neither it nor `driver-mongodb` ran the filter-logic one — including a hole in the very case-set whose changeset made the claim. `scripts/check-driver-conformance.mjs` (`pnpm check:driver-conformance`, wired into lint.yml's required job) makes the hole the failure. Every (driver × case-set) cell is covered — some file under the package's `src/` imports _and drives_ the case-set's marker export — or carries a measured DEBT/EXEMPT entry, reconciled in both directions. A third direction, CLASSIFIED, holds the other end: a new `*-conformance.ts` fixture nobody classified fails the run rather than starting life uncovered, which is the direction that actually rots (#4203). It caught an unclassified `TEMPORAL_TIME_CASES` on its first run. `driver-sqlite-wasm` gains the pagination suite the gate found missing. It inherits `SqlDriver`'s ORDER BY construction, so nothing is re-implemented — what the suite pins is that the clause survives a different _engine_: this driver swaps knex's transport for a custom sql.js dialect that compiles, executes and marshals every row through its own path, and a dialect that reordered or dropped the trailing `ORDER BY id` would fail in no other suite. The two filter-logic holes are ledgered as DEBT rather than fixed here, with their reasons printed on every run and tracked in #4405. The mongodb row is the substantive one: `translateFilter` is an independent FilterCondition backend — the fifth, and the one #3774 never enrolled when it counted "the four". - 4384921: fix(spec,drivers): `bypassTenantAudit` becomes a declared driver option, and `findOne` stops accepting a bare id (#4311) Three drivers built with `tsup` and tested with `vitest`, so no `tsc` had ever read them. Onboarding them to the #4311 type-check ratchet surfaced 292 errors, and most of what looked like sloppy test fixtures was the types being wrong. **`DriverOptions.bypassTenantAudit` is now declared.** It has been live for a long time without being on the schema: `SqlDriver.auditMissingTenant` reads it to suppress the "tenant-scoped write without `tenantId`" warning, the driver's own warning text tells callers to set it, `ObjectQLEngine` sets it for system-context calls, and `service-settings` / `service-datasource` pass it on every global-scope write. Because the schema never had it, the driver read it through `(options as any)` and no caller was type-checked. The declaration states the limit as well: it silences a diagnostic and MUST NOT change which rows a write touches — suppressing an audit warning is not a permission. The same cast covered `timezone`, `tenantId`, `tenantIds` and `preserveAudit`, all long since declared. Those reads now go through `DriverOptions`, so the next undeclared option fails the build instead of hiding behind an existing cast. **`SqlDriver.findOne(object, id)` is removed.** An undeclared `typeof query === 'string' | 'number'` branch accepted a bare id. It was on no contract, nothing outside that package's own tests used it, and the other two drivers answered the identical call differently — `MemoryDriver` spreads the string into `{0:'t',1:'1'}`, `MongoDBDriver` reads `query.where` as `undefined` and returns an arbitrary row. It also bypassed the shared `findRows()` path, so it skipped field selection, temporal coercion, unknown-column recovery and the `singleRowLookup` ORDER BY decision. Spell an id lookup as the query it is: ```ts -(await driver.findOne("task", "t1")); +(await driver.findOne("task", { object: "task", where: { id: "t1" } })); ``` **`SqlDriver.initObjects` declares the `tenancy` it consumes.** Each object is fed to `computeAndRecordTenantField`, which reads `obj.tenancy` to pick the tenant column and to set or clear the sticky explicit-opt-out — but the parameter type listed only `{ name, fields }`, so a caller that spelled the key correctly was rejected while the driver read it anyway. `registerExternalObject` already had it. **`AnalyticsQueryInput` joins `AnalyticsQuery`.** `timezone` is `.default('UTC')`, so the parsed type requires it and an authored literal does not have it — the same two-tier split `QueryInput`/`QueryAST` already names on the query side. `InMemoryDriver.create`/`bulkCreate` also declare their `IDataDriver` return types; without them TS inferred the literal the method builds and every other column of the created row disappeared from the caller's view. One silent runtime bug fell out of the same pass: a driver test asked for `orderBy: [['id', 'asc']]`, the driver reads `item.field`, a tuple has none, and the sort never reached SQL. The tuple spelling appears nowhere else. - 06ba036: feat(drivers): `@objectstack/driver-turso` 迁回本仓并公开发布，五个 driver 统一收进 `packages/drivers/` (#4645) `TursoDriver` 一直以 `extends SqlDriver` 的方式**跨仓库继承**本仓的类，自己却住在闭源的 `objectstack-ai/cloud`（`publishConfig: restricted`）。而本仓的 runtime 早就把 turso 当一等 公民——`http-dispatcher.ts` 里环境 provisioning 的偏好顺序第一位就是它，`POST /cloud/environments` 的 `driver` 参数示例是 `memory | turso`，`objectql/src/engine.ts` 还带着一段 turso 专属的瞬时 `fetch failed` 重试。开源侧的代码路径引用着一个自己仓里既测不到也 grep 不到的 driver，闭源侧则 在每次 pin bump 时追赶父类的重构。维护者裁定把核心迁回本仓、公开 Apache-2.0 发布。 **新包 `@objectstack/driver-turso`（`packages/drivers/driver-turso`，Apache-2.0，`access: public`）** 带着它在 cloud 的全部实现与测试落地：`TursoDriver`（local / replica / remote 三种传输模式）、 `RemoteTransport`（纯 `@libsql/client` 走 HTTP/WebSocket，无原生依赖，可跑 serverless/edge）、 驱动的 spec/Studio 元数据，以及 15 个测试文件 538 条断言——全部 hermetic，默认 CI 下不碰网络、 不要凭据（remote 面走包内的 sqlite stub）。 **留在 cloud（不随迁）**：按租户路由的 `multi-tenant.ts`（云产品差异化能力）及其 schema、 `vector-poc.test.ts`。因此本包的 barrel **不再导出** `createMultiTenantRouter` / `MultiTenantConfig` / `MultiTenantRouter`，也不导出多租户 schema——它们从来不是这个 driver 的 一部分，只是曾经同包而已。 **目录重组**：五个 `IDataDriver` 实现（`driver-memory` / `driver-mongodb` / `driver-sql` / `driver-sqlite-wasm` + 迁入的 `driver-turso`）现在都住在 `packages/drivers/`， `knowledge-*` 与 `embedder-*` 留在 `packages/plugins/`。四个存量包**内容零改动**，只有 `repository.directory` 随目录更新——包名、入口、导出面、行为全部不变，消费者无需改动任何 import。 这也把 turso 交给了本仓的仓库级守卫：`check:driver-conformance` 从磁盘发现 driver 包， 迁入即入矩阵（5 drivers × 5 case-sets）。它的 temporal 两格是真绿（local 与 remote 双面套件）， filter 组合语义与两个分页 case-set 记为 measured DEBT——remote 传输自带一套 `buildWhereSQL` 与 `LIMIT`/`OFFSET` 拼装，是独立实现，"继承所以没问题"正是这些共享套件存在来证伪的假设。 补齐工作跟踪在 #5590。 - 9b43ee2: test(drivers): the filter-logic standard now covers the backend it was counted without (#4405) `FILTER_LOGIC_CASES` (#3774) opens by calling itself the standard "the four independent FilterCondition backends are each checked against". Five backends exist. `driver-mongodb`'s `translateFilter` was missed, not excluded — an independent implementation whose `$and`/`$or`/`$not` translation shares no line of code with the SQL compiler or the in-memory matcher, and the only one whose target language cannot spell the standard directly: MongoDB has no document-level `$not` at all (the server answers `unknown top level operator: $not`), so a negation has to leave as `$nor`, and a branch's own keys have to stay in one document while `$and`/`$or` clauses are lifted beside them. That route was never checked against the shared cases. Both DEBT rows the #4363 gate recorded are now cleared, and `scripts/check-driver-conformance.mjs` reports `ok` for every cell of the matrix. **`driver-mongodb` runs the table twice, and the split is deliberate.** `mongodb-filter-logic-translation.test.ts` drives every shared case through `translateFilter` and evaluates the emitted MongoDB _document_ over the shared fixture — a pure function, no server, so it always runs. That matters here more than anywhere: `mongodb-memory-server` downloads a ~123 MB binary from fastdl.mongodb.org, and a defect only a downloadable binary can catch is a defect nobody catches on a restricted network. Its in-process reader is strict by construction — every shape it does not model throws instead of evaluating to true, a document-level `$not` included — and its own discrimination is pinned by cases that require a widened document to FAIL the case it widens, so "all green" cannot mean "the reader says yes to everything". `mongodb-filter-logic-conformance.test.ts` runs the same table against a real mongod and answers the one question the first half cannot — does MongoDB agree? — skipping cleanly (never silently) when the binary is unreachable. **`driver-sqlite-wasm` runs the table through its own engine.** It inherits `SqlDriver`'s filter compiler, so nothing is re-implemented; what the suite pins is that a nested `(… AND …) OR (… AND …)` survives the custom sql.js dialect that compiles, binds and marshals it — the same seam its temporal and pagination suites cover for their clauses. Tracked as DEBT rather than EXEMPT because "inherits, therefore fine" is the assumption those suites exist to disprove; the suite is what disproves it. **No divergence was found.** `translateFilter` answers all seventeen shared cases correctly today, `$not`-inside-a-branch and nested `$and`-inside-`$or` included, so no translation change ships here — what changes is that the next edit to it cannot quietly widen a filter. Both suites were verified to be discriminating rather than decorative by reintroducing the #3774 miscompile (propagating `or` into a branch's own contents): 15 of the mongodb translation suite's 26 tests fail, and 13 of the wasm suite's 18. `packages/spec`'s `filter-logic-conformance.ts` header now says five and names the fifth — a code comment; no schema, export or generated artifact moved. - c53aa53: File-backed SQLite now runs `journal_mode = WAL` (#3941). `SqlDriver.connect()` set `auto_vacuum` and left the journal mode alone, so every ObjectStack SQLite database ran SQLite's built-in default — a rollback journal. That is the worst mode for the shape this platform actually has, which is **several processes on one file**: a dev server, `os migrate`, `os meta resync`, a test run. Measured, on the same file: | | rollback journal | WAL | | :--------------------------------------------- | :------------------------------------------------- | :---------------------------------------------------------------- | | writer while another process holds a read open | `SQLITE_BUSY` — committing needs an exclusive lock | proceeds | | idle attached connection visible to SQL | no — a lock lasts only as long as its transaction | yes (`locking_mode = EXCLUSIVE` + `BEGIN IMMEDIATE` reports busy) | The second row is why the `os migrate` occupancy check had to inspect file descriptors to see a live server at all (#3940): under a rollback journal there was nothing in the database to see. That signal stays — it names the process, which WAL's lock probe cannot — but the SQL probe is now authoritative for databases ObjectStack created rather than a fallback that was blind in practice. Concurrent _writers_ still serialize; SQLite allows one at a time in any mode. Journal mode is a persistent property of the file, so an existing database is converted in place on the next connect (a header change — no rows are touched) and stays converted. Two consequences to plan for: - `app.db-wal` / `app.db-shm` exist beside the database while a connection is attached, and `app.db-wal` can hold committed transactions. A clean shutdown checkpoints them away; a naive copy of `app.db` alone while a server runs does not. Use `sqlite3 app.db ".backup …"`. - **WAL does not work on network filesystems** (NFS/SMB). Opt out with `OS_DATABASE_SQLITE_JOURNAL_MODE=delete`, or per datasource with `sqliteJournalMode: 'delete'` in the driver config (which outranks the env var). Either form _applies_ `delete`, so it also converts a database that already adopted WAL back — skipping would have stranded it. Nothing here fails a boot, and nothing is assumed: `PRAGMA journal_mode = X` answers with the mode actually in force rather than raising on refusal, so the reply is read back; and because a filesystem can accept WAL and then fail the first read _through_ it, the mode is proven with a read and rolled back to `delete` if that fails — with a warning naming the file and the escape hatch. `synchronous` is untouched, so durability is exactly what it was. `:memory:` databases are left alone, as is `auto_vacuum = INCREMENTAL`, which keeps reclaiming under WAL (ADR-0057). `os db clean` now counts `-wal` / `-shm` as part of the database when it measures what a `VACUUM` reclaimed, so bytes that were sitting in the log do not read as a reclaim of zero. `@objectstack/driver-sqlite-wasm` deliberately stays out of WAL. Its live database is in the WASM heap and what reaches disk is a byte image it exports, so nothing reads the database across processes and the pragma buys it nothing — while still being a persistent header change in the operator's file. sql.js _accepts_ the pragma (its VFS is memory-backed), so this had to be declared rather than discovered. It also now parks a `-wal` left behind by an unclean native-driver exit rather than loading the image beside it: wasm SQLite cannot read that log, and leaving it next to a freshly rewritten image would let a later real SQLite replay frames that no longer belong to it. The warning names the file it parked and how to recover what was in it. - bee5ffe: drivers: every SQL read door routes through the tenant chokepoint (#6792) `SqlDriver.applyTenantScope()` owns read-side tenant isolation for the whole SQL family — the `tenantId` early-out, the "object has no tenant field" early-out, the NULL-org platform-row rule (#2734) and the ADR-0105 D2 union posture (#3623). Its own docstring said "every CRUD method routes through it". Nothing ever checked that, and it was false for as long as it had existed. **Three** read doors built their query through `getBuilder()` and never arrived: - **`findWithWindowFunctions()`** — the documented #4286 window door. It returns **rows**, so on a deployment where the scope would have applied (`options.tenantId` set, object has a tenant field) it returned rows belonging to **every** tenant. Measured with two tenants seeded plus one NULL-org platform row: `tenantId: 'org_a'` returned `[a1, a2, b1, b2, p1]` here against `find()`'s `[a1, a2, p1]` — another tenant's rows, handed over at the driver layer. - **`analyzeQuery()` / `explain()`** — returns a **plan**, not rows, so this is a smaller fix and it is made on its own merits rather than folded into the one above. It is the same defect #6577 fixed on these two methods one builder line lower: a plan is only worth reading if it explains the statement `find()` would actually run, and a missing tenant predicate changes selectivity and therefore which index the planner picks. Compiled `select * from account` where `find()` sent the `organization_id` clause. - **`distinct()`** — returns one column's **values** for every tenant. This one was in no card. #6792 states the opposite, listing `distinct` among the scoped call sites; the 13th read site is `aggregate()`. It was found by measuring the invariant rather than re-reading it. All three now call `applyTenantScope()` beside their `getBuilder()` line, the position `findRows()` uses. They route through the chokepoint rather than re-deriving a predicate: a local equality would silently drop NULL-org platform rows (#2734) and collapse group reads to active-org reach (#3623). Both of the chokepoint's early-outs are inherited unchanged, so an unscoped admin/seed read (no `tenantId`) and any object without a tenant field behave exactly as before. **The durable half is a gate, not the three lines.** `pnpm check:tenant-chokepoint` (`scripts/check-tenant-chokepoint.mjs`, wired into `.github/workflows/lint.yml`) re-derives the invariant from the AST across the `SqlDriver` family on every run: a method that builds through `getBuilder(object, options)` must call `applyTenantScope()` on that builder, or carry a written exemption. Insert builders are exempt structurally — write-side tenancy is `injectTenantOnInsert` — rather than by a name list. It is keyed on the **builder** and not on the method signature, because the signature criterion the card sketches ("takes `(object, …, options)` and returns rows") misses `distinct` (no `query` parameter) and `analyzeQuery` (returns a plan). Verified red against the pre-fix tree, red against a newly-added unscoped door, and silent once that door is scoped. The chokepoint docstring no longer asserts the invariant; it names the gate that proves it. If you call these doors directly on a multi-tenant deployment, pass `options.tenantId` as you would to `find()` — that is what now takes effect. Callers that never passed it are unaffected; that remains the documented unscoped/admin path. - 24915d2: fix(driver-sqlite-wasm): a `RETURNING` write is a write — persist it (#4518) A file-backed `sqlite-wasm` database flushed its schema at boot and then recorded nothing else. Every table was on disk; every row written after schema sync lived only in the WASM heap and died with the process. Reopening the file found a complete, empty database. **Cause.** The Knex dialect picked its execution branch from _"does this statement return rows"_ — and then marked the database dirty only on the other, row-less branch. `INSERT … RETURNING *` returns rows, so it executed on the row-returning branch and never set the flag. Since the `on-disconnect` flush is gated on the same flag, nothing rescued it afterwards either: **both** persist strategies dropped the write. ObjectQL writes through `RETURNING *` (it hands the stored row back to the caller), so this covered essentially all business data, along with `knex.raw('INSERT …')` and any other mutation arriving without a Knex `method`. **Fix.** "Does this statement change the database?" is now one exported predicate — `statementMutatesDatabase(sql, method)` — classifying by Knex method _and_ SQL text, applied at a single funnel after execution. It is independent of which branch executed the statement, so a mutation can no longer slip through by returning rows, by arriving without a method, or by taking a branch that forgot to say so. Transaction control still routes to `noteTransactionControl`, which keeps deferring flushes until the transaction closes (#1494), and mutating `PRAGMA` assignments (`auto_vacuum`, `user_version`) now count as writes too. **What changes for you.** Nothing to author. File-backed wasm SQLite now actually persists under `on-write` / `debounced:*`, and `disconnect()` is a real durability boundary: when it returns, committed data is on disk. This is what `bootStack({ databaseFile })` in `@objectstack/verify` needed to make `stop()` → second `bootStack` a genuine cold boot — the suspended-run restart proof ADR-0019 promises is now asserted end to end in the dogfood gate. Expect more disk writes than before on a file-backed dev database, because previously there were almost none. **One internal signature moved.** `WasmSqliteConnection.markDirty(method?)` is now `markDirty()`. It used to re-filter the caller's Knex method against its own allowlist, which made "did this mutate?" a decision taken in two places that could — and did — disagree. If you call it directly, drop the argument; the dialect classifies, the connection obeys. - Updated dependencies [50616d9] - Updated dependencies [430dcc2] - Updated dependencies [690ccf2] - Updated dependencies [6a67d7a] - Updated dependencies [333a374] - Updated dependencies [9fe9c1d] - Updated dependencies [3d5c090] - Updated dependencies [e5bd768] - Updated dependencies [08b5a3d] - Updated dependencies [e027b3e] - Updated dependencies [e6ac4bd] - Updated dependencies [c2429b0] - Updated dependencies [445a0c2] - Updated dependencies [d99aeb3] - Updated dependencies [f6609e6] - Updated dependencies [4727eb8] - Updated dependencies [a70358a] - Updated dependencies [0ecc656] - Updated dependencies [06772eb] - Updated dependencies [d4e0809] - Updated dependencies [80334c7] - Updated dependencies [f63cd09] - Updated dependencies [97e7e3c] - Updated dependencies [ce5242c] - Updated dependencies [a7163ea] - Updated dependencies [e6e9379] - Updated dependencies [5823d59] - Updated dependencies [3140f9c] - Updated dependencies [9500ba4] - Updated dependencies [fa3d0cf] - Updated dependencies [af5a224] - Updated dependencies [71f76e1] - Updated dependencies [37b1346] - Updated dependencies [99736a0] - Updated dependencies [fe67e34] - Updated dependencies [fdb4f50] - Updated dependencies [270650f] - Updated dependencies [3aef718] - Updated dependencies [1bd5652] - Updated dependencies [14252d3] - Updated dependencies [7fb436c] - Updated dependencies [879ea13] - Updated dependencies [8828b9e] - Updated dependencies [1ea6bce] - Updated dependencies [c1dcacd] - Updated dependencies [ad303ed] - Updated dependencies [32ccb23] - Updated dependencies [f5a4ef0] - Updated dependencies [2d3e255] - Updated dependencies [a8940e4] - Updated dependencies [7d7521f] - Updated dependencies [5dc4d02] - Updated dependencies [f724f69] - Updated dependencies [98877c9] - Updated dependencies [98877c9] - Updated dependencies [53068c1] - Updated dependencies [ee58392] - Updated dependencies [f16e54e] - Updated dependencies [06be54e] - Updated dependencies [28ad90e] - Updated dependencies [76d74ec] - Updated dependencies [201b31f] - Updated dependencies [e6b1b69] - Updated dependencies [29e28a3] - Updated dependencies [c7f4417] - Updated dependencies [259459d] - Updated dependencies [3f7f14e] - Updated dependencies [e2616e0] - Updated dependencies [6fdc5c6] - Updated dependencies [8b9d71e] - Updated dependencies [05154a1] - Updated dependencies [33f5e23] - Updated dependencies [259af21] - Updated dependencies [f8644c7] - Updated dependencies [306ca50] - Updated dependencies [978fed2] - Updated dependencies [cfc293f] - Updated dependencies [587fc91] - Updated dependencies [de70b42] - Updated dependencies [9b6fe7c] - Updated dependencies [fb3d99b] - Updated dependencies [1986594] - Updated dependencies [6968885] - Updated dependencies [eaed61f] - Updated dependencies [cdfbee2] - Updated dependencies [ad4af62] - Updated dependencies [debe2f6] - Updated dependencies [d44dbfa] - Updated dependencies [29c6c9d] - Updated dependencies [d21c001] - Updated dependencies [ad047d2] - Updated dependencies [8c711fb] - Updated dependencies [f1cc3a3] - Updated dependencies [09e4547] - Updated dependencies [97b0798] - Updated dependencies [474fe39] - Updated dependencies [0bc685a] - Updated dependencies [b949059] - Updated dependencies [2826d1e] - Updated dependencies [be1c52c] - Updated dependencies [c5ff96d] - Updated dependencies [5a84d41] - Updated dependencies [84e7be9] - Updated dependencies [91f4c78] - Updated dependencies [ddc2527] - Updated dependencies [820eff9] - Updated dependencies [a6c3f38] - Updated dependencies [debc23a] - Updated dependencies [0f8ad09] - Updated dependencies [553a47f] - Updated dependencies [43a7a8d] - Updated dependencies [a98085f] - Updated dependencies [20b1a9e] - Updated dependencies [344a22a] - Updated dependencies [4827e91] - Updated dependencies [8d895ff] - Updated dependencies [86f7a20] - Updated dependencies [a3a884d] - Updated dependencies [cfed092] - Updated dependencies [203a449] - Updated dependencies [8f9689f] - Updated dependencies [73f69dc] - Updated dependencies [04c56aa] - Updated dependencies [f6472d7] - Updated dependencies [57a3bb3] - Updated dependencies [b3efeb7] - Updated dependencies [ecb39ea] - Updated dependencies [ddd075a] - Updated dependencies [88154be] - Updated dependencies [db12b88] - Updated dependencies [62452c6] - Updated dependencies [6f6fec7] - Updated dependencies [7d1ff75] - Updated dependencies [e8dc61e] - Updated dependencies [9c82146] - Updated dependencies [5f9a987] - Updated dependencies [744b8f5] - Updated dependencies [ac37fc6] - Updated dependencies [2f3e793] - Updated dependencies [4820f55] - Updated dependencies [462d9c4] - Updated dependencies [78caf51] - Updated dependencies [7d21581] - Updated dependencies [37785ed] - Updated dependencies [62a789b] - Updated dependencies [2e284b2] - Updated dependencies [d8e8d9c] - Updated dependencies [789ad63] - Updated dependencies [f2445c9] - Updated dependencies [94e749b] - Updated dependencies [ea1d916] - Updated dependencies [2af1988] - Updated dependencies [0af50a3] - Updated dependencies [1b49eaf] - Updated dependencies [ae31a19] - Updated dependencies [2e836de] - Updated dependencies [e0f300b] - Updated dependencies [0161c7f] - Updated dependencies [e900015] - Updated dependencies [db02d47] - Updated dependencies [b5bdf48] - Updated dependencies [23338c3] - Updated dependencies [12a19a8] - Updated dependencies [5b843fb] - Updated dependencies [62b6a2f] - Updated dependencies [7e5af5c] - Updated dependencies [5b4780b] - Updated dependencies [a933452] - Updated dependencies [9d1d9c7] - Updated dependencies [8140915] - Updated dependencies [a019e52] - Updated dependencies [e8f8f6c] - Updated dependencies [41dcda3] - Updated dependencies [7b48cf9] - Updated dependencies [b5404f4] - Updated dependencies [64fc6d5] - Updated dependencies [b746aa0] - Updated dependencies [b4487aa] - Updated dependencies [1007379] - Updated dependencies [65ca83a] - Updated dependencies [0bfdf46] - Updated dependencies [947d4f9] - Updated dependencies [f764691] - Updated dependencies [e120a5a] - Updated dependencies [e5bd2f6] - Updated dependencies [e650d67] - Updated dependencies [04476e7] - Updated dependencies [67bf2e2] - Updated dependencies [eaaf03c] - Updated dependencies [d17df80] - Updated dependencies [7d0e7b5] - Updated dependencies [c6d1cb4] - Updated dependencies [6513c17] - Updated dependencies [36030ff] - Updated dependencies [79228cd] - Updated dependencies [6117f7b] - Updated dependencies [e533b0b] - Updated dependencies [cdf4d9a] - Updated dependencies [aee1806] - Updated dependencies [c13350b] - Updated dependencies [c13350b] - Updated dependencies [2c1988c] - Updated dependencies [9ca2d85] - Updated dependencies [c13350b] - Updated dependencies [891d345] - Updated dependencies [42e3b01] - Updated dependencies [c8124e5] - Updated dependencies [a52e2ef] - Updated dependencies [5293114] - Updated dependencies [376a061] - Updated dependencies [c142ced] - Updated dependencies [211abdb] - Updated dependencies [b3363e9] - Updated dependencies [39eb01b] - Updated dependencies [eda599e] - Updated dependencies [a1a4140] - Updated dependencies [7c7e246] - Updated dependencies [2ef1807] - Updated dependencies [f35cdc5] - Updated dependencies [d03fe25] - Updated dependencies [217e2e6] - Updated dependencies [2672f85] - Updated dependencies [20bc357] - Updated dependencies [11066f6] - Updated dependencies [916af17] - Updated dependencies [84c86fb] - Updated dependencies [2a2a9fb] - Updated dependencies [86a71d1] - Updated dependencies [c001422] - Updated dependencies [77022a9] - Updated dependencies [d5c75e2] - Updated dependencies [03d26f7] - Updated dependencies [5966c2a] - Updated dependencies [2382580] - Updated dependencies [9ea2bc5] - Updated dependencies [a2e157c] - Updated dependencies [95c4227] - Updated dependencies [2a61116] - Updated dependencies [52760bf] - Updated dependencies [5543020] - Updated dependencies [880d343] - Updated dependencies [6e82972] - Updated dependencies [d4df105] - Updated dependencies [4615a18] - Updated dependencies [f505689] - Updated dependencies [d9fa683] - Updated dependencies [32d3800] - Updated dependencies [606d577] - Updated dependencies [4384921] - Updated dependencies [d367f03] - Updated dependencies [45e711a] - Updated dependencies [465a0fa] - Updated dependencies [cf5e033] - Updated dependencies [6de592c] - Updated dependencies [d254421] - Updated dependencies [e2798fa] - Updated dependencies [06ba036] - Updated dependencies [3c628ce] - Updated dependencies [c2d9098] - Updated dependencies [0fd8556] - Updated dependencies [3c7bcc0] - Updated dependencies [4b6cac7] - Updated dependencies [7631964] - Updated dependencies [ac471a0] - Updated dependencies [60ae58e] - Updated dependencies [7f62706] - Updated dependencies [667fa44] - Updated dependencies [37e38d1] - Updated dependencies [e906126] - Updated dependencies [ce92674] - Updated dependencies [08363a0] - Updated dependencies [444de5b] - Updated dependencies [0f17114] - Updated dependencies [a227ed7] - Updated dependencies [7cb922e] - Updated dependencies [1d22114] - Updated dependencies [1eb13a0] - Updated dependencies [c52e608] - Updated dependencies [9613396] - Updated dependencies [3f7b4ff] - Updated dependencies [74155c7] - Updated dependencies [b5f9397] - Updated dependencies [ed77493] - Updated dependencies [6908830] - Updated dependencies [8b06bba] - Updated dependencies [58a03d2] - Updated dependencies [2bacd1a] - Updated dependencies [e47b342] - Updated dependencies [4c54037] - Updated dependencies [dc530b4] - Updated dependencies [9f601e8] - Updated dependencies [6a9dec6] - Updated dependencies [0f7157b] - Updated dependencies [4dc1c7d] - Updated dependencies [d9bef45] - Updated dependencies [4dfd002] - Updated dependencies [f549a0d] - Updated dependencies [51c5227] - Updated dependencies [82da264] - Updated dependencies [f586f1a] - Updated dependencies [77be690] - Updated dependencies [4ed7ed4] - Updated dependencies [9b9b70f] - Updated dependencies [f5a9bc2] - Updated dependencies [e59786e] - Updated dependencies [2fa4ca1] - Updated dependencies [bcf1112] - Updated dependencies [baeb4f0] - Updated dependencies [29488cc] - Updated dependencies [881a3cc] - Updated dependencies [f5a2320] - Updated dependencies [ad6317b] - Updated dependencies [811c30c] - Updated dependencies [a4a85c8] - Updated dependencies [859cb83] - Updated dependencies [07a4e26] - Updated dependencies [9774b78] - Updated dependencies [8a88885] - Updated dependencies [deb538f] - Updated dependencies [b49ccfd] - Updated dependencies [c7406b0] - Updated dependencies [5b89711] - Updated dependencies [85d95e7] - Updated dependencies [08cd163] - Updated dependencies [0c8a22f] - Updated dependencies [6f98c2d] - Updated dependencies [5f7669e] - Updated dependencies [becbe53] - Updated dependencies [b127c8b] - Updated dependencies [763931e] - Updated dependencies [ec975f1] - Updated dependencies [168f60f] - Updated dependencies [b07d829] - Updated dependencies [de9af8a] - Updated dependencies [eb4204b] - Updated dependencies [a80302a] - Updated dependencies [a648e96] - Updated dependencies [a47ac06] - Updated dependencies [e4c61a7] - Updated dependencies [cc60165] - Updated dependencies [474f131] - Updated dependencies [081aa6f] - Updated dependencies [91f4c78] - Updated dependencies [050cd82] - Updated dependencies [4d552af] - Updated dependencies [44d677c] - Updated dependencies [c32944d] - Updated dependencies [1dd780f] - Updated dependencies [e8d0c21] - Updated dependencies [244ca86] - Updated dependencies [546ab3c] - Updated dependencies [c4df271] - Updated dependencies [c8d6f6e] - Updated dependencies [0b51bb6] - Updated dependencies [d9971d3] - Updated dependencies [7dc1067] - Updated dependencies [4f13be2] - Updated dependencies [a41ba5c] - Updated dependencies [189854c] - Updated dependencies [5d4de37] - Updated dependencies [0e3a226] - Updated dependencies [92a67f2] - Updated dependencies [9136327] - Updated dependencies [bf0ae99] - Updated dependencies [eb3e650] - Updated dependencies [abeb375] - Updated dependencies [cb3b6cd] - Updated dependencies [73b7234] - Updated dependencies [d2b97c3] - Updated dependencies [61cc079] - Updated dependencies [45dc446] - Updated dependencies [0e96e46] - Updated dependencies [c1d44f7] - Updated dependencies [59b794f] - Updated dependencies [ef4efa8] - Updated dependencies [cbb6a5c] - Updated dependencies [fc3a36a] - Updated dependencies [ab9fb5c] - Updated dependencies [69787f0] - Updated dependencies [5d022a1] - Updated dependencies [042b9ee] - Updated dependencies [f985b3f] - Updated dependencies [795b6e1] - Updated dependencies [d52d4fe] - Updated dependencies [742cebb] - Updated dependencies [175d789] - Updated dependencies [f549a0d] - Updated dependencies [427344c] - Updated dependencies [8af76ae] - Updated dependencies [1d4756e] - Updated dependencies [720c5ad] - Updated dependencies [a8d1e24] - Updated dependencies [b85cc54] - Updated dependencies [a36db28] - Updated dependencies [7a8476f] - Updated dependencies [518ca7a] - Updated dependencies [41642b0] - Updated dependencies [4cca74c] - Updated dependencies [88ef03e] - Updated dependencies [9a4932a] - Updated dependencies [3f8817a] - Updated dependencies [a2443e3] - Updated dependencies [e1554b1] - Updated dependencies [9e2caf3] - Updated dependencies [4856789] - Updated dependencies [81ce41a] - Updated dependencies [85e1e4e] - Updated dependencies [c3f4916] - Updated dependencies [55dbbba] - Updated dependencies [33e0385] - Updated dependencies [dac6a08] - Updated dependencies [72c3c86] - Updated dependencies [2d8dba3] - Updated dependencies [7f1a635] - Updated dependencies [2205363] - Updated dependencies [09fe58d] - Updated dependencies [f9fc874] - Updated dependencies [d62f8eb] - Updated dependencies [d0a5ceb] - Updated dependencies [a7586cd] - Updated dependencies [4c5e80e] - Updated dependencies [ef678d0] - Updated dependencies [4b5702a] - Updated dependencies [011b386] - Updated dependencies [e18a162] - Updated dependencies [394b7a1] - Updated dependencies [ce92674] - Updated dependencies [0f2fdcd] - Updated dependencies [d6d1a50] - Updated dependencies [cf2c9b7] - Updated dependencies [8ffa8b9] - Updated dependencies [d127ff0] - Updated dependencies [674ac99] - Updated dependencies [833b512] - Updated dependencies [36d90fc] - Updated dependencies [7777e8f] - Updated dependencies [9b86cf6] - Updated dependencies [d063a96] - Updated dependencies [8825a06] - Updated dependencies [5087ac6] - Updated dependencies [677b591] - Updated dependencies [cf7c694] - Updated dependencies [ddd0f06] - Updated dependencies [d77d1b7] - Updated dependencies [0f9faa2] - Updated dependencies [2d1ddf0] - Updated dependencies [354b00f] - Updated dependencies [3de535b] - Updated dependencies [fe2e15a] - Updated dependencies [5b79a34] - Updated dependencies [502564d] - Updated dependencies [603cab8] - Updated dependencies [c757854] - Updated dependencies [471839d] - Updated dependencies [507b92a] - Updated dependencies [46365ab] - Updated dependencies [b508244] - Updated dependencies [6146b67] - Updated dependencies [df95346] - Updated dependencies [3dede58] - Updated dependencies [c6b6bb4] - Updated dependencies [594508e] - Updated dependencies [7cf42fe] - Updated dependencies [5966c2a] - Updated dependencies [0045682] - Updated dependencies [7309c81] - Updated dependencies [2f59da0] - Updated dependencies [d56012f] - Updated dependencies [f78dd83] - Updated dependencies [a2cd18a] - Updated dependencies [9051802] - Updated dependencies [20bc1ec] - Updated dependencies [1c625ca] - Updated dependencies [2f8328c] - Updated dependencies [2a6c279] - Updated dependencies [9319586] - Updated dependencies [8c8f0df] - Updated dependencies [8ad609c] - Updated dependencies [bbee302] - Updated dependencies [90c2b15] - Updated dependencies [4638aaa] - Updated dependencies [0222d3c] - Updated dependencies [08863dd] - Updated dependencies [33a5ff4] - Updated dependencies [9e01213] - Updated dependencies [071d0dc] - Updated dependencies [f293d45] - Updated dependencies [56664f5] - Updated dependencies [71f205d] - Updated dependencies [f067930] - Updated dependencies [414395b] - Updated dependencies [42eeb7d] - Updated dependencies [31cbe90] - Updated dependencies [6b7129a] - Updated dependencies [c5adfe1] - Updated dependencies [97ace2a] - Updated dependencies [26e1029] - Updated dependencies [0a936ea] - Updated dependencies [90bbf25] - Updated dependencies [023c00b] - Updated dependencies [eb91eba] - Updated dependencies [42da73d] - Updated dependencies [01e124d] - Updated dependencies [4addd9d] - Updated dependencies [ef7b5ef] - Updated dependencies [9514767] - Updated dependencies [8f20201] - Updated dependencies [155507e] - Updated dependencies [643b7c7] - Updated dependencies [7bba90b] - Updated dependencies [8813b90] - Updated dependencies [108ba8d] - Updated dependencies [2a5f04a] - Updated dependencies [4f740b0] - Updated dependencies [7ce02eb] - Updated dependencies [b4ad984] - Updated dependencies [a9f32df] - Updated dependencies [aeb9b27] - Updated dependencies [7d27da0] - Updated dependencies [d0d5205] - Updated dependencies [4fccace] - Updated dependencies [1a15893] - Updated dependencies [b70e534] - Updated dependencies [7e05d8e] - Updated dependencies [8f1851e] - Updated dependencies [61ea810] - Updated dependencies [2233a85] - Updated dependencies [67452d1] - Updated dependencies [089767f] - Updated dependencies [a13827e] - Updated dependencies [66d99ec] - Updated dependencies [cb43296] - Updated dependencies [b61afc1] - Updated dependencies [79021fc] - Updated dependencies [7733604] - Updated dependencies [40e420f] - Updated dependencies [62dd69a] - Updated dependencies [d13004a] - Updated dependencies [be7360c] - Updated dependencies [e15e679] - Updated dependencies [2ddba89] - Updated dependencies [2ab1257] - Updated dependencies [3fe0ff1] - Updated dependencies [0fc6219] - Updated dependencies [061406d] - Updated dependencies [e4c8b6c] - Updated dependencies [acb10f6] - Updated dependencies [605e190] - Updated dependencies [c6c59f1] - Updated dependencies [b0e78a8] - Updated dependencies [f31cc8d] - Updated dependencies [f343dc4] - Updated dependencies [8269e32] - Updated dependencies [74f7339] - Updated dependencies [a6c35a2] - Updated dependencies [c2f1002] - Updated dependencies [4cc4fb7] - Updated dependencies [97b6658] - Updated dependencies [28d1eb7] - Updated dependencies [06770c0] - Updated dependencies [2c26040] - Updated dependencies [f758cec] - Updated dependencies [5b47ab5] - Updated dependencies [b09d8d9] - Updated dependencies [b09d8d9] - Updated dependencies [8675db6] - Updated dependencies [b09d8d9] - Updated dependencies [27358d5] - Updated dependencies [1c3da1f] - Updated dependencies [c1f344b] - Updated dependencies [3eb1b2b] - Updated dependencies [9c93465] - Updated dependencies [a34fd2e] - Updated dependencies [ebb209c] - Updated dependencies [76bcb83] - Updated dependencies [59b85c0] - Updated dependencies [889ae47] - Updated dependencies [4f4c3fb] - Updated dependencies [78f0be8] - Updated dependencies [6e357ed] - Updated dependencies [d6938bf] - Updated dependencies [35f7fb4] - Updated dependencies [0410522] - Updated dependencies [63b33e6] - Updated dependencies [f163028] - Updated dependencies [814db6d] - Updated dependencies [a5302c7] - Updated dependencies [9c5abf4] - Updated dependencies [82397b6] - Updated dependencies [31e0be9] - Updated dependencies [4bfd455] - Updated dependencies [ffd2ce2] - Updated dependencies [2a44c1d] - Updated dependencies [7084313] - Updated dependencies [f07808c] - Updated dependencies [7ffc3d3] - Updated dependencies [88346ba] - Updated dependencies [4631592] - Updated dependencies [62f8017] - Updated dependencies [32ff033] - Updated dependencies [a831df1] - Updated dependencies [f752ee3] - Updated dependencies [a1b61e0] - Updated dependencies [cd6b9f2] - Updated dependencies [2cb6d3c] - Updated dependencies [af2a095] - Updated dependencies [5ac93d4] - Updated dependencies [695cfbd] - Updated dependencies [0e043d8] - Updated dependencies [93f267f] - Updated dependencies [7445149] - Updated dependencies [ec796d5] - Updated dependencies [071d0dc] - Updated dependencies [0024abf] - Updated dependencies [8dd98bf] - Updated dependencies [e87fea1] - Updated dependencies [c65e529] - Updated dependencies [0848bea] - Updated dependencies [d51bed2] - Updated dependencies [dadd1ad] - Updated dependencies [acbf364] - Updated dependencies [3ca34c1] - Updated dependencies [7adc841] - Updated dependencies [239c3a3] - Updated dependencies [b8b3c64] - Updated dependencies [2f2e63c] - Updated dependencies [4845f85] - Updated dependencies [486d526] - Updated dependencies [94a0bbc] - Updated dependencies [d6bfb3d] - Updated dependencies [8a9c079] - Updated dependencies [7b005b4] - Updated dependencies [cc3555e] - Updated dependencies [a2266a6] - Updated dependencies [d25a0ec] - Updated dependencies [89d7b35] - Updated dependencies [94f7b6a] - Updated dependencies [5c94f83] - Updated dependencies [ea936f3] - Updated dependencies [f98fa65] - Updated dependencies [0c0fbd9] - Updated dependencies [667b83e] - Updated dependencies [f3141d8] - Updated dependencies [7687f7b] - Updated dependencies [5a84d41] - Updated dependencies [fd3013a] - Updated dependencies [85ec26d] - Updated dependencies [73e576f] - Updated dependencies [f6476fc] - Updated dependencies [69ac82c] - Updated dependencies [4ac12ef] - Updated dependencies [833ed84] - Updated dependencies [a18abf3] - Updated dependencies [c6a4eeb] - Updated dependencies [1659072] - Updated dependencies [f450ae7] - Updated dependencies [abceb0d] - Updated dependencies [627b188] - Updated dependencies [8d4eae7] - Updated dependencies [c5a5996] - Updated dependencies [0c302a7] - Updated dependencies [b88f5e8] - Updated dependencies [857a6cf] - Updated dependencies [65a3a84] - Updated dependencies [6633337] - Updated dependencies [21676eb] - Updated dependencies [e9cb9ab] - Updated dependencies [42cc219] - Updated dependencies [d7e0b42] - Updated dependencies [3510e4a] - Updated dependencies [f00d8d4] - Updated dependencies [5326b36] - Updated dependencies [aa4b90d] - Updated dependencies [ccd9397] - Updated dependencies [503be86] - Updated dependencies [647ec8b] - Updated dependencies [54299ca] - Updated dependencies [3264516] - Updated dependencies [ae490ef] - Updated dependencies [e124711] - Updated dependencies [dc61def] - Updated dependencies [bca935b] - Updated dependencies [d92c72d] - Updated dependencies [c54c822] - Updated dependencies [8dcc0f5] - Updated dependencies [75b9e51] - Updated dependencies [f61c8cf] - Updated dependencies [e3ef52b] - Updated dependencies [0a2f233] - Updated dependencies [8621cdd] - Updated dependencies [251e888] - Updated dependencies [07f1822] - Updated dependencies [e336549] - Updated dependencies [3bb9340] - Updated dependencies [1e604c4] - Updated dependencies [04fab5e] - Updated dependencies [183b4c4] - Updated dependencies [7f713b6] - Updated dependencies [d40f43a] - Updated dependencies [2fdb36e] - Updated dependencies [62159bd] - Updated dependencies [193cd5c] - Updated dependencies [f1544e2] - Updated dependencies [7457a09] - Updated dependencies [5aae790] - Updated dependencies [07f1822] - Updated dependencies [d48aad5] - Updated dependencies [5f0852f] - Updated dependencies [c53aa53] - Updated dependencies [6f23667] - Updated dependencies [cde1975] - Updated dependencies [0bc685a] - Updated dependencies [20526f5] - Updated dependencies [efedd28] - Updated dependencies [5d21a48] - Updated dependencies [5278e11] - Updated dependencies [c5eef1d] - Updated dependencies [e5e7ee0] - Updated dependencies [23dba62] - Updated dependencies [e0f300b] - Updated dependencies [761a0ba] - Updated dependencies [c960170] - Updated dependencies [19365b7] - Updated dependencies [ba98e26] - Updated dependencies [b7ed26d] - Updated dependencies [a2ebea2] - Updated dependencies [800bdb0] - Updated dependencies [9d4dfc4] - Updated dependencies [1059965] - Updated dependencies [def5919] - Updated dependencies [ee264b2] - Updated dependencies [60b672e] - Updated dependencies [6b441a8] - Updated dependencies [ce0cfe9] - Updated dependencies [04f1182] - Updated dependencies [be87153] - Updated dependencies [dd0f681] - Updated dependencies [60f0dd8] - Updated dependencies [a87c5cd] - Updated dependencies [a47f338] - Updated dependencies [b3a3d83] - Updated dependencies [7a55913] - Updated dependencies [35accbf] - Updated dependencies [6038de7] - Updated dependencies [fc5f536] - Updated dependencies [bee5ffe] - Updated dependencies [5647006] - Updated dependencies [e654bfd] - Updated dependencies [01a7337] - Updated dependencies [b45c71e] - Updated dependencies [d71ff32] - Updated dependencies [3172831] - Updated dependencies [f8cfbb4] - Updated dependencies [939f579] - Updated dependencies [6e6c872] - Updated dependencies [2598216] - Updated dependencies [11949fc] - Updated dependencies [2c7e62d] - Updated dependencies [eb95d97] - Updated dependencies [b098b0e] - Updated dependencies [4d00b13] - Updated dependencies [1363084] - Updated dependencies [fa5758e] - Updated dependencies [38f7e4f] - Updated dependencies [eb7613c] - Updated dependencies [c57f3cf] - Updated dependencies [ecc9110] - Updated dependencies [e4c2dc8] - Updated dependencies [97faca3] - Updated dependencies [57bab76] - Updated dependencies [c89d18c] - Updated dependencies [1bd2795] - Updated dependencies [f7bd4e2] - Updated dependencies [694c350] - Updated dependencies [361bd5b] - Updated dependencies [acf34e3] - Updated dependencies [aac90a5] - Updated dependencies [3da3da5] - Updated dependencies [1e6ab15] - Updated dependencies [b90086a] - Updated dependencies [8186a70] - Updated dependencies [a329cca] - Updated dependencies [c87ef70] - Updated dependencies [3cb0618] - Updated dependencies [32a0874] - Updated dependencies [6eec18c] - Updated dependencies [4d7bebf] - Updated dependencies [821ac7a] - Updated dependencies [8f81731] - Updated dependencies [7055c22] - Updated dependencies [785a748] - Updated dependencies [3af0354] - Updated dependencies [866ff16] - Updated dependencies [5a85e67] - Updated dependencies [8b50cb3] - Updated dependencies [a0fdc56] - Updated dependencies [b95577a] - Updated dependencies [0dcbc11] - Updated dependencies [2342ee4] - Updated dependencies [d88f3e9] - Updated dependencies [ad5fe25] - Updated dependencies [c183a12] - Updated dependencies [83c161f] - Updated dependencies [d8c4957] - Updated dependencies [b9f930b] - Updated dependencies [f24cb83] - Updated dependencies [5dbbb92] - Updated dependencies [ea90179] - Updated dependencies [1818998] - Updated dependencies [ce92674] - Updated dependencies [5ef0b5b] - Updated dependencies [8c2db68] - Updated dependencies [22b5e54] - Updated dependencies [0166bd5] - Updated dependencies [8064b07] - Updated dependencies [09ee21c] - Updated dependencies [4a56dbd] - Updated dependencies [289d04a] - Updated dependencies [f549a0d] - Updated dependencies [48fbacb] - Updated dependencies [06df4fa] - Updated dependencies [3fc2e48] - Updated dependencies [c9b809f] - Updated dependencies [e8f435c] - Updated dependencies [32386f8] - Updated dependencies [9b702dc] - Updated dependencies [ab16331] - Updated dependencies [41610f6] - Updated dependencies [69f1dfd] - Updated dependencies [bbe05de] - Updated dependencies [355e951] - Updated dependencies [a1dd1e4] - Updated dependencies [a5dcb74] - Updated dependencies [dadb43f] - Updated dependencies [3556b67] - @objectstack/spec@17.0.0 - @objectstack/core@17.0.0 - @objectstack/driver-sql@17.0.0 ## 17.0.0-rc.6 ### Major Changes - d367f03: refactor(drivers)!: 五个驱动的 query 参数跟进 `DriverQuery`，休眠的类型谎言就此没有藏身处 (#6075) #5181（PR #6076）把 `IDataDriver.find/findOne/count/updateMany/deleteMany/explain` 的 query 参数收窄为 `DriverQuery`（`Omit`），并在同一条 changeset 里写明：「把驱动签名一并迁到 `DriverQuery` 是后续的机械收尾」。这就是那次收尾。 在此之前，五个驱动的实现仍旧声明 `query: QueryAST`（turso 侧是 `query: any`）。**它不红，也不会红** —— 方法参数按双变比较，实现声明得比契约宽照样满足契约。但调用方现在**有权**省略 `object`，于是这些实现的类型说 `query.object` 是 `string`，运行期却可能是 `undefined`：一句休眠的谎言，没有任何门拦得住下一个照着它写代码的人。 收尾之后，「驱动读 `query.object`」直接变成编译错误： ```ts // 收窄前：编译通过，运行期可能是 undefined —— 谎言 // 收窄后：error TS2339: Property 'object' does not exist on type 'DriverQuery'. const name = query.object; ``` **零运行时改动。** 本次改的全部是类型注解：五个驱动的六个契约方法签名，以及为让类型自洽而必须跟进的少量私有辅助方法参数（mongodb 的 `buildFindOptions` / `buildSortSpec`，sql 的 `findRows` / `orderKeysFor`，turso 的 `toRemoteQuery` / `toRemoteReadQuery`，memory 的 `performAggregation`）—— 它们都只转发或读取 `where` / `orderBy` / `groupBy` 这些字段，本来就不读 `object`。turso 的几处 `query: any` 一并收紧，多拿回一批本已放弃的检查。emit 无差异，测试全绿（memory 524、mongodb 206、sql 906、sqlite-wasm 254、turso 788）。 **迁移面：删掉驱动调用字面量里的 `object:` 键**，与 #5181 是同一句话，只是现在也覆盖了直接按具体驱动类（`SqlDriver` / `MemoryDriver` / …）而非按 `IDataDriver` 取类型的调用方。编译器会逐处指出来（TS2353 `'object' does not exist in type 'DriverQuery'`）。本仓下游 25 个包实测零处需要改动，改动只落在五个驱动自己的测试里。 标 major 的依据与 #5181 一致：**源码级破坏性**（调用点内联字面量），运行时行为零变化。`check:api-surface` 只记录导出的存在与否、不记录签名，因此这条说明同样是该变更唯一的下游载体。 `aggregate` / `distinct` / `syncSchemasBatch` 不在本次范围内 —— 它们不是 `IDataDriver` 收窄的那六个方法，其中 `syncSchemasBatch` 的条目里 `object` 是被真实读取的必填键，`expand` 条目里的 `object` 同理命名的是关联对象，都不是冗余。 - 62159bd: refactor(driver-sql)!: `SqlDriver.distinct` 的第三参收成裸 `FilterCondition`，一个静默返回全集的写法就此编译不过 (#6320) `distinct` 不在 `IDataDriver` 上，所以 #5181（PR #6076）与 #6075（PR #6210）的收窄都没走到它，#6212 批 A+E（#6355）收的是 `analyzeQuery` / `findWithWindowFunctions`，也没覆盖它。它的方法体一直说得很清楚——`applyFilters(builder, filters)` 拿的是**实参本身**，因此它要的是 `find()` 放在 `query.where` 里的那个值，**不是 query 信封**；`filters?: any` 只是没把这句话写进类型里。 ```ts // 收窄前后都成立，一处调用点都不用改 await driver.distinct("orders", "product", { status: "completed" }); ``` **收窄真正买到的东西，是实测出来的，不是推断的。** 三行数据（`Laptop`/`Mouse` 为 `completed`，`Ghost` 为 `pending`），逐个形状喂给 `distinct('orders','product', …)`： | 第三参 | 收窄前 | 收窄后 | | :--------------------------- | :--------------------------------- | :----------- | | `{ status: 'completed' }` | 返回 `["Laptop","Mouse"]` | 不变 | | 省略 | 返回全集 | 不变 | | `'completed'`（标量） | **编译通过，返回全集** | **编译错误** | | `{ object, where }`（信封） | 抛 `INVALID_FILTER` / 400 | 不变 | | `['status','=','completed']` | 抛 `INVALID_FILTER` / 400（#5158） | 不变 | 第三行就是本次消掉的那一格：一个真心想问「completed 订单里有哪些商品」的调用，编译通过，然后拿到**每一个**商品。`applyFilters` 对「真值但非对象、非数组」的 filter 不发射任何谓词（该方法尾注写着这件事），于是过滤条件被整条丢掉。方向是**放宽**——这正是 #6320 与 #5234 同族的那类「静默错答案」。 **有一格是任何类型都关不上的，本次如实写进注释而不是假装关上了。** `FilterCondition` 的键**就是字段名**，所以它是开放映射（`[key: string]: any`）：`{ object, where }` 在结构上是一个完全合法的 filter——约束两个分别叫 `object` 和 `where` 的列。没有任何注解能把它和正当 filter 分开。#6320 提出的「让反向错配也编译不过」在这个参数上**不可达**，实测确认；能拿到的保证是**运行期响亮失败**：信封里的 `where` 是对象，而没有任何比较值可以是对象，于是 `assertCompilableComparand` 抛 `INVALID_FILTER` / 400。这半边 driver-sql 从来就不是静默的；`driver-memory` 那半边（裸 filter 交给它会静默返回全集）留在 #5499 冻结面内，本次不碰。 **零运行时改动**：非测试改动 100% 是一个类型注解加一段注释，无逻辑、无行为、无 emit 差异。 **逐处复核了全部 14 个调用点**（本单正文记的是 3 处，实测偏低）：driver-sql 11 处、driver-sqlite-wasm 3 处、driver-turso 0 处；其中真正传第三参的是 4 处（driver-sql 2 + driver-sqlite-wasm 2），全部本来就写的裸 filter，**零报错、零 fixture 改动**。 **driver-sqlite-wasm 也标 major**：`SqliteWasmDriver extends SqlDriver` 且不覆写 `distinct`，所以它**已发布的 `.d.ts`** 里这个方法的签名同样收窄，它的使用者看到的是同一个变化。该包读的是 driver-sql 构建后的 `dist/*.d.ts` 而非源码，是一处已知门禁盲区，本次用「往参数类型里临时塞一个调用方不可能满足的成员、重建、看调用点是否逐一变红」证明它确实读到了新 d.ts：driver-sql 6 处红、driver-sqlite-wasm 3 处红，与预判逐一相符。 ### 迁移 调用点若把**标量**（或任何非 `FilterCondition` 值）交给第三参，编译器会指出来： ``` error TS2345: Argument of type 'string' is not assignable to parameter of type 'FilterCondition'. ``` 改法是把它写成它本来就该是的裸 filter 对象（`'completed'` → `{ status: 'completed' }`）。⚠️ 这类调用点在收窄前拿到的是**未过滤的全集**，所以这不是一次等价改写：修完之后返回值会变，而变化后的那个才是调用方本来想要的答案。本仓零处这样的调用点。 ⚠️ 无类型的 JS 调用方**既不会拿到编译错误、也不会有任何行为变化**（本次零运行时改动）。对他们而言，上面那条是「你一直没在过滤」的**唯一通知渠道** —— 这也是本次记台账条目的理由，见下。 ### Minor Changes - 92a67f2: feat(drivers,spec)!: `GroupByNode.alias` is honoured by the SQL faces — one aggregate, one column key (#6401) `GroupByNodeSchema` has declared `alias` ("Alias for the projected group value", defaulting to `field`) for as long as the structured `groupBy` entry has existed. Exactly one execution path read it. The result: the SAME query came back with a different result-column key depending on which path the engine happened to take. ```ts groupBy: [{ field: "closed_at", dateGranularity: "month", alias: "qtr" }]; ``` - pushed down to a driver ⇒ rows keyed **`closed_at`** - run through the in-memory fallback ⇒ rows keyed **`qtr`** And the choice between them is `engine.ts`'s `allStructuredSupported && !tzRequiresInMemory` — a driver capability bit and a `timezone`, neither of which the caller can see. That is the multi-face consistency invariant broken in its quietest form: both answers are valid rows, so nothing throws and nothing looks wrong. **Resolved to ENFORCE**, and the leg was chosen by measurement rather than taste. ADR-0049 splits on whether the feature already exists: a _dangling_ promise is removed, a _live_ one with a missing gate is enforced. `alias` is live — three consumers read it and change behaviour (`in-memory-aggregation.ts`, `MemoryDriver.performAggregation`, and `chartAggregateCategoryKey`), and the publish gate _compels_ it: `validate-react-page-props.ts` errors `REACT_CHART_AXIS_UNKNOWN` unless a chart's category axis is bound to `alias ?? field`, telling the author in so many words to "bind it to" the alias. A key the build gate makes you write is not a dangling promise. The count of real non-test producers is **zero**, which is what makes enforcing safe rather than what argues against it: no shipped payload changes its result keys. **What changed, on every SQL face at once** — a fix landing on one and not its twin is the #6203 shape, and `TursoDriver` picks its face from `url`: - **`driver-sql`** — both limbs of the structured `groupBy` branch project `alias ?? field`: the date-bucket limb aliases the bucket expression to it, and the plain limb emits `?? as ??` (only when the name actually moves — an alias equal to the field emits no self-rename). `presentedOutput` is now keyed by the OUTPUT column, matching how the aggregation branch beside it has always worked; an aliased group value went unpresented before. - **`driver-turso` REMOTE** — the same projection, `"field" AS "alias"`. The alias reaches the statement as a quoted identifier and is therefore held to `assertSafeIdentifier`, exactly like `field`. - **`driver-sqlite-wasm`** — inherits `SqlDriver`'s compiler; covered by its own conformance suite rather than by assumption. **GROUP BY still keys on the FIELD** on every face. Only the projection is renamed, so the buckets are unchanged. This is deliberate and pinned: SQLite resolves output names in `GROUP BY`, so a face that grouped by the alias would look correct here and diverge on a dialect that does not. `having` needed no change and now means one thing: it is applied over the aggregated row's own columns, so a filter on a group projection references the alias on every path — previously the alias on one path and the field on the other. **Conformance.** `AGGREGATION_CASES` (#6409) gains a `groupByAlias` axis and two cases. Their VALUES are an existing case verbatim — only the key moves — so they can fail only on the key, which is the point: every wrong answer in this area is a valid query returning plausible rows. `objectql`'s in-memory fallback is now **enrolled** as a fourth face, answering #6409's open question ②: it is the face the SQL three were converged onto, so the new behaviour would otherwise be pinned against nothing, and reaching it needs no engine at all — `applyInMemoryAggregation` is a pure function of rows and an AST. **Reverse verification**, predicted before running. Reverting the in-memory face to `g.field`: only the two alias cases move and only ONE fails — the degenerate `alias === field` case stays green, which is why both are in the table. Reverting the harness to read `c.groupBy` instead of `c.groupByAlias ?? c.groupBy` — the copied-neighbour mistake: everything passes on an unmodified face, a false GREEN, which is the failure mode that would have made the axis vacuous. **Frozen drivers (#5499), measured from source, not flipped.** `driver-memory` already returned `{ field, alias: node.alias ?? node.field }` and projects under the alias — it had independently reached the enforce answer, so it needed no alignment. `driver-mongodb` is a recorded DEBT row and the defect is wider than `alias`: `buildAggregationPipeline` types `groupBy` as `string[]` and builds `groupId[field] = '$' + field`, so a structured node — aliased or not — becomes the literal key `"[object Object]"`. It cannot take a structured `GroupByNode` at all; `mongodb-driver.ts` passes `(query as any).groupBy`, which is why `tsc` never saw it. Tracked on #6814. **Compatibility.** A caller who writes `alias` and reads the result under `field` on a pushdown path will now find the value under `alias` — which is what the key has always meant on the fallback path, and what the chart gate already required. Callers who never write `alias` are unaffected: the emitted SQL is byte-identical. - 82397b6: feat(drivers,objectql): `$regex` / `$options` are refused everywhere, and `$icontains` is implemented on the SQL family (#5702) The driver half of the #4706 ruling. #5701 landed the contract (the vocabulary, the `RETIRED_FILTER_OPERATORS` prescriptions, the shared text case-set) and #5710 flipped the last live producer — `plugin-auth`'s ObjectQL adapter, which emitted `$regex` on the authentication path — so the refusal can now land without breaking sign-in. **BREAKING for anyone writing `$regex` or `$options` in a filter.** Both are refused on every backend with `INVALID_FILTER` / 400 and a message that names the replacement. `$regex` was never a declared operator: `driver-sql` compiled it to a LIKE-escaped substring (so `a.b` matched only the literal `a.b`), `driver-memory` ran it as a real `RegExp` (so the same filter also matched `axb`, and an _invalid_ pattern was caught and answered `false` — zero rows, in silence), and `objectql`'s `having` did the same. Write `$icontains` for the case-insensitive substring search this was almost always used for, `$contains` for a case-sensitive one; a pattern that genuinely needs a regex has no filter-level replacement. **`$icontains` now runs on the SQL family** — `driver-sql`, `driver-sqlite-wasm`, and both of `driver-turso`'s transports (the remote one does not go through knex, so it needed its own). It compiles to `LOWER(col) LIKE LOWER(?) ESCAPE ?` through the same `applyLike` / `pushLike` that carries the `%` / `_` / `\` escaping, as a `fold` parameter rather than a second emitter — a copied emitter is where the escape class would have been dropped, and an unescaped `%` matches every row. An empty or non-string comparand is refused on the validating walk (an empty one matches every row, which widens rather than narrows). On SQLite `lower()` folds ASCII only, which IS the contract (#4706 Q1 = A): `$icontains: 'café'` does not match `CAFÉ`. `driver-mongodb`'s unknown-operator arm was throwing a bare `Error` with no `code` and no `status`, three lines from the helper in its own file that sets `INVALID_FILTER` / 400 — a 500-shaped body for a 400-class client mistake. It now speaks the same envelope as its three siblings. Two parts of the ruling are deliberately NOT in this change and stay tracked in `scripts/check-driver-conformance.mjs`'s ledger: the `$contains` family's case-sensitivity (#4706 Q2 = A) needs SQLite's `LIKE` replaced by a case-exact construct in the driver, the RLS lowering and the analytics lowering together, or one permission rule compiles to two row sets (#6518); and `$icontains` on the JS evaluation faces needs the spec vocabulary to take the operator, which cannot happen before `driver-memory` has an arm for it (#6520). - 3172831: fix(drivers): text-operator case folding is the CONTRACT's answer, not the dialect's (#6518) The `$contains` family and `$icontains` returned **different rows on different databases** for the same filter, because case sensitivity was decided by whatever `LIKE` happened to mean on the dialect underneath. Both directions **over-matched** — they returned rows the filter excludes, which on an ADR-0021 RLS read scope is over-reach rather than a loose filter (#3948): | | `$contains` / `$notContains` / `$startsWith` / `$endsWith` — case-SENSITIVE (#4706 Q2 = A) | `$icontains` — folds ASCII ONLY (#4706 Q1 = A) | | :--------------------------- | :----------------------------------------------------------------------------------------- | :--------------------------------------------- | | SQLite / turso / sqlite-wasm | ❌ `LIKE` folds ASCII | ✅ `lower()` is ASCII-only | | Postgres | ✅ `LIKE` is case-exact | ❌ `LOWER()` folds all of Unicode | | MySQL | ❌ follows the column's collation | ❌ `LOWER()` folds all of Unicode | Read across: **each dialect was already right on the half another one got wrong**, which is why neither half could be found from one backend alone. ## What now runs The construct is chosen per dialect, in one emitter, so the escaping and the fold stay a single code path (an unescaped wildcard is a filter bypass, P0 — #5567): - **SQLite family → `GLOB`.** `LIKE`'s ASCII fold cannot be switched off per statement (`PRAGMA case_sensitive_like` is connection-global, so one query would redefine every other query on the connection), and `CAST(col AS BLOB) LIKE ?` was measured to match _nothing at all_. `GLOB` is case-exact and brings its own escaped class — `*`, `?`, `[` as the self-closing classes `[*]`, `[?]`, `[[]`, because SQLite's grammar gives `GLOB` no `ESCAPE` clause. `$icontains` keeps `lower()` on both operands, still ASCII-only. - **Postgres → `LIKE`, unchanged.** Only the fold moved, from `LOWER()` to an explicit `translate()` over the 26 ASCII letters. Measured on a live PostgreSQL 16 (ICU database): `LOWER('CAFÉ')` is `'café'` — the over-fold — while the `translate()` form leaves `É` alone. - **MySQL → `LIKE` over `CAST(… AS BINARY)`**, so the comparison is byte-wise and no collation decides the case; `$icontains` folds byte-wise over the same binary rendering, which is ASCII-only because UTF-8 is self-synchronising. - **Any other client** keeps the previous `LIKE` / `LOWER()` shape — it is the only form that still runs there — and is recorded as residue rather than left to be discovered. `driver-turso`'s remote transport carries the twin (it compiles filters itself and inherits nothing), and the two transports are now held to the same rows by a parity suite that runs the shared `FILTER_TEXT_CASES` on both. ## Behaviour change — read this before upgrading A filter whose comparand's case did not match the stored text used to match on SQLite/turso/sqlite-wasm and may have matched on MySQL. It no longer does: ```ts // rows: { id: '1', name: 'ACME Corp' }, { id: '2', name: 'acme corp' } { name: { $contains: "acme"; } } // was ['1','2'] on SQLite → now ['2'] everywhere { name: { $icontains: "acme"; } } // ['1','2'] — unchanged, and now correct on PG/MySQL too { name: { $icontains: "café"; } } // was ['3','4'] on PG/MySQL → now ['4'] everywhere ``` If you were relying on `$contains` to ignore case, **write `$icontains`** — that is the operator for it, and it now folds the same ASCII-only range on every backend. Result sets only ever get NARROWER, never wider, so a filter that was already correct stays correct. ## Why `minor` rather than `major` No declared surface moves. `$contains` still exists, still takes the same comparand, and `filter.zod.ts` is untouched — the case-sensitivity this delivers was **already published** as the contract by #5701 (`FILTER_TEXT_CASES`, one release earlier in this same v17 major), and the drivers were the half that had not caught up. This is Prime Directive #12 applied in the direction it points: declared = enforced. It is graded the way its sibling #5702/#6549 was graded for the same operator family in the same rc cycle, and it registers nothing in the ADR-0087 registries because it retires no authorable key. ## What is deliberately NOT in this change `driver-memory` and `driver-mongodb` still fold case on their query paths — they are the #5499 frozen family, so their `FILTER_TEXT_CASES` cells stay honest DEBT and are tracked as #6682 (case sensitivity) and #6520 (`$icontains`). The `service-analytics` SQL compilers were measured already compliant: they emit Postgres-shaped statements, where `LIKE` is case-exact, and that assumption is now written down and pinned rather than implied. ### Patch Changes - bee5ffe: drivers: every SQL read door routes through the tenant chokepoint (#6792) `SqlDriver.applyTenantScope()` owns read-side tenant isolation for the whole SQL family — the `tenantId` early-out, the "object has no tenant field" early-out, the NULL-org platform-row rule (#2734) and the ADR-0105 D2 union posture (#3623). Its own docstring said "every CRUD method routes through it". Nothing ever checked that, and it was false for as long as it had existed. **Three** read doors built their query through `getBuilder()` and never arrived: - **`findWithWindowFunctions()`** — the documented #4286 window door. It returns **rows**, so on a deployment where the scope would have applied (`options.tenantId` set, object has a tenant field) it returned rows belonging to **every** tenant. Measured with two tenants seeded plus one NULL-org platform row: `tenantId: 'org_a'` returned `[a1, a2, b1, b2, p1]` here against `find()`'s `[a1, a2, p1]` — another tenant's rows, handed over at the driver layer. - **`analyzeQuery()` / `explain()`** — returns a **plan**, not rows, so this is a smaller fix and it is made on its own merits rather than folded into the one above. It is the same defect #6577 fixed on these two methods one builder line lower: a plan is only worth reading if it explains the statement `find()` would actually run, and a missing tenant predicate changes selectivity and therefore which index the planner picks. Compiled `select * from account` where `find()` sent the `organization_id` clause. - **`distinct()`** — returns one column's **values** for every tenant. This one was in no card. #6792 states the opposite, listing `distinct` among the scoped call sites; the 13th read site is `aggregate()`. It was found by measuring the invariant rather than re-reading it. All three now call `applyTenantScope()` beside their `getBuilder()` line, the position `findRows()` uses. They route through the chokepoint rather than re-deriving a predicate: a local equality would silently drop NULL-org platform rows (#2734) and collapse group reads to active-org reach (#3623). Both of the chokepoint's early-outs are inherited unchanged, so an unscoped admin/seed read (no `tenantId`) and any object without a tenant field behave exactly as before. **The durable half is a gate, not the three lines.** `pnpm check:tenant-chokepoint` (`scripts/check-tenant-chokepoint.mjs`, wired into `.github/workflows/lint.yml`) re-derives the invariant from the AST across the `SqlDriver` family on every run: a method that builds through `getBuilder(object, options)` must call `applyTenantScope()` on that builder, or carry a written exemption. Insert builders are exempt structurally — write-side tenancy is `injectTenantOnInsert` — rather than by a name list. It is keyed on the **builder** and not on the method signature, because the signature criterion the card sketches ("takes `(object, …, options)` and returns rows") misses `distinct` (no `query` parameter) and `analyzeQuery` (returns a plan). Verified red against the pre-fix tree, red against a newly-added unscoped door, and silent once that door is scoped. The chokepoint docstring no longer asserts the invariant; it names the gate that proves it. If you call these doors directly on a multi-tenant deployment, pass `options.tenantId` as you would to `find()` — that is what now takes effect. Callers that never passed it are unaffected; that remains the documented unscoped/admin path. - Updated dependencies [3d5c090] - Updated dependencies [e5bd768] - Updated dependencies [e027b3e] - Updated dependencies [c2429b0] - Updated dependencies [445a0c2] - Updated dependencies [f6609e6] - Updated dependencies [a70358a] - Updated dependencies [97e7e3c] - Updated dependencies [8828b9e] - Updated dependencies [53068c1] - Updated dependencies [ee58392] - Updated dependencies [f16e54e] - Updated dependencies [06be54e] - Updated dependencies [29e28a3] - Updated dependencies [259459d] - Updated dependencies [3f7f14e] - Updated dependencies [6968885] - Updated dependencies [eaed61f] - Updated dependencies [debe2f6] - Updated dependencies [97b0798] - Updated dependencies [43a7a8d] - Updated dependencies [73f69dc] - Updated dependencies [04c56aa] - Updated dependencies [b3efeb7] - Updated dependencies [ddd075a] - Updated dependencies [88154be] - Updated dependencies [db12b88] - Updated dependencies [6f6fec7] - Updated dependencies [7d1ff75] - Updated dependencies [e8dc61e] - Updated dependencies [2f3e793] - Updated dependencies [d8e8d9c] - Updated dependencies [94e749b] - Updated dependencies [ea1d916] - Updated dependencies [ae31a19] - Updated dependencies [e0f300b] - Updated dependencies [62b6a2f] - Updated dependencies [5b4780b] - Updated dependencies [a933452] - Updated dependencies [8140915] - Updated dependencies [7b48cf9] - Updated dependencies [b5404f4] - Updated dependencies [f764691] - Updated dependencies [e120a5a] - Updated dependencies [e650d67] - Updated dependencies [04476e7] - Updated dependencies [79228cd] - Updated dependencies [b3363e9] - Updated dependencies [2ef1807] - Updated dependencies [d03fe25] - Updated dependencies [2672f85] - Updated dependencies [11066f6] - Updated dependencies [916af17] - Updated dependencies [84c86fb] - Updated dependencies [2a2a9fb] - Updated dependencies [a2e157c] - Updated dependencies [95c4227] - Updated dependencies [2a61116] - Updated dependencies [d4df105] - Updated dependencies [d367f03] - Updated dependencies [45e711a] - Updated dependencies [465a0fa] - Updated dependencies [6de592c] - Updated dependencies [d254421] - Updated dependencies [e2798fa] - Updated dependencies [0fd8556] - Updated dependencies [74155c7] - Updated dependencies [6908830] - Updated dependencies [8b06bba] - Updated dependencies [4c54037] - Updated dependencies [0f7157b] - Updated dependencies [d9bef45] - Updated dependencies [f549a0d] - Updated dependencies [82da264] - Updated dependencies [f586f1a] - Updated dependencies [9b9b70f] - Updated dependencies [f5a9bc2] - Updated dependencies [881a3cc] - Updated dependencies [ad6317b] - Updated dependencies [8a88885] - Updated dependencies [5f7669e] - Updated dependencies [becbe53] - Updated dependencies [b127c8b] - Updated dependencies [a80302a] - Updated dependencies [474f131] - Updated dependencies [050cd82] - Updated dependencies [4d552af] - Updated dependencies [44d677c] - Updated dependencies [c32944d] - Updated dependencies [1dd780f] - Updated dependencies [c8d6f6e] - Updated dependencies [92a67f2] - Updated dependencies [9136327] - Updated dependencies [bf0ae99] - Updated dependencies [cb3b6cd] - Updated dependencies [73b7234] - Updated dependencies [d2b97c3] - Updated dependencies [59b794f] - Updated dependencies [fc3a36a] - Updated dependencies [69787f0] - Updated dependencies [5d022a1] - Updated dependencies [042b9ee] - Updated dependencies [f549a0d] - Updated dependencies [a36db28] - Updated dependencies [3f8817a] - Updated dependencies [a2443e3] - Updated dependencies [e1554b1] - Updated dependencies [4856789] - Updated dependencies [c3f4916] - Updated dependencies [33e0385] - Updated dependencies [2205363] - Updated dependencies [09fe58d] - Updated dependencies [d0a5ceb] - Updated dependencies [ef678d0] - Updated dependencies [e18a162] - Updated dependencies [d6d1a50] - Updated dependencies [d127ff0] - Updated dependencies [9b86cf6] - Updated dependencies [8825a06] - Updated dependencies [5087ac6] - Updated dependencies [2d1ddf0] - Updated dependencies [354b00f] - Updated dependencies [3de535b] - Updated dependencies [fe2e15a] - Updated dependencies [6146b67] - Updated dependencies [c6b6bb4] - Updated dependencies [2f59da0] - Updated dependencies [8ad609c] - Updated dependencies [bbee302] - Updated dependencies [08863dd] - Updated dependencies [56664f5] - Updated dependencies [31cbe90] - Updated dependencies [90bbf25] - Updated dependencies [eb91eba] - Updated dependencies [42da73d] - Updated dependencies [643b7c7] - Updated dependencies [d0d5205] - Updated dependencies [1a15893] - Updated dependencies [b70e534] - Updated dependencies [2233a85] - Updated dependencies [62dd69a] - Updated dependencies [e15e679] - Updated dependencies [2ab1257] - Updated dependencies [4cc4fb7] - Updated dependencies [28d1eb7] - Updated dependencies [2c26040] - Updated dependencies [f758cec] - Updated dependencies [78f0be8] - Updated dependencies [35f7fb4] - Updated dependencies [a5302c7] - Updated dependencies [82397b6] - Updated dependencies [7084313] - Updated dependencies [0e043d8] - Updated dependencies [dadd1ad] - Updated dependencies [2f2e63c] - Updated dependencies [486d526] - Updated dependencies [89d7b35] - Updated dependencies [85ec26d] - Updated dependencies [f6476fc] - Updated dependencies [4ac12ef] - Updated dependencies [b88f5e8] - Updated dependencies [42cc219] - Updated dependencies [d7e0b42] - Updated dependencies [3510e4a] - Updated dependencies [aa4b90d] - Updated dependencies [54299ca] - Updated dependencies [3264516] - Updated dependencies [dc61def] - Updated dependencies [251e888] - Updated dependencies [183b4c4] - Updated dependencies [2fdb36e] - Updated dependencies [62159bd] - Updated dependencies [d48aad5] - Updated dependencies [20526f5] - Updated dependencies [c5eef1d] - Updated dependencies [e0f300b] - Updated dependencies [761a0ba] - Updated dependencies [be87153] - Updated dependencies [60f0dd8] - Updated dependencies [a87c5cd] - Updated dependencies [a47f338] - Updated dependencies [bee5ffe] - Updated dependencies [3172831] - Updated dependencies [939f579] - Updated dependencies [2598216] - Updated dependencies [2c7e62d] - Updated dependencies [eb7613c] - Updated dependencies [ecc9110] - Updated dependencies [f7bd4e2] - Updated dependencies [361bd5b] - Updated dependencies [1818998] - Updated dependencies [09ee21c] - Updated dependencies [f549a0d] - Updated dependencies [3fc2e48] - Updated dependencies [e8f435c] - Updated dependencies [41610f6] - @objectstack/spec@17.0.0-rc.6 - @objectstack/driver-sql@17.0.0-rc.6 - @objectstack/core@17.0.0-rc.6 ## 17.0.0-rc.5 ### Patch Changes - Updated dependencies [e8f8f6c] - Updated dependencies [7f713b6] - Updated dependencies [c960170] - Updated dependencies [def5919] - Updated dependencies [ce0cfe9] - Updated dependencies [1363084] - @objectstack/spec@17.0.0-rc.5 - @objectstack/core@17.0.0-rc.5 - @objectstack/driver-sql@17.0.0-rc.5 ## 17.0.0-rc.4 ### Patch Changes - 06ba036: feat(drivers): `@objectstack/driver-turso` 迁回本仓并公开发布，五个 driver 统一收进 `packages/drivers/` (#4645) `TursoDriver` 一直以 `extends SqlDriver` 的方式**跨仓库继承**本仓的类，自己却住在闭源的 `objectstack-ai/cloud`（`publishConfig: restricted`）。而本仓的 runtime 早就把 turso 当一等 公民——`http-dispatcher.ts` 里环境 provisioning 的偏好顺序第一位就是它，`POST /cloud/environments` 的 `driver` 参数示例是 `memory | turso`，`objectql/src/engine.ts` 还带着一段 turso 专属的瞬时 `fetch failed` 重试。开源侧的代码路径引用着一个自己仓里既测不到也 grep 不到的 driver，闭源侧则 在每次 pin bump 时追赶父类的重构。维护者裁定把核心迁回本仓、公开 Apache-2.0 发布。 **新包 `@objectstack/driver-turso`（`packages/drivers/driver-turso`，Apache-2.0，`access: public`）** 带着它在 cloud 的全部实现与测试落地：`TursoDriver`（local / replica / remote 三种传输模式）、 `RemoteTransport`（纯 `@libsql/client` 走 HTTP/WebSocket，无原生依赖，可跑 serverless/edge）、 驱动的 spec/Studio 元数据，以及 15 个测试文件 538 条断言——全部 hermetic，默认 CI 下不碰网络、 不要凭据（remote 面走包内的 sqlite stub）。 **留在 cloud（不随迁）**：按租户路由的 `multi-tenant.ts`（云产品差异化能力）及其 schema、 `vector-poc.test.ts`。因此本包的 barrel **不再导出** `createMultiTenantRouter` / `MultiTenantConfig` / `MultiTenantRouter`，也不导出多租户 schema——它们从来不是这个 driver 的 一部分，只是曾经同包而已。 **目录重组**：五个 `IDataDriver` 实现（`driver-memory` / `driver-mongodb` / `driver-sql` / `driver-sqlite-wasm` + 迁入的 `driver-turso`）现在都住在 `packages/drivers/`， `knowledge-*` 与 `embedder-*` 留在 `packages/plugins/`。四个存量包**内容零改动**，只有 `repository.directory` 随目录更新——包名、入口、导出面、行为全部不变，消费者无需改动任何 import。 这也把 turso 交给了本仓的仓库级守卫：`check:driver-conformance` 从磁盘发现 driver 包， 迁入即入矩阵（5 drivers × 5 case-sets）。它的 temporal 两格是真绿（local 与 remote 双面套件）， filter 组合语义与两个分页 case-set 记为 measured DEBT——remote 传输自带一套 `buildWhereSQL` 与 `LIMIT`/`OFFSET` 拼装，是独立实现，"继承所以没问题"正是这些共享套件存在来证伪的假设。 补齐工作跟踪在 #5590。 - Updated dependencies [9fe9c1d] - Updated dependencies [d4e0809] - Updated dependencies [f724f69] - Updated dependencies [28ad90e] - Updated dependencies [f8644c7] - Updated dependencies [306ca50] - Updated dependencies [978fed2] - Updated dependencies [cfc293f] - Updated dependencies [de70b42] - Updated dependencies [fb3d99b] - Updated dependencies [cdfbee2] - Updated dependencies [29c6c9d] - Updated dependencies [d21c001] - Updated dependencies [f1cc3a3] - Updated dependencies [ddc2527] - Updated dependencies [553a47f] - Updated dependencies [a3a884d] - Updated dependencies [cfed092] - Updated dependencies [2e284b2] - Updated dependencies [1b49eaf] - Updated dependencies [0161c7f] - Updated dependencies [e900015] - Updated dependencies [b5bdf48] - Updated dependencies [a019e52] - Updated dependencies [64fc6d5] - Updated dependencies [b746aa0] - Updated dependencies [947d4f9] - Updated dependencies [eaaf03c] - Updated dependencies [d17df80] - Updated dependencies [7d0e7b5] - Updated dependencies [6513c17] - Updated dependencies [c142ced] - Updated dependencies [eda599e] - Updated dependencies [c001422] - Updated dependencies [77022a9] - Updated dependencies [52760bf] - Updated dependencies [5543020] - Updated dependencies [880d343] - Updated dependencies [6e82972] - Updated dependencies [4615a18] - Updated dependencies [06ba036] - Updated dependencies [7f62706] - Updated dependencies [667fa44] - Updated dependencies [37e38d1] - Updated dependencies [0f17114] - Updated dependencies [1eb13a0] - Updated dependencies [c52e608] - Updated dependencies [4dfd002] - Updated dependencies [77be690] - Updated dependencies [811c30c] - Updated dependencies [b49ccfd] - Updated dependencies [c7406b0] - Updated dependencies [85d95e7] - Updated dependencies [168f60f] - Updated dependencies [244ca86] - Updated dependencies [546ab3c] - Updated dependencies [0b51bb6] - Updated dependencies [d9971d3] - Updated dependencies [eb3e650] - Updated dependencies [abeb375] - Updated dependencies [ef4efa8] - Updated dependencies [cbb6a5c] - Updated dependencies [795b6e1] - Updated dependencies [175d789] - Updated dependencies [55dbbba] - Updated dependencies [72c3c86] - Updated dependencies [7f1a635] - Updated dependencies [0f2fdcd] - Updated dependencies [8ffa8b9] - Updated dependencies [674ac99] - Updated dependencies [502564d] - Updated dependencies [471839d] - Updated dependencies [46365ab] - Updated dependencies [b508244] - Updated dependencies [594508e] - Updated dependencies [1c625ca] - Updated dependencies [71f205d] - Updated dependencies [414395b] - Updated dependencies [c5adfe1] - Updated dependencies [26e1029] - Updated dependencies [4addd9d] - Updated dependencies [108ba8d] - Updated dependencies [b4ad984] - Updated dependencies [a9f32df] - Updated dependencies [aeb9b27] - Updated dependencies [7d27da0] - Updated dependencies [089767f] - Updated dependencies [2ddba89] - Updated dependencies [e4c8b6c] - Updated dependencies [acb10f6] - Updated dependencies [1c3da1f] - Updated dependencies [a34fd2e] - Updated dependencies [889ae47] - Updated dependencies [4f4c3fb] - Updated dependencies [9c5abf4] - Updated dependencies [7adc841] - Updated dependencies [4845f85] - Updated dependencies [7b005b4] - Updated dependencies [94f7b6a] - Updated dependencies [5c94f83] - Updated dependencies [f98fa65] - Updated dependencies [73e576f] - Updated dependencies [c5a5996] - Updated dependencies [ae490ef] - Updated dependencies [f61c8cf] - Updated dependencies [e3ef52b] - Updated dependencies [07f1822] - Updated dependencies [04fab5e] - Updated dependencies [193cd5c] - Updated dependencies [5aae790] - Updated dependencies [07f1822] - Updated dependencies [efedd28] - Updated dependencies [5278e11] - Updated dependencies [23dba62] - Updated dependencies [ba98e26] - Updated dependencies [fc5f536] - Updated dependencies [f8cfbb4] - Updated dependencies [c89d18c] - Updated dependencies [acf34e3] - Updated dependencies [aac90a5] - Updated dependencies [1e6ab15] - Updated dependencies [c87ef70] - Updated dependencies [3cb0618] - Updated dependencies [32a0874] - Updated dependencies [7055c22] - Updated dependencies [785a748] - Updated dependencies [3af0354] - Updated dependencies [866ff16] - Updated dependencies [5a85e67] - Updated dependencies [c183a12] - Updated dependencies [8064b07] - Updated dependencies [4a56dbd] - Updated dependencies [06df4fa] - @objectstack/spec@17.0.0-rc.4 - @objectstack/driver-sql@17.0.0-rc.4 - @objectstack/core@17.0.0-rc.4 ## 17.0.0-rc.2 ### Patch Changes - 9b43ee2: test(drivers): the filter-logic standard now covers the backend it was counted without (#4405) `FILTER_LOGIC_CASES` (#3774) opens by calling itself the standard "the four independent FilterCondition backends are each checked against". Five backends exist. `driver-mongodb`'s `translateFilter` was missed, not excluded — an independent implementation whose `$and`/`$or`/`$not` translation shares no line of code with the SQL compiler or the in-memory matcher, and the only one whose target language cannot spell the standard directly: MongoDB has no document-level `$not` at all (the server answers `unknown top level operator: $not`), so a negation has to leave as `$nor`, and a branch's own keys have to stay in one document while `$and`/`$or` clauses are lifted beside them. That route was never checked against the shared cases. Both DEBT rows the #4363 gate recorded are now cleared, and `scripts/check-driver-conformance.mjs` reports `ok` for every cell of the matrix. **`driver-mongodb` runs the table twice, and the split is deliberate.** `mongodb-filter-logic-translation.test.ts` drives every shared case through `translateFilter` and evaluates the emitted MongoDB _document_ over the shared fixture — a pure function, no server, so it always runs. That matters here more than anywhere: `mongodb-memory-server` downloads a ~123 MB binary from fastdl.mongodb.org, and a defect only a downloadable binary can catch is a defect nobody catches on a restricted network. Its in-process reader is strict by construction — every shape it does not model throws instead of evaluating to true, a document-level `$not` included — and its own discrimination is pinned by cases that require a widened document to FAIL the case it widens, so "all green" cannot mean "the reader says yes to everything". `mongodb-filter-logic-conformance.test.ts` runs the same table against a real mongod and answers the one question the first half cannot — does MongoDB agree? — skipping cleanly (never silently) when the binary is unreachable. **`driver-sqlite-wasm` runs the table through its own engine.** It inherits `SqlDriver`'s filter compiler, so nothing is re-implemented; what the suite pins is that a nested `(… AND …) OR (… AND …)` survives the custom sql.js dialect that compiles, binds and marshals it — the same seam its temporal and pagination suites cover for their clauses. Tracked as DEBT rather than EXEMPT because "inherits, therefore fine" is the assumption those suites exist to disprove; the suite is what disproves it. **No divergence was found.** `translateFilter` answers all seventeen shared cases correctly today, `$not`-inside-a-branch and nested `$and`-inside-`$or` included, so no translation change ships here — what changes is that the next edit to it cannot quietly widen a filter. Both suites were verified to be discriminating rather than decorative by reintroducing the #3774 miscompile (propagating `or` into a branch's own contents): 15 of the mongodb translation suite's 26 tests fail, and 13 of the wasm suite's 18. `packages/spec`'s `filter-logic-conformance.ts` header now says five and names the fifth — a code comment; no schema, export or generated artifact moved. - 24915d2: fix(driver-sqlite-wasm): a `RETURNING` write is a write — persist it (#4518) A file-backed `sqlite-wasm` database flushed its schema at boot and then recorded nothing else. Every table was on disk; every row written after schema sync lived only in the WASM heap and died with the process. Reopening the file found a complete, empty database. **Cause.** The Knex dialect picked its execution branch from _"does this statement return rows"_ — and then marked the database dirty only on the other, row-less branch. `INSERT … RETURNING *` returns rows, so it executed on the row-returning branch and never set the flag. Since the `on-disconnect` flush is gated on the same flag, nothing rescued it afterwards either: **both** persist strategies dropped the write. ObjectQL writes through `RETURNING *` (it hands the stored row back to the caller), so this covered essentially all business data, along with `knex.raw('INSERT …')` and any other mutation arriving without a Knex `method`. **Fix.** "Does this statement change the database?" is now one exported predicate — `statementMutatesDatabase(sql, method)` — classifying by Knex method _and_ SQL text, applied at a single funnel after execution. It is independent of which branch executed the statement, so a mutation can no longer slip through by returning rows, by arriving without a method, or by taking a branch that forgot to say so. Transaction control still routes to `noteTransactionControl`, which keeps deferring flushes until the transaction closes (#1494), and mutating `PRAGMA` assignments (`auto_vacuum`, `user_version`) now count as writes too. **What changes for you.** Nothing to author. File-backed wasm SQLite now actually persists under `on-write` / `debounced:*`, and `disconnect()` is a real durability boundary: when it returns, committed data is on disk. This is what `bootStack({ databaseFile })` in `@objectstack/verify` needed to make `stop()` → second `bootStack` a genuine cold boot — the suspended-run restart proof ADR-0019 promises is now asserted end to end in the dogfood gate. Expect more disk writes than before on a file-backed dev database, because previously there were almost none. **One internal signature moved.** `WasmSqliteConnection.markDirty(method?)` is now `markDirty()`. It used to re-filter the caller's Knex method against its own allowlist, which made "did this mutate?" a decision taken in two places that could — and did — disagree. If you call it directly, drop the argument; the dialect classifies, the connection obeys. - Updated dependencies [430dcc2] - Updated dependencies [e6ac4bd] - Updated dependencies [80334c7] - Updated dependencies [ce5242c] - Updated dependencies [a7163ea] - Updated dependencies [e6e9379] - Updated dependencies [98877c9] - Updated dependencies [98877c9] - Updated dependencies [e6b1b69] - Updated dependencies [ad047d2] - Updated dependencies [2826d1e] - Updated dependencies [5a84d41] - Updated dependencies [20b1a9e] - Updated dependencies [203a449] - Updated dependencies [ac37fc6] - Updated dependencies [4820f55] - Updated dependencies [462d9c4] - Updated dependencies [7d21581] - Updated dependencies [f2445c9] - Updated dependencies [23338c3] - Updated dependencies [5b843fb] - Updated dependencies [b4487aa] - Updated dependencies [65ca83a] - Updated dependencies [67bf2e2] - Updated dependencies [c6d1cb4] - Updated dependencies [36030ff] - Updated dependencies [6117f7b] - Updated dependencies [e533b0b] - Updated dependencies [cdf4d9a] - Updated dependencies [aee1806] - Updated dependencies [c13350b] - Updated dependencies [c13350b] - Updated dependencies [9ca2d85] - Updated dependencies [c13350b] - Updated dependencies [891d345] - Updated dependencies [a52e2ef] - Updated dependencies [5293114] - Updated dependencies [20bc357] - Updated dependencies [5966c2a] - Updated dependencies [2382580] - Updated dependencies [d9fa683] - Updated dependencies [3c7bcc0] - Updated dependencies [4b6cac7] - Updated dependencies [7631964] - Updated dependencies [ac471a0] - Updated dependencies [60ae58e] - Updated dependencies [ce92674] - Updated dependencies [9f601e8] - Updated dependencies [51c5227] - Updated dependencies [a4a85c8] - Updated dependencies [07a4e26] - Updated dependencies [ec975f1] - Updated dependencies [eb4204b] - Updated dependencies [4f13be2] - Updated dependencies [61cc079] - Updated dependencies [0e96e46] - Updated dependencies [d52d4fe] - Updated dependencies [742cebb] - Updated dependencies [ce92674] - Updated dependencies [cf2c9b7] - Updated dependencies [833b512] - Updated dependencies [0f9faa2] - Updated dependencies [7cf42fe] - Updated dependencies [5966c2a] - Updated dependencies [f78dd83] - Updated dependencies [a2cd18a] - Updated dependencies [4638aaa] - Updated dependencies [0222d3c] - Updated dependencies [071d0dc] - Updated dependencies [0a936ea] - Updated dependencies [023c00b] - Updated dependencies [155507e] - Updated dependencies [7bba90b] - Updated dependencies [7e05d8e] - Updated dependencies [061406d] - Updated dependencies [c1f344b] - Updated dependencies [9c93465] - Updated dependencies [ebb209c] - Updated dependencies [63b33e6] - Updated dependencies [2a44c1d] - Updated dependencies [695cfbd] - Updated dependencies [7445149] - Updated dependencies [071d0dc] - Updated dependencies [0848bea] - Updated dependencies [d51bed2] - Updated dependencies [b8b3c64] - Updated dependencies [0c0fbd9] - Updated dependencies [f3141d8] - Updated dependencies [5a84d41] - Updated dependencies [fd3013a] - Updated dependencies [21676eb] - Updated dependencies [e336549] - Updated dependencies [d40f43a] - Updated dependencies [e5e7ee0] - Updated dependencies [a2ebea2] - Updated dependencies [800bdb0] - Updated dependencies [04f1182] - Updated dependencies [5647006] - Updated dependencies [38f7e4f] - Updated dependencies [c57f3cf] - Updated dependencies [97faca3] - Updated dependencies [ad5fe25] - Updated dependencies [ea90179] - Updated dependencies [ce92674] - Updated dependencies [5ef0b5b] - Updated dependencies [48fbacb] - Updated dependencies [355e951] - Updated dependencies [dadb43f] - @objectstack/spec@17.0.0-rc.2 - @objectstack/core@17.0.0-rc.2 - @objectstack/driver-sql@17.0.0-rc.2 ## 17.0.0-rc.1 ### Patch Changes - 0af50a3: fix(driver-sql,service-analytics): a bare-day upper bound covers the whole day on `Field.datetime` (#3777) A bare `YYYY-MM-DD` comparand anchors to midnight UTC. That is right for a lower bound and was silently wrong for an upper one: the dashboard date-range filter compiles `{ $gte: from, $lte: to }` with bare-day bounds, so on a `datetime` column every row created after 00:00 of the `to` day vanished from the result — no error, the chart renders, the numbers are just smaller. The default configuration hit it: the filter's default field is `created_at` (a system-injected `Field.datetime`) and 7 of the 13 presets end "today". The translation is operator-sensitive and half-open, applied at every comparison emitter: - `SqlDriver` (and `SqliteWasmDriver` by inheritance): `$lte`/`<=` with a bare-day comparand on a `datetime` column compiles to `< next-day-midnight` in the column's storage form; `$between [min, max]` with a bare-day max decomposes to `>= min AND < next-day(max)`. Both the plain and the legacy-repair (mixed-storage) column paths, both `where` spellings. - `NativeSQLStrategy`: `dateRange` windows and `lte` filters bind `< next-day` instead of an inclusive `BETWEEN`/`<=` when the bound is a bare day. - The `/analytics/sql` rendering and the dataset preview evaluator apply the same rule, so the echoed SQL and drafted numbers reproduce execution. `@objectstack/core` gains the shared primitive `nextUtcCalendarDay(value)`: the next calendar day of a valid bare `YYYY-MM-DD` (else `null` — instants, `Date`s and impossible days are never widened). Unchanged on purpose, per the semantics table on #3777: `date`/`time` columns (`<= day` is already whole-day-correct there), full-ISO/`Date` comparands (instant semantics), and `$gte`/`$gt`/`$lt` (midnight anchoring is correct for those). No authored metadata changes: a dashboard's existing `{ $gte, $lte }` window now simply includes its final day. - 2e836de: chore(packaging): CHANGELOG.md ships in every npm tarball (#4261) The AGENTS.md post-task checklist requires breaking changesets to carry their FROM → TO migration because "this text ships to consumers as `CHANGELOG.md` inside the npm package and is what an upgrading agent greps after the tombstone error." That delivery path was severed for 68 of the 69 publishable packages: npm packs `package.json` / `README*` / `LICENSE*` unconditionally but — unlike older npm versions — not `CHANGELOG.md`, and the canonical `"files": ["dist", "README.md"]` whitelist never named it. Measured on npm 10.9.7: `npm pack --dry-run` on `@objectstack/types` shipped 3 files while its 70KB `CHANGELOG.md` stayed behind. Only `@objectstack/spec` listed it explicitly. The tombstone-error scenario is precisely the one where the repo is out of reach — the upgrading agent has `node_modules` and nothing else — so the migration text has to ride in the tarball. Every publishable package now declares `CHANGELOG.md` in `files`, and the canonical whitelist is `["dist", "README.md", "CHANGELOG.md"]`. The other half is the gate: `check:published-files` gains a fifth invariant, COMPLETE — a whitelist that fails to cover `CHANGELOG.md` fails the always-required lint job, so the next package cannot silently sever the path again. `@objectstack/spec`'s per-package EXTRA_ENTRIES exemption dissolves into the canonical set. Consumer-visible change: one more file per install (the package's changelog, e.g. 70.8KB for `@objectstack/types`), and `grep -r "removed key" node_modules/@objectstack/*/CHANGELOG.md` now finds the migration it was promised. - 9881074: test(drivers): the "held to by a gate" claim now has a gate behind it (#4363) Three changesets — filter combinator semantics (#3774), temporal storage form (ADR-0053), deterministic paged reads (objectui#3106 / #4363) — each introduced a shared case-set in `@objectstack/spec/data` with some version of the claim that a future driver "is held to this by a gate rather than by remembering it". There was no gate. The case-sets are exports sitting in a package; nothing obliged a driver to import them. Measured on `main`, the matrix had three holes: `driver-sqlite-wasm` ran neither pagination case-set, and neither it nor `driver-mongodb` ran the filter-logic one — including a hole in the very case-set whose changeset made the claim. `scripts/check-driver-conformance.mjs` (`pnpm check:driver-conformance`, wired into lint.yml's required job) makes the hole the failure. Every (driver × case-set) cell is covered — some file under the package's `src/` imports _and drives_ the case-set's marker export — or carries a measured DEBT/EXEMPT entry, reconciled in both directions. A third direction, CLASSIFIED, holds the other end: a new `*-conformance.ts` fixture nobody classified fails the run rather than starting life uncovered, which is the direction that actually rots (#4203). It caught an unclassified `TEMPORAL_TIME_CASES` on its first run. `driver-sqlite-wasm` gains the pagination suite the gate found missing. It inherits `SqlDriver`'s ORDER BY construction, so nothing is re-implemented — what the suite pins is that the clause survives a different _engine_: this driver swaps knex's transport for a custom sql.js dialect that compiles, executes and marshals every row through its own path, and a dialect that reordered or dropped the trailing `ORDER BY id` would fail in no other suite. The two filter-logic holes are ledgered as DEBT rather than fixed here, with their reasons printed on every run and tracked in #4405. The mongodb row is the substantive one: `translateFilter` is an independent FilterCondition backend — the fifth, and the one #3774 never enrolled when it counted "the four". - 4384921: fix(spec,drivers): `bypassTenantAudit` becomes a declared driver option, and `findOne` stops accepting a bare id (#4311) Three drivers built with `tsup` and tested with `vitest`, so no `tsc` had ever read them. Onboarding them to the #4311 type-check ratchet surfaced 292 errors, and most of what looked like sloppy test fixtures was the types being wrong. **`DriverOptions.bypassTenantAudit` is now declared.** It has been live for a long time without being on the schema: `SqlDriver.auditMissingTenant` reads it to suppress the "tenant-scoped write without `tenantId`" warning, the driver's own warning text tells callers to set it, `ObjectQLEngine` sets it for system-context calls, and `service-settings` / `service-datasource` pass it on every global-scope write. Because the schema never had it, the driver read it through `(options as any)` and no caller was type-checked. The declaration states the limit as well: it silences a diagnostic and MUST NOT change which rows a write touches — suppressing an audit warning is not a permission. The same cast covered `timezone`, `tenantId`, `tenantIds` and `preserveAudit`, all long since declared. Those reads now go through `DriverOptions`, so the next undeclared option fails the build instead of hiding behind an existing cast. **`SqlDriver.findOne(object, id)` is removed.** An undeclared `typeof query === 'string' | 'number'` branch accepted a bare id. It was on no contract, nothing outside that package's own tests used it, and the other two drivers answered the identical call differently — `MemoryDriver` spreads the string into `{0:'t',1:'1'}`, `MongoDBDriver` reads `query.where` as `undefined` and returns an arbitrary row. It also bypassed the shared `findRows()` path, so it skipped field selection, temporal coercion, unknown-column recovery and the `singleRowLookup` ORDER BY decision. Spell an id lookup as the query it is: ```ts -(await driver.findOne("task", "t1")); +(await driver.findOne("task", { object: "task", where: { id: "t1" } })); ``` **`SqlDriver.initObjects` declares the `tenancy` it consumes.** Each object is fed to `computeAndRecordTenantField`, which reads `obj.tenancy` to pick the tenant column and to set or clear the sticky explicit-opt-out — but the parameter type listed only `{ name, fields }`, so a caller that spelled the key correctly was rejected while the driver read it anyway. `registerExternalObject` already had it. **`AnalyticsQueryInput` joins `AnalyticsQuery`.** `timezone` is `.default('UTC')`, so the parsed type requires it and an authored literal does not have it — the same two-tier split `QueryInput`/`QueryAST` already names on the query side. `InMemoryDriver.create`/`bulkCreate` also declare their `IDataDriver` return types; without them TS inferred the literal the method builds and every other column of the created row disappeared from the caller's view. One silent runtime bug fell out of the same pass: a driver test asked for `orderBy: [['id', 'asc']]`, the driver reads `item.field`, a tuple has none, and the sort never reached SQL. The tuple spelling appears nowhere else. - c53aa53: File-backed SQLite now runs `journal_mode = WAL` (#3941). `SqlDriver.connect()` set `auto_vacuum` and left the journal mode alone, so every ObjectStack SQLite database ran SQLite's built-in default — a rollback journal. That is the worst mode for the shape this platform actually has, which is **several processes on one file**: a dev server, `os migrate`, `os meta resync`, a test run. Measured, on the same file: | | rollback journal | WAL | | :--------------------------------------------- | :------------------------------------------------- | :---------------------------------------------------------------- | | writer while another process holds a read open | `SQLITE_BUSY` — committing needs an exclusive lock | proceeds | | idle attached connection visible to SQL | no — a lock lasts only as long as its transaction | yes (`locking_mode = EXCLUSIVE` + `BEGIN IMMEDIATE` reports busy) | The second row is why the `os migrate` occupancy check had to inspect file descriptors to see a live server at all (#3940): under a rollback journal there was nothing in the database to see. That signal stays — it names the process, which WAL's lock probe cannot — but the SQL probe is now authoritative for databases ObjectStack created rather than a fallback that was blind in practice. Concurrent _writers_ still serialize; SQLite allows one at a time in any mode. Journal mode is a persistent property of the file, so an existing database is converted in place on the next connect (a header change — no rows are touched) and stays converted. Two consequences to plan for: - `app.db-wal` / `app.db-shm` exist beside the database while a connection is attached, and `app.db-wal` can hold committed transactions. A clean shutdown checkpoints them away; a naive copy of `app.db` alone while a server runs does not. Use `sqlite3 app.db ".backup …"`. - **WAL does not work on network filesystems** (NFS/SMB). Opt out with `OS_DATABASE_SQLITE_JOURNAL_MODE=delete`, or per datasource with `sqliteJournalMode: 'delete'` in the driver config (which outranks the env var). Either form _applies_ `delete`, so it also converts a database that already adopted WAL back — skipping would have stranded it. Nothing here fails a boot, and nothing is assumed: `PRAGMA journal_mode = X` answers with the mode actually in force rather than raising on refusal, so the reply is read back; and because a filesystem can accept WAL and then fail the first read _through_ it, the mode is proven with a read and rolled back to `delete` if that fails — with a warning naming the file and the escape hatch. `synchronous` is untouched, so durability is exactly what it was. `:memory:` databases are left alone, as is `auto_vacuum = INCREMENTAL`, which keeps reclaiming under WAL (ADR-0057). `os db clean` now counts `-wal` / `-shm` as part of the database when it measures what a `VACUUM` reclaimed, so bytes that were sitting in the log do not read as a reclaim of zero. `@objectstack/driver-sqlite-wasm` deliberately stays out of WAL. Its live database is in the WASM heap and what reaches disk is a byte image it exports, so nothing reads the database across processes and the pragma buys it nothing — while still being a persistent header change in the operator's file. sql.js _accepts_ the pragma (its VFS is memory-backed), so this had to be declared rather than discovered. It also now parks a `-wal` left behind by an unclean native-driver exit rather than loading the image beside it: wasm SQLite cannot read that log, and leaving it next to a freshly rewritten image would let a later real SQLite replay frames that no longer belong to it. The warning names the file it parked and how to recover what was in it. - Updated dependencies [6a67d7a] - Updated dependencies [0ecc656] - Updated dependencies [06772eb] - Updated dependencies [270650f] - Updated dependencies [3aef718] - Updated dependencies [1ea6bce] - Updated dependencies [c1dcacd] - Updated dependencies [ad303ed] - Updated dependencies [32ccb23] - Updated dependencies [f5a4ef0] - Updated dependencies [2d3e255] - Updated dependencies [7d7521f] - Updated dependencies [5dc4d02] - Updated dependencies [05154a1] - Updated dependencies [9b6fe7c] - Updated dependencies [8c711fb] - Updated dependencies [09e4547] - Updated dependencies [91f4c78] - Updated dependencies [820eff9] - Updated dependencies [8d895ff] - Updated dependencies [f6472d7] - Updated dependencies [78caf51] - Updated dependencies [62a789b] - Updated dependencies [789ad63] - Updated dependencies [2af1988] - Updated dependencies [0af50a3] - Updated dependencies [2e836de] - Updated dependencies [12a19a8] - Updated dependencies [41dcda3] - Updated dependencies [42e3b01] - Updated dependencies [c8124e5] - Updated dependencies [39eb01b] - Updated dependencies [a1a4140] - Updated dependencies [217e2e6] - Updated dependencies [86a71d1] - Updated dependencies [d5c75e2] - Updated dependencies [03d26f7] - Updated dependencies [4384921] - Updated dependencies [3c628ce] - Updated dependencies [7cb922e] - Updated dependencies [1d22114] - Updated dependencies [b5f9397] - Updated dependencies [ed77493] - Updated dependencies [58a03d2] - Updated dependencies [dc530b4] - Updated dependencies [e59786e] - Updated dependencies [bcf1112] - Updated dependencies [9774b78] - Updated dependencies [6f98c2d] - Updated dependencies [b07d829] - Updated dependencies [a648e96] - Updated dependencies [a47ac06] - Updated dependencies [e4c61a7] - Updated dependencies [cc60165] - Updated dependencies [081aa6f] - Updated dependencies [91f4c78] - Updated dependencies [e8d0c21] - Updated dependencies [45dc446] - Updated dependencies [c1d44f7] - Updated dependencies [ab9fb5c] - Updated dependencies [f985b3f] - Updated dependencies [9a4932a] - Updated dependencies [f9fc874] - Updated dependencies [011b386] - Updated dependencies [7777e8f] - Updated dependencies [507b92a] - Updated dependencies [7309c81] - Updated dependencies [20bc1ec] - Updated dependencies [90c2b15] - Updated dependencies [33a5ff4] - Updated dependencies [9e01213] - Updated dependencies [42eeb7d] - Updated dependencies [01e124d] - Updated dependencies [7ce02eb] - Updated dependencies [a13827e] - Updated dependencies [7733604] - Updated dependencies [40e420f] - Updated dependencies [d13004a] - Updated dependencies [be7360c] - Updated dependencies [3fe0ff1] - Updated dependencies [5b47ab5] - Updated dependencies [b09d8d9] - Updated dependencies [b09d8d9] - Updated dependencies [8675db6] - Updated dependencies [b09d8d9] - Updated dependencies [3eb1b2b] - Updated dependencies [59b85c0] - Updated dependencies [6e357ed] - Updated dependencies [d6938bf] - Updated dependencies [31e0be9] - Updated dependencies [4bfd455] - Updated dependencies [ffd2ce2] - Updated dependencies [62f8017] - Updated dependencies [a831df1] - Updated dependencies [f752ee3] - Updated dependencies [a1b61e0] - Updated dependencies [cd6b9f2] - Updated dependencies [2cb6d3c] - Updated dependencies [af2a095] - Updated dependencies [ec796d5] - Updated dependencies [e87fea1] - Updated dependencies [c65e529] - Updated dependencies [3ca34c1] - Updated dependencies [239c3a3] - Updated dependencies [94a0bbc] - Updated dependencies [d6bfb3d] - Updated dependencies [a2266a6] - Updated dependencies [d25a0ec] - Updated dependencies [667b83e] - Updated dependencies [627b188] - Updated dependencies [8d4eae7] - Updated dependencies [857a6cf] - Updated dependencies [65a3a84] - Updated dependencies [ccd9397] - Updated dependencies [bca935b] - Updated dependencies [d92c72d] - Updated dependencies [c54c822] - Updated dependencies [8dcc0f5] - Updated dependencies [75b9e51] - Updated dependencies [0a2f233] - Updated dependencies [8621cdd] - Updated dependencies [c53aa53] - Updated dependencies [6f23667] - Updated dependencies [5d21a48] - Updated dependencies [19365b7] - Updated dependencies [b7ed26d] - Updated dependencies [b3a3d83] - Updated dependencies [7a55913] - Updated dependencies [35accbf] - Updated dependencies [6038de7] - Updated dependencies [eb95d97] - Updated dependencies [e4c2dc8] - Updated dependencies [1bd2795] - Updated dependencies [8186a70] - Updated dependencies [a329cca] - Updated dependencies [6eec18c] - Updated dependencies [4d7bebf] - Updated dependencies [821ac7a] - Updated dependencies [8f81731] - Updated dependencies [8b50cb3] - Updated dependencies [8c2db68] - Updated dependencies [22b5e54] - Updated dependencies [0166bd5] - Updated dependencies [9b702dc] - Updated dependencies [ab16331] - @objectstack/spec@17.0.0-rc.1 - @objectstack/driver-sql@17.0.0-rc.1 - @objectstack/core@17.0.0-rc.1 ## 17.0.0-rc.0 ### Patch Changes - Updated dependencies [50616d9] - Updated dependencies [08b5a3d] - Updated dependencies [d99aeb3] - Updated dependencies [4727eb8] - Updated dependencies [f63cd09] - Updated dependencies [fa3d0cf] - Updated dependencies [af5a224] - Updated dependencies [71f76e1] - Updated dependencies [37b1346] - Updated dependencies [99736a0] - Updated dependencies [fe67e34] - Updated dependencies [fdb4f50] - Updated dependencies [1bd5652] - Updated dependencies [14252d3] - Updated dependencies [7fb436c] - Updated dependencies [879ea13] - Updated dependencies [201b31f] - Updated dependencies [c7f4417] - Updated dependencies [e2616e0] - Updated dependencies [6fdc5c6] - Updated dependencies [8b9d71e] - Updated dependencies [33f5e23] - Updated dependencies [259af21] - Updated dependencies [587fc91] - Updated dependencies [1986594] - Updated dependencies [ad4af62] - Updated dependencies [d44dbfa] - Updated dependencies [474fe39] - Updated dependencies [0bc685a] - Updated dependencies [b949059] - Updated dependencies [be1c52c] - Updated dependencies [c5ff96d] - Updated dependencies [84e7be9] - Updated dependencies [a6c3f38] - Updated dependencies [debc23a] - Updated dependencies [0f8ad09] - Updated dependencies [8f9689f] - Updated dependencies [57a3bb3] - Updated dependencies [5f9a987] - Updated dependencies [db02d47] - Updated dependencies [0bfdf46] - Updated dependencies [376a061] - Updated dependencies [7c7e246] - Updated dependencies [f35cdc5] - Updated dependencies [9ea2bc5] - Updated dependencies [32d3800] - Updated dependencies [cf5e033] - Updated dependencies [c2d9098] - Updated dependencies [a227ed7] - Updated dependencies [9613396] - Updated dependencies [e47b342] - Updated dependencies [4ed7ed4] - Updated dependencies [2fa4ca1] - Updated dependencies [f5a2320] - Updated dependencies [deb538f] - Updated dependencies [5b89711] - Updated dependencies [0c8a22f] - Updated dependencies [763931e] - Updated dependencies [de9af8a] - Updated dependencies [c4df271] - Updated dependencies [a41ba5c] - Updated dependencies [189854c] - Updated dependencies [5d4de37] - Updated dependencies [0e3a226] - Updated dependencies [1d4756e] - Updated dependencies [720c5ad] - Updated dependencies [a8d1e24] - Updated dependencies [41642b0] - Updated dependencies [4cca74c] - Updated dependencies [88ef03e] - Updated dependencies [9e2caf3] - Updated dependencies [81ce41a] - Updated dependencies [85e1e4e] - Updated dependencies [dac6a08] - Updated dependencies [394b7a1] - Updated dependencies [677b591] - Updated dependencies [d77d1b7] - Updated dependencies [5b79a34] - Updated dependencies [c757854] - Updated dependencies [0045682] - Updated dependencies [2a5f04a] - Updated dependencies [4f740b0] - Updated dependencies [67452d1] - Updated dependencies [0fc6219] - Updated dependencies [605e190] - Updated dependencies [c6c59f1] - Updated dependencies [b0e78a8] - Updated dependencies [f31cc8d] - Updated dependencies [f343dc4] - Updated dependencies [8269e32] - Updated dependencies [74f7339] - Updated dependencies [a6c35a2] - Updated dependencies [c2f1002] - Updated dependencies [f163028] - Updated dependencies [f07808c] - Updated dependencies [7ffc3d3] - Updated dependencies [88346ba] - Updated dependencies [4631592] - Updated dependencies [32ff033] - Updated dependencies [5ac93d4] - Updated dependencies [93f267f] - Updated dependencies [0024abf] - Updated dependencies [acbf364] - Updated dependencies [7687f7b] - Updated dependencies [1659072] - Updated dependencies [abceb0d] - Updated dependencies [0c302a7] - Updated dependencies [6633337] - Updated dependencies [f00d8d4] - Updated dependencies [503be86] - Updated dependencies [647ec8b] - Updated dependencies [7457a09] - Updated dependencies [5f0852f] - Updated dependencies [cde1975] - Updated dependencies [0bc685a] - Updated dependencies [11949fc] - Updated dependencies [b098b0e] - Updated dependencies [4d00b13] - Updated dependencies [57bab76] - Updated dependencies [b90086a] - Updated dependencies [b95577a] - Updated dependencies [83c161f] - Updated dependencies [d8c4957] - Updated dependencies [f24cb83] - Updated dependencies [5dbbb92] - Updated dependencies [69f1dfd] - @objectstack/spec@17.0.0-rc.0 - @objectstack/driver-sql@17.0.0-rc.0 - @objectstack/core@17.0.0-rc.0 ## 16.1.0 ### Patch Changes - Updated dependencies [9e45b63] - Updated dependencies [b20201f] - @objectstack/spec@16.1.0 - @objectstack/core@16.1.0 - @objectstack/driver-sql@16.1.0 ## 16.0.0 ### Patch Changes - Updated dependencies [f972574] - Updated dependencies [6289ec3] - Updated dependencies [22013aa] - Updated dependencies [3ad3dd5] - Updated dependencies [8efa395] - Updated dependencies [3a18b60] - Updated dependencies [a8aa34c] - Updated dependencies [e057f42] - Updated dependencies [a3823b2] - Updated dependencies [43a3efb] - Updated dependencies [524696a] - Updated dependencies [bfa3c3f] - Updated dependencies [5e3301d] - Updated dependencies [dd9f223] - Updated dependencies [47d923c] - Updated dependencies [46e876c] - Updated dependencies [5f05de2] - Updated dependencies [021ba4c] - Updated dependencies [158aa14] - Updated dependencies [62a2117] - Updated dependencies [d2723e2] - Updated dependencies [fefcd54] - Updated dependencies [efbcfe1] - Updated dependencies [beaf2de] - Updated dependencies [369eb6e] - Updated dependencies [06ff734] - Updated dependencies [b659111] - Updated dependencies [5754a23] - Updated dependencies [6c270a6] - Updated dependencies [290e2f0] - Updated dependencies [668dd17] - Updated dependencies [8abf133] - Updated dependencies [e0859b1] - Updated dependencies [ce468c8] - Updated dependencies [04ecd4e] - Updated dependencies [4d5a892] - Updated dependencies [16cebeb] - Updated dependencies [86d30af] - Updated dependencies [8923843] - Updated dependencies [a2795f6] - Updated dependencies [f16b492] - Updated dependencies [4b6fde8] - Updated dependencies [2018df9] - Updated dependencies [fc5a3a2] - Updated dependencies [8ff9210] - @objectstack/spec@16.0.0 - @objectstack/core@16.0.0 - @objectstack/driver-sql@16.0.0 ## 16.0.0-rc.1 ### Patch Changes - Updated dependencies [6289ec3] - Updated dependencies [8efa395] - Updated dependencies [bfa3c3f] - Updated dependencies [62a2117] - Updated dependencies [06ff734] - @objectstack/spec@16.0.0-rc.1 - @objectstack/core@16.0.0-rc.1 - @objectstack/driver-sql@16.0.0-rc.1 ## 16.0.0-rc.0 ### Patch Changes - Updated dependencies [f972574] - Updated dependencies [22013aa] - Updated dependencies [3ad3dd5] - Updated dependencies [3a18b60] - Updated dependencies [a8aa34c] - Updated dependencies [e057f42] - Updated dependencies [a3823b2] - Updated dependencies [43a3efb] - Updated dependencies [524696a] - Updated dependencies [5e3301d] - Updated dependencies [dd9f223] - Updated dependencies [47d923c] - Updated dependencies [46e876c] - Updated dependencies [5f05de2] - Updated dependencies [021ba4c] - Updated dependencies [158aa14] - Updated dependencies [d2723e2] - Updated dependencies [fefcd54] - Updated dependencies [efbcfe1] - Updated dependencies [beaf2de] - Updated dependencies [369eb6e] - Updated dependencies [b659111] - Updated dependencies [5754a23] - Updated dependencies [6c270a6] - Updated dependencies [290e2f0] - Updated dependencies [668dd17] - Updated dependencies [8abf133] - Updated dependencies [e0859b1] - Updated dependencies [ce468c8] - Updated dependencies [04ecd4e] - Updated dependencies [4d5a892] - Updated dependencies [16cebeb] - Updated dependencies [86d30af] - Updated dependencies [8923843] - Updated dependencies [a2795f6] - Updated dependencies [f16b492] - Updated dependencies [4b6fde8] - Updated dependencies [2018df9] - Updated dependencies [fc5a3a2] - @objectstack/spec@16.0.0-rc.0 - @objectstack/core@16.0.0-rc.0 - @objectstack/driver-sql@16.0.0-rc.0 ## 15.1.1 ### Patch Changes - @objectstack/spec@15.1.1 - @objectstack/core@15.1.1 - @objectstack/driver-sql@15.1.1 ## 15.1.0 ### Patch Changes - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [3fe9df1] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [4109153] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [627f225] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - Updated dependencies [f531a26] - @objectstack/spec@15.1.0 - @objectstack/core@15.1.0 - @objectstack/driver-sql@15.1.0 ## 15.0.0 ### Patch Changes - Updated dependencies [28b7c28] - Updated dependencies [13749ec] - Updated dependencies [e62c233] - Updated dependencies [ed61c9b] - Updated dependencies [31d04d4] - @objectstack/spec@15.0.0 - @objectstack/core@15.0.0 - @objectstack/driver-sql@15.0.0 ## 14.8.0 ### Patch Changes - a199626: Harden the wasm SQLite driver (the dev fallback used when native `better-sqlite3` has an ABI mismatch) against three failure modes that spammed `pnpm dev`: - **Atomic flushes.** The database was persisted with a plain `writeFile` that truncates-then-streams in place, so a process killed mid-write (a dev-server restart, Ctrl-C, or crash — likely under `on-write`, where every dispatcher tick flushes) left a torn file that sql.js rejected on the next boot with `database disk image is malformed`. Flushes now write to a sibling temp file, `fsync`, and atomically `rename()` over the target, so a reader always sees a complete image. - **Corruption self-heal.** When an on-disk image is already corrupt, the driver now detects it at open (via `PRAGMA quick_check`), quarantines the bad file to `.corrupt-`, and boots on a fresh database — instead of failing every query forever with no path to recovery. - **`undefined` bindings.** A raw `undefined` binding made sql.js `throw` a plain string (`Wrong API use : tried to bind a value of an unknown type (undefined).`), which aborted the write and logged as a garbled char-indexed object. `undefined` is now coerced to SQL `NULL`, matching the driver's `useNullAsDefault` semantics and the native better-sqlite3 path. - Updated dependencies [16b4bf6] - Updated dependencies [16b4bf6] - Updated dependencies [10e8983] - Updated dependencies [84650c5] - Updated dependencies [607aaf4] - Updated dependencies [bb71321] - @objectstack/spec@14.8.0 - @objectstack/driver-sql@14.8.0 - @objectstack/core@14.8.0 ## 14.7.0 ### Patch Changes - Updated dependencies [d6a72eb] - @objectstack/spec@14.7.0 - @objectstack/core@14.7.0 - @objectstack/driver-sql@14.7.0 ## 14.6.0 ### Patch Changes - Updated dependencies [609cb13] - Updated dependencies [ce6d151] - @objectstack/spec@14.6.0 - @objectstack/driver-sql@14.6.0 - @objectstack/core@14.6.0 ## 14.5.0 ### Patch Changes - Updated dependencies [526805e] - Updated dependencies [d79ca07] - Updated dependencies [33ebd34] - Updated dependencies [c044f08] - Updated dependencies [01274eb] - @objectstack/spec@14.5.0 - @objectstack/core@14.5.0 - @objectstack/driver-sql@14.5.0 ## 14.4.0 ### Minor Changes - 7953832: ADR-0057 data lifecycle P1–P4 (#2786): platform-generated data is now bounded by construction. - **P1 — contract**: new `lifecycle` object property (`class: record | audit | telemetry | transient | event` + `retention` / `ttl` / `storage(rotation)` / `archive` / `reclaim`), enforced by the platform-owned **LifecycleService** registered by `ObjectQLPlugin` (default-on; disable via `OS_LIFECYCLE_DISABLED=1` or plugin `lifecycle.enabled=false`). The Reaper batch-deletes rows past `retention.maxAge` / `ttl` under a system context and reclaims space (`SqlDriver.reclaimSpace()` → SQLite `PRAGMA incremental_vacuum`). Non-`record` classes must declare a bounding policy (parse-time invariant + spec-liveness gate + dogfood storage-growth gate). - **P2 — rotation**: `storage: { strategy: 'rotation', shards, unit }` physically time-shards the table on SQLite — writes land in the current shard, reads go through a UNION-ALL view under the base name, expiry is an O(1) `DROP` of shards past the window. A legacy table is adopted as the first shard on upgrade. Other dialects fall back to an equivalent age-based reap. - **P3 — separation + Archiver**: registering a datasource named `telemetry` routes telemetry/event/audit objects to it (opt-in by existence; `transient` deliberately stays on the primary). Audit objects with `archive` declared get retain → archive → delete once the archive datasource exists; without it rows are retained, never dropped unarchived. - **P4 — governance**: new `lifecycle` settings namespace — runtime enable switch, per-object retention overrides (tenant-scoped: regulated tenants set years, dev sets days), per-object/per-class row quotas and growth alerts (observe-and-alert only). **Behavior change**: 11 platform objects now carry lifecycle declarations and their telemetry is bounded by default — `sys_activity` 14d (rotated), `sys_audit_log` 90d hot → archive (retained forever until an `archive` datasource is registered), `sys_metadata_audit` 365d → archive, `sys_job_run` / `sys_automation_run` / `sys_http_delivery` 30d, notification pipeline (`sys_notification`, delivery, receipt, inbox) 90d, `sys_device_code` expires_at + 1d. Extend windows per environment/tenant via the `lifecycle.retention_overrides` setting. ### Patch Changes - Updated dependencies [7953832] - Updated dependencies [82e745e] - Updated dependencies [f3035bd] - Updated dependencies [82c0d94] - Updated dependencies [7449476] - @objectstack/spec@14.4.0 - @objectstack/driver-sql@14.4.0 - @objectstack/core@14.4.0 ## 14.3.0 ### Patch Changes - Updated dependencies [2a71f48] - Updated dependencies [02f6af4] - Updated dependencies [c1064f1] - @objectstack/spec@14.3.0 - @objectstack/core@14.3.0 - @objectstack/driver-sql@14.3.0 ## 14.2.0 ### Patch Changes - Updated dependencies [ac8f029] - Updated dependencies [4ab9958] - @objectstack/spec@14.2.0 - @objectstack/core@14.2.0 - @objectstack/driver-sql@14.2.0 ## 14.1.0 ### Patch Changes - Updated dependencies [5a8465f] - Updated dependencies [7f8620b] - Updated dependencies [82ba3a6] - @objectstack/spec@14.1.0 - @objectstack/core@14.1.0 - @objectstack/driver-sql@14.1.0 ## 14.0.0 ### Patch Changes - Updated dependencies [0a8e685] - Updated dependencies [afa8115] - Updated dependencies [80f12ca] - Updated dependencies [e2fa074] - Updated dependencies [23c8668] - Updated dependencies [29f017d] - Updated dependencies [afa8115] - Updated dependencies [216fa9a] - Updated dependencies [6c22b12] - @objectstack/spec@14.0.0 - @objectstack/driver-sql@14.0.0 - @objectstack/core@14.0.0 ## 13.0.0 ### Patch Changes - Updated dependencies [6d83431] - Updated dependencies [01917c2] - Updated dependencies [b271691] - Updated dependencies [a5a1e41] - Updated dependencies [466adf6] - Updated dependencies [5be00c3] - Updated dependencies [466adf6] - Updated dependencies [2bee609] - Updated dependencies [fc7e7f7] - @objectstack/spec@13.0.0 - @objectstack/core@13.0.0 - @objectstack/driver-sql@13.0.0 ## 12.6.0 ### Patch Changes - Updated dependencies [6cebf22] - Updated dependencies [21420d9] - @objectstack/spec@12.6.0 - @objectstack/core@12.6.0 - @objectstack/driver-sql@12.6.0 ## 12.5.0 ### Patch Changes - Updated dependencies [8b3d363] - @objectstack/spec@12.5.0 - @objectstack/core@12.5.0 - @objectstack/driver-sql@12.5.0 ## 12.4.0 ### Patch Changes - Updated dependencies [60dc3ba] - @objectstack/spec@12.4.0 - @objectstack/core@12.4.0 - @objectstack/driver-sql@12.4.0 ## 12.3.0 ### Patch Changes - Updated dependencies [e7eceec] - @objectstack/spec@12.3.0 - @objectstack/core@12.3.0 - @objectstack/driver-sql@12.3.0 ## 12.2.0 ### Patch Changes - Updated dependencies [fce8ff4] - Updated dependencies [3962023] - Updated dependencies [2bb193d] - Updated dependencies [0426d27] - Updated dependencies [da807f7] - Updated dependencies [4f5b791] - @objectstack/spec@12.2.0 - @objectstack/core@12.2.0 - @objectstack/driver-sql@12.2.0 ## 12.1.0 ### Patch Changes - Updated dependencies [93e6d02] - @objectstack/spec@12.1.0 - @objectstack/core@12.1.0 - @objectstack/driver-sql@12.1.0 ## 12.0.0 ### Patch Changes - Updated dependencies [a8df396] - Updated dependencies [e695fe0] - Updated dependencies [7c09621] - Updated dependencies [7709db4] - Updated dependencies [2082109] - Updated dependencies [7c09621] - Updated dependencies [9860de4] - Updated dependencies [069c205] - @objectstack/spec@12.0.0 - @objectstack/core@12.0.0 - @objectstack/driver-sql@12.0.0 ## 11.10.0 ### Patch Changes - Updated dependencies [6a9397e] - Updated dependencies [c0efe5d] - @objectstack/spec@11.10.0 - @objectstack/core@11.10.0 - @objectstack/driver-sql@11.10.0 ## 11.9.0 ### Patch Changes - Updated dependencies [d3595d9] - Updated dependencies [8d87930] - @objectstack/spec@11.9.0 - @objectstack/driver-sql@11.9.0 - @objectstack/core@11.9.0 ## 11.8.0 ### Patch Changes - @objectstack/spec@11.8.0 - @objectstack/core@11.8.0 - @objectstack/driver-sql@11.8.0 ## 11.7.0 ### Patch Changes - Updated dependencies [5178906] - @objectstack/spec@11.7.0 - @objectstack/core@11.7.0 - @objectstack/driver-sql@11.7.0 ## 11.6.0 ### Patch Changes - @objectstack/spec@11.6.0 - @objectstack/core@11.6.0 - @objectstack/driver-sql@11.6.0 ## 11.5.0 ### Patch Changes - Updated dependencies [6ee4f04] - Updated dependencies [c1e3a65] - @objectstack/spec@11.5.0 - @objectstack/core@11.5.0 - @objectstack/driver-sql@11.5.0 ## 11.4.0 ### Patch Changes - Updated dependencies [5821c51] - Updated dependencies [a0fce3f] - @objectstack/spec@11.4.0 - @objectstack/core@11.4.0 - @objectstack/driver-sql@11.4.0 ## 11.3.0 ### Patch Changes - Updated dependencies [58e8e31] - Updated dependencies [b4a5df0] - @objectstack/spec@11.3.0 - @objectstack/core@11.3.0 - @objectstack/driver-sql@11.3.0 ## 11.2.0 ### Patch Changes - Updated dependencies [d0f4b13] - Updated dependencies [302bdab] - @objectstack/spec@11.2.0 - @objectstack/core@11.2.0 - @objectstack/driver-sql@11.2.0 ## 11.1.0 ### Patch Changes - Updated dependencies [ce0b4f6] - Updated dependencies [9ccfcd6] - Updated dependencies [ecf193f] - Updated dependencies [51bec81] - Updated dependencies [3e593a7] - Updated dependencies [63d5403] - @objectstack/core@11.1.0 - @objectstack/spec@11.1.0 - @objectstack/driver-sql@11.1.0 ## 11.0.0 ### Patch Changes - Updated dependencies [ab5718a] - Updated dependencies [4845c12] - Updated dependencies [c1a754a] - Updated dependencies [6fbe91f] - Updated dependencies [715d667] - Updated dependencies [5eef4cf] - Updated dependencies [72759e1] - Updated dependencies [6c4fbd9] - Updated dependencies [ef3ed67] - Updated dependencies [cd51229] - Updated dependencies [7697a0e] - Updated dependencies [e7e04f1] - Updated dependencies [cfd5ac4] - Updated dependencies [2be5c1f] - Updated dependencies [ad143ce] - Updated dependencies [5c4a8c8] - Updated dependencies [3afaeed] - Updated dependencies [8801c02] - Updated dependencies [3d04e06] - Updated dependencies [98a1535] - Updated dependencies [bc22a89] - Updated dependencies [8a7e9f1] - Updated dependencies [4a84c98] - Updated dependencies [c715d25] - Updated dependencies [aa33b02] - Updated dependencies [d980f0d] - Updated dependencies [a658523] - Updated dependencies [82ff91c] - Updated dependencies [638f472] - @objectstack/spec@11.0.0 - @objectstack/driver-sql@11.0.0 - @objectstack/core@11.0.0 ## 10.3.0 ### Patch Changes - Updated dependencies [5ba52b0] - @objectstack/driver-sql@10.3.0 - @objectstack/spec@10.3.0 - @objectstack/core@10.3.0 ## 10.2.0 ### Patch Changes - Updated dependencies [b496498] - @objectstack/spec@10.2.0 - @objectstack/core@10.2.0 - @objectstack/driver-sql@10.2.0 ## 10.1.0 ### Patch Changes - Updated dependencies [49da36e] - Updated dependencies [ac79f16] - Updated dependencies [517dad9] - @objectstack/spec@10.1.0 - @objectstack/driver-sql@10.1.0 - @objectstack/core@10.1.0 ## 10.0.0 ### Patch Changes - Updated dependencies [d7ff626] - Updated dependencies [92db3e5] - Updated dependencies [2a1b16b] - Updated dependencies [e16f2a8] - Updated dependencies [e411a82] - Updated dependencies [a581385] - Updated dependencies [d5f6d29] - Updated dependencies [220ce5b] - Updated dependencies [3efe334] - Updated dependencies [feead7e] - Updated dependencies [6ca20b3] - Updated dependencies [5f875fe] - Updated dependencies [b469950] - @objectstack/spec@10.0.0 - @objectstack/driver-sql@10.0.0 - @objectstack/core@10.0.0 ## 9.11.0 ### Patch Changes - Updated dependencies [e7f6539] - Updated dependencies [2365d07] - Updated dependencies [6595b53] - Updated dependencies [fa8964d] - Updated dependencies [36138c7] - Updated dependencies [a8e4f3b] - Updated dependencies [4c213c2] - Updated dependencies [2afb612] - @objectstack/spec@9.11.0 - @objectstack/driver-sql@9.11.0 - @objectstack/core@9.11.0 ## 9.10.0 ### Patch Changes - Updated dependencies [db02bd5] - Updated dependencies [641675d] - Updated dependencies [d9508d1] - Updated dependencies [1d352d3] - Updated dependencies [94e9040] - Updated dependencies [1f88fd9] - Updated dependencies [1f88fd9] - @objectstack/driver-sql@9.10.0 - @objectstack/spec@9.10.0 - @objectstack/core@9.10.0 ## 9.9.1 ### Patch Changes - @objectstack/spec@9.9.1 - @objectstack/core@9.9.1 - @objectstack/driver-sql@9.9.1 ## 9.9.0 ### Patch Changes - Updated dependencies [84249a4] - Updated dependencies [796f0d6] - Updated dependencies [11af299] - Updated dependencies [d5774b5] - Updated dependencies [bfa3102] - Updated dependencies [134043a] - Updated dependencies [90108e0] - Updated dependencies [9afeb2d] - Updated dependencies [6bec07e] - Updated dependencies [601cc11] - Updated dependencies [575448d] - @objectstack/spec@9.9.0 - @objectstack/driver-sql@9.9.0 - @objectstack/core@9.9.0 ## 9.8.0 ### Patch Changes - Updated dependencies [97c55b3] - Updated dependencies [1b1f490] - @objectstack/spec@9.8.0 - @objectstack/core@9.8.0 - @objectstack/driver-sql@9.8.0 ## 9.7.0 ### Patch Changes - @objectstack/spec@9.7.0 - @objectstack/core@9.7.0 - @objectstack/driver-sql@9.7.0 ## 9.6.0 ### Patch Changes - Updated dependencies [d1e930a] - Updated dependencies [71578f2] - Updated dependencies [5e3a301] - Updated dependencies [5db2742] - @objectstack/spec@9.6.0 - @objectstack/core@9.6.0 - @objectstack/driver-sql@9.6.0 ## 9.5.1 ### Patch Changes - Updated dependencies [ee72aae] - @objectstack/spec@9.5.1 - @objectstack/core@9.5.1 - @objectstack/driver-sql@9.5.1 ## 9.5.0 ### Patch Changes - Updated dependencies [d08551c] - Updated dependencies [707aeed] - Updated dependencies [7a103d4] - Updated dependencies [4b01250] - @objectstack/spec@9.5.0 - @objectstack/core@9.5.0 - @objectstack/driver-sql@9.5.0 ## 9.4.0 ### Patch Changes - Updated dependencies [060467a] - Updated dependencies [0856476] - Updated dependencies [b678d8c] - Updated dependencies [b678d8c] - Updated dependencies [b678d8c] - Updated dependencies [b678d8c] - @objectstack/spec@9.4.0 - @objectstack/driver-sql@9.4.0 - @objectstack/core@9.4.0 ## 9.3.0 ### Patch Changes - Updated dependencies [1ada658] - Updated dependencies [3219191] - Updated dependencies [290f631] - Updated dependencies [50b7b47] - Updated dependencies [f15d6f6] - Updated dependencies [f8684ea] - Updated dependencies [b4765be] - @objectstack/spec@9.3.0 - @objectstack/core@9.3.0 - @objectstack/driver-sql@9.3.0 ## 9.2.0 ### Patch Changes - Updated dependencies [2f57b75] - Updated dependencies [2f57b75] - @objectstack/spec@9.2.0 - @objectstack/core@9.2.0 - @objectstack/driver-sql@9.2.0 ## 9.1.0 ### Patch Changes - Updated dependencies [b9062c9] - @objectstack/spec@9.1.0 - @objectstack/core@9.1.0 - @objectstack/driver-sql@9.1.0 ## 9.0.1 ### Patch Changes - Updated dependencies [1817845] - @objectstack/spec@9.0.1 - @objectstack/core@9.0.1 - @objectstack/driver-sql@9.0.1 ## 9.0.0 ### Patch Changes - Updated dependencies [4c3f693] - Updated dependencies [0bf39f1] - Updated dependencies [f533f42] - Updated dependencies [1c83ee8] - @objectstack/spec@9.0.0 - @objectstack/core@9.0.0 - @objectstack/driver-sql@9.0.0 ## 8.0.1 ### Patch Changes - @objectstack/spec@8.0.1 - @objectstack/core@8.0.1 - @objectstack/driver-sql@8.0.1 ## 8.0.0 ### Patch Changes - Updated dependencies [a46c017] - Updated dependencies [b990b89] - Updated dependencies [99111ec] - Updated dependencies [d5a8161] - Updated dependencies [5cf1f1b] - Updated dependencies [9ef89d4] - Updated dependencies [1e8b680] - Updated dependencies [3306d2f] - Updated dependencies [c262301] - Updated dependencies [bc44195] - Updated dependencies [9e2e229] - @objectstack/spec@8.0.0 - @objectstack/driver-sql@8.0.0 - @objectstack/core@8.0.0 ## 7.9.0 ### Patch Changes - @objectstack/spec@7.9.0 - @objectstack/core@7.9.0 - @objectstack/driver-sql@7.9.0 ## 7.8.0 ### Patch Changes - Updated dependencies [06f2bbb] - Updated dependencies [36719db] - Updated dependencies [424ab26] - @objectstack/spec@7.8.0 - @objectstack/core@7.8.0 - @objectstack/driver-sql@7.8.0 ## 7.7.0 ### Patch Changes - Updated dependencies [b391955] - Updated dependencies [f06b64e] - Updated dependencies [023bf93] - Updated dependencies [764c747] - @objectstack/spec@7.7.0 - @objectstack/driver-sql@7.7.0 - @objectstack/core@7.7.0 ## 7.6.0 ### Patch Changes - be20aa4: Fix `COMMIT; - cannot commit - no transaction is active` under `persist: 'on-write'` (#1494). sql.js's `Database.export()` closes and reopens the database (it has no in-place serialize), which rolls back any open transaction. The fire-and-forget flush triggered after a write inside a Knex transaction (e.g. the autonumber sequence `BEGIN…COMMIT`) could therefore abort that transaction, leaving the trailing `COMMIT` to fail. The connection is now transaction-aware: `flush()` is deferred while a transaction is open and runs once it fully closes, so committed data is still persisted without aborting in-flight transactions. - Updated dependencies [955d4c8] - Updated dependencies [c4a4cbd] - Updated dependencies [b046ec2] - Updated dependencies [2170ad9] - Updated dependencies [02d6359] - Updated dependencies [7648242] - Updated dependencies [8fa1e7f] - Updated dependencies [55866f5] - Updated dependencies [60f9c45] - @objectstack/spec@7.6.0 - @objectstack/core@7.6.0 - @objectstack/driver-sql@7.6.0 ## 7.5.0 ### Patch Changes - @objectstack/spec@7.5.0 - @objectstack/core@7.5.0 - @objectstack/driver-sql@7.5.0 ## 7.4.1 ### Patch Changes - @objectstack/spec@7.4.1 - @objectstack/core@7.4.1 - @objectstack/driver-sql@7.4.1 ## 7.4.0 ### Patch Changes - Updated dependencies [23c7107] - Updated dependencies [c72daad] - Updated dependencies [f115182] - Updated dependencies [24c9013] - Updated dependencies [2faf9f2] - Updated dependencies [2faf9f2] - Updated dependencies [2faf9f2] - Updated dependencies [58b450b] - Updated dependencies [82eb6cf] - Updated dependencies [13d8653] - Updated dependencies [ff3d006] - Updated dependencies [5e831de] - @objectstack/spec@7.4.0 - @objectstack/driver-sql@7.4.0 - @objectstack/core@7.4.0 ## 7.3.0 ### Patch Changes - Updated dependencies [5e7c554] - @objectstack/spec@7.3.0 - @objectstack/core@7.3.0 - @objectstack/driver-sql@7.3.0 ## 7.2.1 ### Patch Changes - @objectstack/spec@7.2.1 - @objectstack/core@7.2.1 - @objectstack/driver-sql@7.2.1 ## 7.2.0 ### Patch Changes - @objectstack/spec@7.2.0 - @objectstack/core@7.2.0 - @objectstack/driver-sql@7.2.0 ## 7.1.0 ### Patch Changes - Updated dependencies [47a92f4] - @objectstack/spec@7.1.0 - @objectstack/core@7.1.0 - @objectstack/driver-sql@7.1.0 ## 7.0.0 ### Patch Changes - Updated dependencies [74470ad] - Updated dependencies [d29617e] - Updated dependencies [dc72172] - @objectstack/spec@7.0.0 - @objectstack/core@7.0.0 - @objectstack/driver-sql@7.0.0 ## 6.9.0 ### Patch Changes - @objectstack/spec@6.9.0 - @objectstack/core@6.9.0 - @objectstack/driver-sql@6.9.0 ## 6.8.1 ### Patch Changes - @objectstack/spec@6.8.1 - @objectstack/core@6.8.1 - @objectstack/driver-sql@6.8.1 ## 6.8.0 ### Patch Changes - Updated dependencies [6e88f77] - Updated dependencies [c8b9f57] - @objectstack/spec@6.8.0 - @objectstack/core@6.8.0 - @objectstack/driver-sql@6.8.0 ## 6.7.1 ### Patch Changes - @objectstack/spec@6.7.1 - @objectstack/core@6.7.1 - @objectstack/driver-sql@6.7.1 ## 6.7.0 ### Patch Changes - Updated dependencies [4944f3a] - Updated dependencies [430067b] - Updated dependencies [4f9e9d4] - @objectstack/driver-sql@6.7.0 - @objectstack/spec@6.7.0 - @objectstack/core@6.7.0 ## 6.6.0 ### Patch Changes - Updated dependencies [a49cfc2] - @objectstack/spec@6.6.0 - @objectstack/core@6.6.0 - @objectstack/driver-sql@6.6.0 ## 6.5.1 ### Patch Changes - @objectstack/spec@6.5.1 - @objectstack/core@6.5.1 - @objectstack/driver-sql@6.5.1 ## 6.5.0 ### Patch Changes - @objectstack/spec@6.5.0 - @objectstack/core@6.5.0 - @objectstack/driver-sql@6.5.0 ## 6.4.0 ### Patch Changes - Updated dependencies [f8651cc] - Updated dependencies [f8651cc] - Updated dependencies [0bf6f9a] - @objectstack/spec@6.4.0 - @objectstack/core@6.4.0 - @objectstack/driver-sql@6.4.0 ## 6.3.0 ### Patch Changes - @objectstack/spec@6.3.0 - @objectstack/core@6.3.0 - @objectstack/driver-sql@6.3.0 ## 6.2.0 ### Patch Changes - Updated dependencies [b4c74a9] - @objectstack/spec@6.2.0 - @objectstack/core@6.2.0 - @objectstack/driver-sql@6.2.0 ## 6.1.1 ### Patch Changes - 084ee2f: Sync `@objectstack/driver-sqlite-wasm` into the v6 fixed-version group so it releases in lockstep with the rest of the framework. The package was previously stuck at 5.2.1 on npm while every other `@objectstack/*` package moved to 6.0.0, which broke StackBlitz/WebContainer installs of templates that pin `^6.0.0`. - @objectstack/spec@6.1.1 - @objectstack/core@6.1.1 - @objectstack/driver-sql@6.1.1 ## 5.2.2 ### Patch Changes - Updated dependencies [93c0589] - @objectstack/spec@6.1.0 - @objectstack/core@6.1.0 - @objectstack/driver-sql@6.1.0 ## 5.2.1 ### Patch Changes - Updated dependencies [629a716] - Updated dependencies [dbc4f7d] - Updated dependencies [944f187] - @objectstack/spec@6.0.0 - @objectstack/core@6.0.0 - @objectstack/driver-sql@6.0.0