@functional-systems/lambdadb-cli 0.1.2-dev.12 → 0.1.3-dev.13

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 ## [Unreleased]
 
+### Maintenance
+
+- Synchronize the 0.1.2 release history and start the 0.1.3 development line.
+- Prepare the Homebrew formula for verified stable 0.1.2 and record npm publication evidence.
+
+## [0.1.2] - 2026-10-04
+
 ### Fixed
 
 - Preserve fixed rerank status/provider/model/criteria/reason tokens when they

package/README.md

@@ -19,7 +19,7 @@ lambdadb --help
 ```
 
 For reproducible CI runs, pin an exact published version such as
-`@functional-systems/lambdadb-cli@0.1.1`. To try development builds, explicitly use
+`@functional-systems/lambdadb-cli@0.1.2`. To try development builds, explicitly use
 `@functional-systems/lambdadb-cli@dev`; this moving channel contains prereleases.
 Installed CLIs do not update themselves. See
 [RELEASING.md](RELEASING.md#current-status) for release status and

package/RELEASING.md

@@ -2,6 +2,28 @@
 
 ## Current status
 
+CLI 0.1.2 was published on 2026-10-04 from merged main commit
+`6628fe0ed1f405c88fbd91d591e5223d3250dd73` through
+[GitHub Release v0.1.2](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.2)
+and the [successful OIDC workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/37191188846).
+It pins SDK 0.7.0 and includes 49 fixed analyzer presets, optional per-query
+managed reranking and credential-safe fixed rerank metadata.
+
+Independent registry verification confirmed latest=0.1.2 and dev=0.1.2-dev.12.
+The published tarball is byte-identical to the reviewed, live-tested candidate.
+A clean registry consumer passed all 46 CLI contracts, version/help, SDK version,
+integrity, four registry signatures and three attestations. Decoded provenance
+identifies the release commit, tag and workflow. See
+[publication evidence](VALIDATION.md#cli-012-publication-2026-10-04).
+
+This post-release branch synchronizes main into develop with 0.1.3-dev.1 and
+prepares the verified 0.1.2 Homebrew formula. The public tap still provides 0.1.1
+until its separate formula PR is reviewed and merged. Publication and bounded
+development smoke do not establish production deployment, search quality,
+load/failure coverage or billing readiness.
+
+## CLI 0.1.1 publication
+
 CLI 0.1.1 was published on 2026-09-29 through
 [GitHub Release v0.1.1](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.1)
 and the [OIDC release workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/36557578359).
@@ -16,8 +38,8 @@ tarball is byte-identical to the tested final candidate; provenance identifies t
 release commit, tag and workflow. See [VALIDATION.md](VALIDATION.md#cli-011-publication).
 
 The post-release branch synchronizes main history into develop with `0.1.2-dev.1`
-and prepares the 0.1.1 Homebrew formula. The public tap update requires its separate
-review and merge. Facets still require a supporting server and newly built keyword
+and prepares the 0.1.1 Homebrew formula. The public tap was checked on 2026-10-04
+and matches that verified 0.1.1 formula; the 0.1.2 handoff follows publication. Facets still require a supporting server and newly built keyword
 indexes; publication does not migrate Collections or upgrade installed CLIs.
 
 ## Prior publication status
@@ -260,9 +282,11 @@ npm run test:live
 
 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,
-uses the new `chinese` analyzer, checks exact facet-only and document+facet buckets,
-and checks committed query/fetch contents with a maximum 300-second observation
-window per stage. Request timeouts and polling sleeps are capped to the remaining
+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 reranking with default criteria, null
+and custom criteria, including final/retrieval scores and status metadata.
+Request timeouts and polling sleeps are capped to the remaining
 budget, and responses at or after the deadline cannot pass. Process termination
 and event-loop scheduling may delay reporting. It reports elapsed time and
 matched-document counts; a timeout is a failed smoke, not proof that accepted
@@ -287,7 +311,8 @@ release, follow the [Homebrew maintainer guide](https://github.com/lambdadb/lamb
 update checksums, pass installation checks and prepare a tap PR. Tap publication
 is separate from this repository's npm workflow; no cross-repository write or
 automatic tap update is configured. The public
-[LambdaDB tap](https://github.com/lambdadb/homebrew-tap) provides stable `0.1.0`;
+[LambdaDB tap](https://github.com/lambdadb/homebrew-tap) provides stable `0.1.1`
+(verified on 2026-10-04);
 installation evidence is recorded in [VALIDATION.md](VALIDATION.md#homebrew-publication).
 
 ## Design references

package/VALIDATION.md

@@ -3,6 +3,121 @@
 Updated: 2026-10-04. Local contract tests use loopback servers and synthetic
 credentials. Authenticated development-project evidence is recorded separately.
 
+## CLI 0.1.2 publication (2026-10-04)
+
+[PR #15](https://github.com/lambdadb/lambdadb-cli/pull/15) merged as
+`6628fe0ed1f405c88fbd91d591e5223d3250dd73`. The annotated v0.1.2 tag points to
+that commit. [GitHub Release v0.1.2](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.2)
+triggered [OIDC publication](https://github.com/lambdadb/lambdadb-cli/actions/runs/37191188846),
+which passed Node 22/24 validation and exact-artifact tests on attempt 1.
+
+- Registry latest=0.1.2; dev=0.1.2-dev.12 remained unchanged.
+- Downloaded npm tarball is byte-identical to the reviewed final candidate and
+  merged-main pack. SHA-256:
+  `e63c2c0fd624e1d81c45c5ba24d641a11ee0ecdc60f063aba4268e06547761ea`.
+  Registry SHA-512 integrity:
+  `sha512-9l1WPN2vrX+JXRjuOh7Uz5DCVcaiV/YLpYKgZb7ORU1jphaAIx38VSWeiQitz0V2Nw/b1vTxfcXzvra6EAkaFg==`.
+- An isolated registry consumer passed all 46 installed CLI contracts and
+  version/help. Its lockfile integrity matched npm and SDK resolves to 0.7.0.
+  npm audit signatures verified four registry signatures and three attestations.
+- Decoded [provenance](https://registry.npmjs.org/-/npm/v1/attestations/@functional-systems%2flambdadb-cli@0.1.2)
+  matched the artifact digest, repository, release commit, refs/tags/v0.1.2,
+  publish.yaml and workflow run 37191188846. Verification retried registry reads
+  during propagation without another publication. Temporary consumer, archive
+  and cache were removed.
+- The candidate live evidence below applies to the identical published artifact;
+  no additional live run was performed. The earlier failed sample remains recorded.
+- Formula handoff pins this npm tarball and release lockfile SHA-256
+  `e2d12af262d13c3a23073d1313b183766bb40b5360abeb0d773b5100819dac65`.
+  Public-tap installation and upgrade remain pending its separate PR merge.
+
+These checks establish artifact publication and the recorded development sample;
+production deployment, search quality, load/failure coverage and billing readiness
+remain separate dependencies.
+
+## CLI 0.1.2 stable candidate (2026-10-04)
+
+Prepared release/0.1.2 from reviewed develop merge `aef74a3`, retaining SDK 0.7.0
+and all reviewed runtime/test changes. The release branch changes only version
+metadata, the dated changelog and release/validation documentation. Stable npm
+0.1.2 was absent when checked; latest remains 0.1.1. No stable tag, GitHub Release,
+package publication or main merge was performed during preparation.
+
+- npm ci, lint, typecheck, version checks and the explicit
+  RELEASE_TAG=v0.1.2 / RELEASE_PRERELEASE=false preflight passed on Node 24.15.0
+  with npm 11.12.1. All 71 source tests and 46 separately installed CLI tests passed.
+  The executable and lockfile agree on 0.1.2, and the installed SDK is 0.7.0.
+- A candidate tarball was installed into an isolated consumer with its own npm
+  cache. Its executable was selected via LAMBDADB_TEST_CLI for the authorized
+  development smoke using the existing .env.local target and in-memory mapping.
+  The successful run took 54.4 seconds: accepted writes at about 3 seconds,
+  committed query/fetch contents at about 52 seconds, exact facets and managed
+  reranking default/null/custom by about 54 seconds. All 49 preset metadata
+  checks passed. Cleanup returned HTTP 404 for
+  `cli-smoke-14b21fee-59e1-4898-9ef2-8a57db823de0`.
+- The first candidate live attempt failed after 53.2 seconds during query
+  observation with exit 3 and no HTTP status. The log does not distinguish a
+  transport timeout from another request failure; this is not a passing sample
+  or proof of a candidate defect. No runtime code was changed for the retry.
+  Cleanup was not confirmed by that run. An independent SDK get found its
+  test-owned collection still present; delete was accepted and a subsequent
+  get returned HTTP 404 for `cli-smoke-c42a987e-592a-4611-a8d7-04cf5b90ad15`.
+- Every live launcher checked .env.local's SHA-256 before/after execution. It
+  remained byte-for-byte unchanged. Temporary consumers, caches and initial
+  candidate tarballs were removed.
+- Only documentation was updated after the successful live run. The final
+  review tarball is rebuilt and checked again through the installed-package
+  suite; generated dist remains ignored. Candidate publication will be verified
+  independently after approval, rather than assuming dev provenance applies.
+- The public Homebrew tap was read and matches the verified 0.1.1 formula. Its
+  0.1.2 update waits for the stable npm artifact and immutable release lockfile.
+
+The live checks are bounded development evidence. Provider failure/load behavior,
+dense vector reranking, new-preset language quality, production deployment and
+billing readiness remain outside this verification. The PR must pass Node 22/24
+CI and receive review before main promotion. Tagging and publication are separate
+approved actions; synchronize main back into develop with 0.1.3-dev.1 afterward.
+
+## Published SDK 0.7.0 development consumer (2026-10-04)
+
+The [develop merge workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/37188862636)
+completed successfully and published
+[`0.1.2-dev.12`](https://www.npmjs.com/package/@functional-systems/lambdadb-cli/v/0.1.2-dev.12)
+from `aef74a3deeacb1e5d3f50856301562b58739fcdd` on attempt 1. Required Node
+22/24 validation and the exact publication artifact tests passed. Registry
+visibility was checked with reads while the automatic job completed; no second
+publication was attempted. At verification, dev=0.1.2-dev.12 and latest=0.1.1.
+
+- Downloaded tarball SHA-512 matched registry integrity and the clean consumer
+  lockfile. SDK dependency and the installed SDK both resolve exactly to 0.7.0.
+  Integrity: `sha512-AyGfP2ibeu/unYj5RvkkBO2WICkCMk6dp+4TauH0Da2xBsN6g3Nub7MmM/ZeiRE93wwV9r05IhXV2DyS28WY1A==`.
+- Registry/installed gitHead and decoded
+  [provenance](https://registry.npmjs.org/-/npm/v1/attestations/@functional-systems%2flambdadb-cli@0.1.2-dev.12)
+  agree on the merge commit, repository, develop ref, publish.yaml workflow and
+  run 37188862636; the provenance subject digest matches the downloaded artifact.
+- A fresh tarball consumer passed version/help and all 46 CLI contracts. Tests
+  came from an archived merge-source snapshot, with its expected package version
+  set to the generated published version. A separate registry-version consumer
+  with an isolated cache verified matching lockfile integrity and SDK version;
+  npm audit signatures verified four registry signatures and three attestations,
+  including the published CLI. The preliminary local-tarball audit verified only
+  the three registry dependencies, so the registry consumer verified the CLI too.
+- The published CLI's executable was selected through LAMBDADB_TEST_CLI for the
+  expanded authorized development smoke. All 49 preset metadata, ordinary/bulk
+  writes, full committed query/fetch contents, exact facets and managed reranking
+  default/null/custom checks passed in 81.9 seconds. Query contents appeared at
+  about 78 seconds; acceptance at about 2 seconds did not imply search readiness.
+- Cleanup was accepted and HTTP 404 confirmed for
+  `cli-smoke-5028c4c7-535c-4b29-8978-b3b805054d7d`. Temporary consumers, caches,
+  source snapshots and tarballs were removed. .env.local remained byte-for-byte
+  unchanged. The designated target and in-memory environment mapping are recorded
+  in the authenticated follow-up below.
+
+This establishes the published development artifact and a bounded sample on one
+development target. It does not establish stable publication, production feature
+deployment, language-specific search quality, load/failure coverage or billing
+readiness.
+
 ## SDK 0.7.0 local compatibility (2026-10-04)
 
 The checkout began clean on develop at `3903531`. npm now pins the released

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.2-dev.12",
+  "version": "0.1.3-dev.13",
   "private": false,
   "description": "Project-scoped LambdaDB command-line tools",
   "type": "module",
@@ -53,5 +53,5 @@
     "url": "https://github.com/lambdadb/lambdadb-cli/issues"
   },
   "license": "Apache-2.0",
-  "gitHead": "aef74a3deeacb1e5d3f50856301562b58739fcdd"
+  "gitHead": "aefbaeed9c799e76dd7a9501ecda6ab80dc6e958"
 }