@functional-systems/lambdadb-cli 0.1.4-dev.17 → 0.1.4-dev.18

package/CHANGELOG.md

@@ -4,9 +4,15 @@
 
 ### Maintenance
 
+- Standardize feature descriptions to native embedding and native reranking;
+  preserve legacy wire fields, CLI behavior and historical references.
 - Synchronize the 0.1.3 release history and start the 0.1.4 development line.
 - Prepare the Homebrew formula for verified stable 0.1.3 and record publication evidence.
 
+### Dependencies
+
+- Pin `@functional-systems/lambdadb` and the npm lockfile to stable 0.8.1.
+
 ## [0.1.3] - 2026-10-06
 
 ### Added

package/CONTRIBUTING.md

@@ -147,7 +147,7 @@ The test fails before API calls when required settings are absent. It creates a
 random temporary collection, imports two 3 MiB documents plus a bulk document,
 accepts and verifies metadata for all 49 fixed analyzer presets, checks exact
 facet-only and document+facet buckets, and checks committed query/fetch contents
-with a maximum 300-second observation window per stage. It also checks managed
+with a maximum 300-second observation window per stage. It also checks native
 reranking with default criteria, null and custom criteria, including
 final/retrieval scores and status metadata.
 It creates two additional temporary Collections for native embedding-only and

package/DESIGN.md

@@ -129,6 +129,13 @@ fetch/query already delegate docsUrl to the SDK and preserve full results. Impor
 retains its existing bounded preflight and ordinary/bulk behavior; native
 embeddings use ordinary upsert. No changes to those flows were needed.
 
+## SDK 0.8.1 terminology update
+
+The runtime and lockfile now pin `@functional-systems/lambdadb@0.8.1`.
+Feature descriptions use native embedding and native reranking. The legacy
+`managedEmbedding` wire field and existing CLI behavior remain unchanged.
+The versioned contracts above retain their original source paths.
+
 ## Architecture
 
 ```text
@@ -171,7 +178,7 @@ helpers own presigned response downloads and authentication isolation.
 | No readiness wait or version-management commands | First use works through main; reads can target existing refs, without assuming lifecycle or indexing guarantees. |
 
 The public API documents ordinary upsert at 6 MB and bulk at 200 MB; CLI limits
-are deliberately smaller. Bulk is unsupported for managed embedding vector
+are deliberately smaller. Bulk is unsupported for native embedding vector
 fields. `consistentRead` only supports direct branches and excludes pending bulk
 imports. Collection statistics describe committed main, not selected ref readiness.
 

package/README.md

@@ -1,7 +1,7 @@
 # LambdaDB CLI
 
 A first, project-scoped CLI for developers, coding agents and CI. It uses
-`@functional-systems/lambdadb@0.8.0` for authentication, HTTP, read retries,
+`@functional-systems/lambdadb@0.8.1` for authentication, HTTP, read retries,
 pagination, bulk transfers and large response downloads.
 
 ## Install and run
@@ -235,7 +235,7 @@ backend `9072a1bc8925954369a887f558f1eaf387b7ea0e`. See the SDK 0.8.0
 [Bayesian contract](https://github.com/lambdadb/lambdadb-typescript-client/blob/v0.8.0/docs/bayesian-search.md)
 and [native embedding contract](https://github.com/lambdadb/lambdadb-typescript-client/blob/v0.8.0/docs/native-embeddings.md).
 
-### Managed reranking
+### Native reranking
 
 ```sh
 lambdadb query --collection cli-demo-docs --ref branch:main \
@@ -243,7 +243,8 @@ lambdadb query --collection cli-demo-docs --ref branch:main \
 ```
 
 Add optional `rerank` to a query file; omission/null keeps existing searches.
-This is a per-query setting, with LambdaDB-managed credentials and no Jev key.
+This is a per-query setting. The LambdaDB server supplies provider credentials;
+you do not supply a Jev key.
 Use `provider: "typesafe"`, `model: "jev-1.13.0"`, nonblank `queryText` (also for
 raw vectors, up to 8 KiB UTF-8), and 1–8 unique stored scalar text `fields`.
 Returned-field projection remains independent of these model inputs.
@@ -306,7 +307,7 @@ and 16,000,000 bytes; `--batch-bytes` allows up to 64,000,000. These are conserv
 CLI limits, not advertised server maxima. The SDK also enforces the bulk limit
 returned by the server. `--mode bulk` calls the existing SDK `bulkUpsertDocs`
 helper with the selected branch, including signed upload headers and finalization.
-Bulk is unsupported for managed embedding vector fields; use ordinary upsert.
+Bulk is unsupported for native embedding vector fields; use ordinary upsert.
 
 Import result fields are stable under `schemaVersion: 1`:
 
@@ -383,7 +384,7 @@ this SDK update. If migration is needed, deliberately create a new Collection an
 reinsert the source data; the CLI performs no automatic migration. Accepted imports
 and `consistentRead` are not proof of committed facet/index readiness.
 
-This source pins SDK 0.8.0. Existing CLI installations keep their packaged SDK
+This source pins SDK 0.8.1. Existing CLI installations keep their packaged SDK
 until a new CLI version is published and installed.
 
 ## Output, deadlines and exit codes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.4-dev.17",
+  "version": "0.1.4-dev.18",
   "private": false,
   "description": "Project-scoped LambdaDB command-line tools",
   "type": "module",
@@ -32,7 +32,7 @@
     "test:live": "npm run build && node --test test/live/*.test.mjs"
   },
   "dependencies": {
-    "@functional-systems/lambdadb": "0.8.0",
+    "@functional-systems/lambdadb": "0.8.1",
     "commander": "14.0.3"
   },
   "devDependencies": {
@@ -52,5 +52,5 @@
     "url": "https://github.com/lambdadb/lambdadb-cli/issues"
   },
   "license": "Apache-2.0",
-  "gitHead": "b2a52489a5893198466850e221a2cc4bcde79bd3"
+  "gitHead": "6e4c83681b49eac1c5c5f34f1f87f11aff78d84a"
 }