@functional-systems/lambdadb-mcp 0.1.2-dev.9 → 0.1.3-dev.10

package/CHANGELOG.md

@@ -2,19 +2,21 @@
 
 ## Unreleased
 
+## [0.1.2] - 2026-10-04
+
 - Pin the LambdaDB TypeScript SDK to 0.7.0 and expose all 49 fixed lowercase
   analyzer presets in collection-tool guidance; preserve analyzer serialization.
 - Add optional per-query managed reranking to the MCP schema and SDK request path,
   preserving omission/null, distinct sizes, custom criteria, envelope scores and
   status metadata, including document downloads. Retain SDK validation and errors.
 - Extend local and installed-package contracts for analyzer expansion and reranking;
-  update the opt-in live analyzer check without claiming live feature verification.
+  update the opt-in live analyzer check to cover all 49 names.
 - Add a separate opt-in managed-reranking live suite for real default/custom
   inference, empty candidates, omitted/null behavior and docsUrl envelope
   preservation, with owned-resource cleanup and no fixed relevance expectations.
 - Native SDK usage is unchanged; no Qdrant mapping exists in this server. Supporting
-  backend deployment/model availability remains required. No package is published
-  and existing MCP installations require a separately released update.
+  backend deployment/model availability remains required; existing MCP installations
+  require a version containing these changes.
 
 ## [0.1.1] - 2026-09-29
 

package/README.md

@@ -14,21 +14,23 @@ MCP server for LambdaDB using the official TypeScript MCP SDK and the official L
 Package: `@functional-systems/lambdadb-mcp`. Executable: `lambdadb-mcp`.
 Requires Node.js >=22.14.0; CI tests the minimum and current Node 22/24 LTS.
 
-The stable package is available on npm. As verified on 2026-09-29 (KST),
-`latest` resolves to `0.1.1` and `dev` to `0.1.1-dev.7`. Use an exact version for
+The stable package is available on npm. As verified on 2026-10-04 (KST),
+`latest` resolves to `0.1.2` and `dev` to `0.1.2-dev.9`. Use an exact version for
 reproducibility or the default stable channel for initial setup. See
 [release status and policy](RELEASING.md).
 
-[MCP 0.1.1](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.1) is published
-with SDK 0.6.0, keyword facets, match-all queries, and 16 text analyzers. Develop
-starts the next `0.1.2-dev.1` base; check npm for the current published dev version.
+[MCP 0.1.2](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.2) is the
+published stable release with SDK 0.7.0, 49 fixed text analyzer presets and optional
+managed reranking. This synchronization starts the next `0.1.3-dev.1` source base;
+check npm for the current published dev version. Use the exact stable version
+`0.1.2` for reproducible installed execution.
 Existing installations need an MCP version containing these changes; upgrading
 the SDK separately does not update them.
 
 ```sh
 npx --yes @functional-systems/lambdadb-mcp
 # Pin the stable release:
-npx --yes @functional-systems/lambdadb-mcp@0.1.1
+npx --yes @functional-systems/lambdadb-mcp@0.1.2
 # Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp

package/RELEASING.md

@@ -1,6 +1,35 @@
 # Releasing LambdaDB MCP
 
-## Current stable release: 0.1.1 (2026-09-29 KST)
+## Current stable release: 0.1.2 (2026-10-04 KST)
+
+[v0.1.2](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.2) tags main
+commit `627ffbb3161bc3d41d5f2a5f2a0f5289fd73de3f`, which merged
+[release PR #12](https://github.com/lambdadb/lambdadb-mcp/pull/12) with preserved
+ancestry. The [release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/37191117220)
+passed Node 22.14.0 / 22 / 24 validation and published its exact tested artifact
+with OIDC and provenance. Registry snapshot: `latest=0.1.2`, `dev=0.1.2-dev.9`.
+A downloaded stable tarball matched registry integrity, source commit and SDK
+0.7.0 and passed 31 clean-consumer stdio tests. Provenance statement repository,
+workflow, tag, source commit and subject digest matched the publication.
+
+SDK 0.7.0 adds 49 fixed text analyzer presets and optional per-query managed
+reranking. Read-only defaults and explicit write opt-in remain. See
+`docs/validation/2026-10-04-0.1.2.md` for separate candidate, authorized
+source-build live, published dev and published stable evidence. Do not repeat the
+0.1.2 publication or move its tag.
+
+This synchronization brings main back into develop with the next base
+`0.1.3-dev.1`. Review it into develop using a merge commit to preserve ancestry.
+Eligible develop merges may publish a new dev version while `latest` stays on
+0.1.2. Do not merge stable version metadata directly into develop.
+
+Both live suites require explicit designation of a development project. Reranking
+also requires managed inference opt-in; no Jev API key is required. Live contract
+checks do not establish production deployment, search quality, load/failure
+coverage or billing readiness. Supporting backend deployment/model availability
+and keyword-index requirements remain; existing collections/indexes are not migrated.
+
+## Previous stable release: 0.1.1 (2026-09-29 KST)
 
 [v0.1.1](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.1) tags main
 commit `40a8afc25bb93fb14d03d23e3ab38aa1924cf060`, which merged the reviewed release
@@ -14,10 +43,9 @@ See `docs/validation/2026-09-29-0.1.1.md` in this source for separate candidate,
 development-service, and published-package evidence. Do not repeat the 0.1.1
 publication or move its tag.
 
-This synchronization brings main back into develop with the next base
-`0.1.2-dev.1`. Review it into develop using a merge commit to preserve ancestry.
-Eligible develop merges may publish a new dev version while `latest` stays on
-0.1.1. Do not merge stable version metadata directly into develop.
+The 0.1.1 synchronization is complete: main was brought back into develop with
+the `0.1.2-dev.1` base through PR #10. Eligible develop merges publish dev versions
+while leaving `latest` on 0.1.1 until an explicitly published stable release.
 Facets need a supporting server and newly built keyword indexes; this release
 does not migrate existing Collections or indexes.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.2-dev.9",
+  "version": "0.1.3-dev.10",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -61,5 +61,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "99896e0279fa7610358e9abafc032dd507b10f40"
+  "gitHead": "df4be52ea47726f4d3d82a99b3ee2a755139c1f9"
 }