@lossless.org/nosqldb 10.7.1 → 10.7.3

package/dist_rust/rustdb_linux_amd64.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "6689710534aa0e5c913a0618bbb8d4a89894f326e817f251d4c832f145054ce3",
+  "binarySha256": "bbfa10bcaa43f0beda9e67ce1046a99de9500a810d6d104056541d21f51680e3",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:40:36.475Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:22:27.258Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "linux_amd64"
   }

package/dist_rust/rustdb_linux_amd64_musl.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "3af6fbdca2d70ed8ba9b54045ff7bce223187a42a172cc080baadb68034a7d6a",
+  "binarySha256": "e0edf0d9bf8937b71802fa115f3ecca7d5d438fa896e873349ac863962298a64",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:40:37.306Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:22:28.300Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "linux_amd64_musl"
   }

package/dist_rust/rustdb_linux_arm64.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "5f534b84c39d0013d4724a930ccae57842748d01d9f93f8a6c1c0ba416cb90ce",
+  "binarySha256": "5fa2b96061374c185072cf2943aee1c54b13c8a6977e19ac7e1107c1ba684eb6",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:40:36.898Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:22:27.716Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "linux_arm64"
   }

package/dist_rust/rustdb_linux_arm64_musl.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "5d82aca1acb518acd86b8b879a3a1c8b68625f0793d8e96b3ce9d5c65e9e7297",
+  "binarySha256": "9c78460d631be6354936553d68ec1932fc9ed8b749763248fe42efa3c977bdb8",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:40:37.725Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:22:28.746Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "linux_arm64_musl"
   }

package/dist_rust/rustdb_macos_amd64.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "2fd9b284e1b6a5a051a53645dc660e3e2accb4a15b25512072ed0196f1fe6c41",
+  "binarySha256": "49f654b34560f807c5413cdde1cbc809c04f598e05c4df3a8441a95a26eed6b3",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:25:27.522Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:05:09.004Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "macos_amd64"
   }

package/dist_rust/rustdb_macos_arm64.tsrust-build.json

@@ -1,13 +1,13 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "01ef95a56fe7b5944639eed54bdc964bd75c8251fbae17e003cb5b3afe543410",
+  "binarySha256": "4f2a3863d25386e79e33b6eb53a28cccaadba5282cb94af643097c09c724438d",
   "buildInfo": {
     "projectName": "@lossless.org/nosqldb",
-    "projectVersion": "10.7.1",
-    "gitCommit": "fbc2af3b9b2791db6f0896f6b990038e1f733722",
+    "projectVersion": "10.7.3",
+    "gitCommit": "a347f08fa79361afadb09c24d6aff50baffcc0cf",
     "gitDirty": false,
-    "builtAt": "2026-09-26T20:25:28.100Z",
-    "tsrustVersion": "1.15.1",
+    "builtAt": "2026-09-29T20:05:09.730Z",
+    "tsrustVersion": "2.0.0",
     "binary": "rustdb",
     "target": "macos_arm64"
   }

package/dist_ts/00_commitinfo_data.js

@@ -3,7 +3,7 @@
  */
 export const commitinfo = {
     name: '@lossless.org/nosqldb',
-    version: '10.7.1',
+    version: '10.7.3',
     description: 'A MongoDB-compatible embedded database server with wire protocol support, backed by a high-performance Rust engine.'
 };
 //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSx1QkFBdUI7SUFDN0IsT0FBTyxFQUFFLFFBQVE7SUFDakIsV0FBVyxFQUFFLHFIQUFxSDtDQUNuSSxDQUFBIn0=

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lossless.org/nosqldb",
-  "version": "10.7.1",
+  "version": "10.7.3",
   "private": false,
   "description": "A MongoDB-compatible embedded database server with wire protocol support, backed by a high-performance Rust engine.",
   "exports": {
@@ -15,9 +15,9 @@
     "@api.global/typedserver": "^8.4.6",
     "@design.estate/dees-element": "^2.2.4",
     "@git.zone/tsbuild": "^5.0.0",
-    "@git.zone/tsbundle": "^2.15.0",
-    "@git.zone/tsrust": "^1.15.1",
-    "@git.zone/tstest": "^6.3.0",
+    "@git.zone/tsbundle": "^3.1.0",
+    "@git.zone/tsrust": "^2.0.0",
+    "@git.zone/tstest": "^6.3.2",
     "@lossless.org/client": "0.1.1",
     "@types/node": "26.6.2",
     "mongodb": "^7.5.0"

package/readme.md

@@ -382,11 +382,17 @@ generation bindings are validated before and after the batch; mutation,
 durability, cancellation and close checks remain enforced. No lease or resolved
 authorization is reused across requests or asynchronous suspensions.
 
-Compound indexes combine leading equality fields with a range on the next field.
-For example, `{ serverId: 1, timestamp: 1 }` seeks directly into the requested
-server's time interval. Inclusive/exclusive endpoints, descending components,
-trailing fields and reverse pagination retain their normal semantics. The full
-predicate is still checked for every selected candidate.
+Compound indexes combine leading equality fields, if any, with a range on the
+next field. For example, `{ serverId: 1, timestamp: 1 }` seeks directly into the
+requested server's time interval. Inclusive/exclusive endpoints, descending
+components, trailing fields and reverse pagination retain their normal
+semantics. A range is built from `$gt`, `$gte`, `$lt` and `$lte`, and from
+`$ne: null` or a `$nin` list holding null, which read only the non-null keys as
+MongoDB's `[MinKey, undefined) ∪ (null, MaxKey]` bounds do: documents without
+the field or with an explicit null are not examined. Ranges are built only on
+complete, non-multikey indexes whose values all have a scalar order; other
+indexes are not narrowed. The full predicate is still checked for every
+selected candidate.
 
 For a query whose filter references only `_id` and whose projection is exactly
 `{ _id: 1 }`, the native primary index can supply the original BSON identity
@@ -586,13 +592,20 @@ unique index key wins, and the later writer is told at its own statement.
   finish. Writes to other documents are not delayed. A multi-document write
   outside a transaction stays all-or-nothing: it publishes nothing until it can
   publish every document.
-- After a transaction has been open for 60 seconds, its uncommitted writes no
-  longer block others: the next writer that needs one of its documents aborts
-  it, and it reports `NoSuchTransaction` (251) on its next statement or commit.
-  The limit is fixed at MongoDB's default `transactionLifetimeLimitSeconds` and
-  is not configurable. A transaction nobody contends with is not
-  aborted by age alone. Ending or expiring the session, and stopping the
-  server, release a transaction's writes as well.
+- A transaction open for longer than 60 seconds is aborted, as by MongoDB's
+  transaction reaper: its staged writes are discarded and its cursors, write
+  claims, transaction capacity and database gates are released. The server
+  checks idle sessions once a second; a statement still executing when the
+  limit passes is not interrupted, and the transaction aborts when that
+  statement has finished (MongoDB instead interrupts that statement with
+  `TransactionExceededLifetimeLimitSeconds` (290)). Its later statements, `commitTransaction` and
+  `abortTransaction` report `NoSuchTransaction` (251); statements and
+  `commitTransaction` carry `TransientTransactionError`, so `withTransaction`
+  retries from the start. Before that abort, the next writer that needs one of
+  its documents aborts it too rather than wait. The limit is fixed at
+  MongoDB's default `transactionLifetimeLimitSeconds` and is not configurable.
+  Ending or expiring the session, and stopping the server, release a
+  transaction's writes as well.
 - TTL expiry is not a contending writer. It leaves out the documents an open
   transaction has written, deletes the other expired documents of the index
   and moves past the held ones. A later pass over the index expires those
@@ -625,6 +638,10 @@ and revalidate under exclusive admission before any publication.
 
 Logical sessions survive socket disconnects. Expiry, `endSessions` and
 `killSessions` drain active work and release cursors and namespace gates.
+A `commitTransaction` or `abortTransaction` retried while its session is being
+ended still replays the transaction's stored outcome, so a committed
+transaction is never reported as aborted; a transaction that was still open
+when its session ended publishes nothing and reports `NoSuchTransaction` (251).
 Rejected new transaction envelopes do not consume session capacity or reset
 existing sessions. See the native resource budgets below.
 
@@ -1535,7 +1552,12 @@ NoSQLDB supports ascending and descending index keys with `name`, `unique`,
 `sparse`, `partialFilterExpression` and `expireAfterSeconds` options. It
 accepts `background` as a validated no-op and index version `v: 2`.
 Unsupported options, including `collation` and `hidden`, are rejected before
-any index in the request is created. Native maintenance expires eligible BSON
+any index in the request is created. A legacy `ns` field is accepted only when
+it names the target namespace. With `ignoreUnknownIndexOptions: true`,
+`createIndexes` removes the fields MongoDB 7 does not know as index options
+(and plugin-specific fields such as `weights` or `bits` on an ascending or
+descending key) before validation, as MongoDB does; options MongoDB knows but
+NoSQLDB does not implement are still rejected. Native maintenance expires eligible BSON
 dates and date arrays in bounded batches, preserving publication holds and
 active snapshots.
 
@@ -1744,6 +1766,23 @@ time-series collections, clustered indexes, encrypted fields, and all general
 view pipelines remain unsupported and are rejected before the database or
 namespace is created.
 
+`create` accepts an `idIndex` only when it describes the primary index every
+collection gets: key `{ _id: 1 }`, name `_id_`, optionally `v: 2` and an `ns`
+naming the new collection. Any other `idIndex` is `InvalidOptions` (72).
+
+**Importing from MongoDB.** `mongorestore` (MongoDB Database Tools 100.x)
+restores a `mongodump` of ordinary collections with its default flags: the
+documents, validators and supported indexes (unique, compound, sparse,
+partial and TTL). It sends this `idIndex` with every `create` and
+`createIndexes` with each index's `ns` and `ignoreUnknownIndexOptions: true`,
+and it builds several collections' indexes in parallel, which queue on the
+database (see "Database waits" below). Exclude the `admin` and `config`
+namespaces (`--nsExclude 'admin.*' --nsExclude 'config.*'`) and create users
+through NoSQLDB's authentication options. Collections or indexes that use
+unsupported features (collation, text, geospatial, hashed or wildcard
+indexes, capped or time-series collections) fail the restore with the
+refusing command's error instead of being restored differently.
+
 ### Collection Validators
 
 `create` and `collMod` accept MongoDB's `validator`, `validationLevel`
@@ -1904,6 +1943,9 @@ const estimated = await collection.estimatedDocumentCount();
 const names = await collection.distinct('name');
 ```
 
+The `count` command answers `n` as a 32-bit integer when the count fits and as
+a 64-bit integer above that, as MongoDB does.
+
 ---
 
 ## Wire Protocol Commands
@@ -2041,8 +2083,7 @@ fields:
   waits, before `find`, `count`, and `distinct` materialize documents, between
   documents in `insert` and `delete` batches, and immediately before a
   transaction commit is handed to storage; expiry fails with `MaxTimeMSExpired`
-  (code 50). Database-permit waits keep their fixed internal timeout, and a
-  single storage step or an in-progress `update` batch runs to completion
+  (code 50). A single storage step or an in-progress `update` batch runs to completion
   before the next check, so a write that expires after its first documents
   were published reports the expiry while those documents remain durable,
   exactly like an interrupted MongoDB batch. The official driver transmits a
@@ -2054,6 +2095,28 @@ fields:
   transaction. `getMore` rejects `maxTimeMS` with `BadValue` because NoSQLDB
   has no awaitData cursors, and a literal `maxCommitTimeMS` field is rejected
   with `InvalidOptions`.
+- **Database waits.** DDL (`create`, `createIndexes`, `drop`, `dropIndexes`,
+  `collMod`, `dropDatabase`, `renameCollection`, `$out`/`$merge`) holds its
+  database exclusively; other commands on that database wait for it, as they
+  wait for a MongoDB collection or database lock. A command outside a
+  transaction waits first in, first out for as long as it may run: until
+  `maxTimeMS` (`MaxTimeMSExpired`, code 50), until its client disconnects or
+  shuts down its sending side (the wait ends with `ClientDisconnect`, code
+  279, which a client that still reads receives before the connection closes)
+  or until the server shuts down (`InterruptedAtShutdown`, code 91). A DDL
+  command likewise waits for the open transactions on its database to commit
+  or abort, and every command on that database that arrives after the DDL
+  queues behind it, including reads of other collections. An open
+  transaction therefore delays DDL and the commands behind it at most until
+  the transaction lifetime limit (60 seconds, MongoDB's
+  `transactionLifetimeLimitSeconds`) aborts it.
+  A transaction statement that needs a further database keeps a fixed
+  five-second limit and then fails with `IllegalOperation` (code 20,
+  `EFENCE_BUSY: …`), so a transaction never waits without bound while it
+  holds its databases; like any failed statement, it aborts the transaction
+  and releases its databases. The service operations (export,
+  import, tenant and publication fencing) keep the same limit and report
+  `EFENCE_BUSY`.
 
 Callers may therefore rely on a successful NoSQLDB response as a durable,
 single-node acknowledgement. They must not read it as a replica-backed
@@ -2189,7 +2252,7 @@ The native distribution terms and qualified library requirements are recorded in
 extract and install these files independently of its compiled JavaScript bundle;
 NoSQLDB does not download engines at startup.
 
-Normal `tsrust` builds select only the current host's partition from `targetsByHost`. Releases use `tsrust matrix` to coordinate both partitions after the version commit exists, then publish only after native verification passes and every exact-commit binary has executed and passed strict provenance assembly.
+A plain `tsrust` build, as run by `pnpm build` and before `pnpm test`, compiles only the configured targets of the host's own architecture (its GNU and musl engines on Linux); `tsrust --configured-targets` builds the host's complete partition from `targetsByHost`. The development suite checks the packaged engines of the host architecture. Releases use `tsrust matrix` to coordinate both partitions after the version commit exists, then publish only after native verification passes and every exact-commit binary has executed and passed strict provenance assembly.
 
 The release coordinator needs Git, Node.js, pnpm and SSH access to the configured macOS builder. The local Linux amd64 builder needs `aarch64-linux-gnu-gcc`, `x86_64-linux-musl-gcc` and `aarch64-linux-musl-gcc` and a registered Linux arm64 `binfmt` interpreter. Linux file storage requires kernel 5.6 or newer with `openat2` enabled. Cross-architecture file qualification requires a full-system Linux guest or a native host. A linux-user executable probe does not qualify secure filesystem syscalls such as `openat2`. The built-package acceptance script `test/verify-alpine.mjs` exercises authenticated nested document persistence and restart through Node and Deno on Alpine; run it on both Linux architectures before publication. The Apple Silicon builder needs Rosetta. The matrix qualifies macOS first and then Linux; both partitions must pass before artifact assembly. Set these environment variables to authorized builders and their dedicated temporary roots:
 
@@ -2202,7 +2265,7 @@ export NOSQLDB_RELEASE_MACOS_TEMP_ROOT="/absolute/dedicated/nosqldb-release"
 
 1. Builds the TypeScript package and debug UI bundle from the version commit.
 2. Transfers an exact Git bundle into isolated local Linux and SSH macOS worker workspaces and installs each frozen lockfile.
-3. Runs the configured `release:verify-native` command on each worker: the full Rust workspace, TypeScript test checks, public API suite, and explicit-engine authentication/ownership/rehearsal tests through the worker's other packaged architecture. Tests use short, private disposable filesystem roots under `/var/tmp` on Linux and canonical `/tmp` on macOS. Linux builders must provide `/var/tmp` on a native-supported durable filesystem; tmpfs is rejected. Failures retain diagnostics and prevent assembly.
+3. Runs the configured `release:verify-native` command on each worker: the full Rust workspace, TypeScript test checks, a `tsrust --configured-targets` build of the worker's partition, the public API suite with the packaged-engine checks for both architectures, and explicit-engine authentication/ownership/rehearsal tests through the worker's other packaged architecture. Tests use short, private disposable filesystem roots under `/var/tmp` on Linux and canonical `/tmp` on macOS. Linux builders must provide `/var/tmp` on a native-supported durable filesystem; tmpfs is rejected. Failures retain diagnostics and prevent assembly.
 4. Builds and executes GNU and musl Linux amd64/arm64 plus macOS arm64/amd64 binaries on their assigned workers.
 5. Retrieves bounded artifact sets and transactionally publishes the complete provenance-checked matrix into `dist_rust/`.
 

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@lossless.org/nosqldb',
-  version: '10.7.1',
+  version: '10.7.3',
   description: 'A MongoDB-compatible embedded database server with wire protocol support, backed by a high-performance Rust engine.'
 }