@functional-systems/lambdadb-cli 0.1.0-dev.5 → 0.1.0

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 ## [Unreleased]
 
+## [0.1.0] - 2026-09-18
+
+### Added
+
+- First stable release of the project-scoped LambdaDB CLI: configure, doctor,
+  collection list/describe/create, JSONL ordinary/bulk import, query and ID fetch.
+- Explicit branch/tag/alias read targets, noninteractive commands, versioned JSON
+  output and documented exit codes, including partial and unknown write outcomes.
+- Reuse of TypeScript SDK 0.5.1 for authentication, transport, read retries,
+  pagination, bulk transfers and large response downloads.
+- Apache-2.0 licensing, installed-package contract tests, opt-in development-project
+  smoke tests and provenance-enabled npm publication.
+
 ### Fixed
 
 - Development publication verifies registry propagation for up to five minutes,

package/CONTRIBUTING.md

@@ -14,9 +14,6 @@ not LambdaDB collection branches or refs.
 4. Address review feedback and pass both required CI checks before merging.
 5. Delete the short-lived branch after verifying the merge.
 
-For the initial MVP, `feat/cli-mvp` targets the initial `develop` commit. The
-review includes the CLI implementation, tests, documentation and CI setup.
-
 ## Local and CI validation
 
 ```sh
@@ -67,8 +64,11 @@ commit so the shared branch ancestry is preserved. After promotion, synchronize
 `develop`, especially release-only changes or hotfixes. Include the next intended
 development base in that synchronization PR so develop retains a dev version.
 
-A separate `release/*` branch is optional when stabilization must proceed while
-new work continues on `develop`. It is not required for the initial release.
+A separate `release/*` branch can be created from reviewed develop and target
+main when preparing rc/stable metadata while develop retains its automatic dev
+base. The first stable release uses `release/0.1.0` for this reason. Do not merge
+stable package metadata into develop without setting its next dev base, because
+automatic development publication requires an `X.Y.Z-dev.N` version.
 
 The first npm bootstrap, rc/stable tags and GitHub Releases remain explicit
 release actions. Subsequent dev publication is automatic once enabled.

package/README.md

@@ -10,7 +10,7 @@ Requires Node.js 22.14 or newer and npm.
 
 ### Install from npm
 
-After the first development version is published, install the `dev` channel:
+The verified development build is available on the `dev` channel:
 
 ```sh
 npm install --global @functional-systems/lambdadb-cli@dev
@@ -18,6 +18,13 @@ lambdadb --version
 lambdadb --help
 ```
 
+This checkout prepares `0.1.0`. Once its GitHub Release and npm publication are
+complete, install the stable version with:
+
+```sh
+npm install --global @functional-systems/lambdadb-cli@0.1.0
+```
+
 The `dev` channel contains prerelease versions. For reproducible CI runs, pin an
 exact published version instead of the moving `dev` tag. See
 [RELEASING.md](RELEASING.md#current-status) for release preparation status and

package/RELEASING.md

@@ -2,6 +2,22 @@
 
 ## Current status
 
+The `release/0.1.0` candidate prepares the first stable version from reviewed
+`develop` commit `c8947e9`. It changes package/lock versions and release documents;
+CLI runtime, dependencies, tests and workflows match the verified development build.
+The promotion PR targets `main` directly so `develop` keeps its automatic dev base.
+Merge with a merge commit, then obtain authorization for `v0.1.0` and a non-prerelease
+GitHub Release. Main promotion alone does not publish npm. After publication,
+verify `latest=0.1.0`, provenance and a clean consumer installation. Synchronize
+main back to develop through a PR that also sets the next development base.
+Stable publication has not yet been performed.
+
+The ordinary develop merge published `0.1.0-dev.5` through OIDC in
+[one successful workflow attempt](https://github.com/lambdadb/lambdadb-cli/actions/runs/35344153978).
+The new verification logic handled approximately three minutes of registry
+propagation without repeating the write or rerunning the workflow. A fresh npm
+installation passed 35 CLI contracts, integrity and provenance/signature checks.
+
 Bootstrap and initial OIDC publication were completed on 2026-09-18:
 
 - `0.1.0-dev.1` was published publicly from reviewed develop as the manual bootstrap.

package/VALIDATION.md

@@ -3,6 +3,44 @@
 Date: 2026-09-18. Local contract tests use loopback servers and synthetic
 credentials. A separate authenticated development-project smoke is recorded below.
 
+## Stable 0.1.0 candidate
+
+Prepared `release/0.1.0` from reviewed develop commit
+`c8947e96308283ac593e712716f0732121bb1958`. Relative to that commit, only package
+versions and release documents change. Runtime source, dependencies, tests,
+examples and workflows are unchanged. Stable publication remains pending.
+
+On Node.js 24.15.0 / npm 11.12.1, a new worktree passed `npm ci`, lint, type
+checking, all 59 source tests, and 35 installed-package contract tests.
+`RELEASE_TAG=v0.1.0 RELEASE_PRERELEASE=false npm run check:version -- --release`
+passed and selected `latest`. CI results for the final commit belong to the
+promotion PR; local success is not a substitute for those required checks.
+
+A newly packed `0.1.0` tarball was installed into an isolated temporary consumer.
+Its executable reported `0.1.0` and was selected with `LAMBDADB_TEST_CLI` while
+running `node --test --test-reporter=tap test/live/cli.test.mjs`. The launcher used
+the maintainer's existing opt-in development settings and the in-memory variable
+mapping described below; it did not change or copy `.env.local` into the worktree.
+Target: `bench-recall` at
+`https://internal-dev-aws-apne2-v3-c05a2b5d492a.lambdadb.ai`.
+
+- Doctor and temporary collection creation passed within the first second.
+- Two ordinary documents with 3 MiB payloads each and one bulk document were
+  accepted at approximately 3 seconds. Acceptance did not imply search visibility.
+- Query and ID fetch on `branch:main` returned all three documents with exact
+  contents at approximately 69 seconds, without a pending-write overlay.
+- The live test passed in 69.6 seconds. Cleanup was accepted, then an independent
+  SDK get returned `ResourceNotFoundError` for
+  `cli-smoke-b854ef72-1448-42ae-8c9a-ce5c0441f104`, confirming its absence.
+- The source `.env.local` was byte-for-byte unchanged, and the temporary consumer
+  and tarball were removed. No key or signed URL is recorded here.
+
+Only documentation was updated after this live run; the final package is checked
+again with the installed-package contracts. This is development-service evidence
+for a bounded sample, not a latency/readiness guarantee or live tag/alias coverage.
+The stable npm artifact and release-event workflow remain unverified until the
+explicit publication and subsequent consumer/provenance checks.
+
 ## Public bootstrap and OIDC publication
 
 On 2026-09-18, the maintainer authorized the public bootstrap
@@ -57,11 +95,18 @@ A read-only probe used the actual npm CLI and new bounded-read flags to verify
 the existing `0.1.0-dev.4` manifest/tag. Only its preflight and accepted write were
 simulated; the probe performed no registry mutation.
 
-The changed publication path has not yet run on an actual develop merge; PR CI
-cannot publish. The next reviewed merge must verify the normal push-to-publication
-flow without a manual rerun. The LambdaDB live smoke was not rerun because CLI
-runtime source is unchanged; the prior development-project evidence below remains
-separate from npm checks.
+The [ordinary develop merge workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/35344153978)
+published `0.1.0-dev.5` from `c8947e96308283ac593e712716f0732121bb1958`
+on attempt 1. Node 22/24 validation and exact-artifact tests passed. Publication
+succeeded at 12:22:09 UTC; registry verification completed at 12:25:10 UTC with
+`result=published`. The approximately 181-second propagation delay required only
+read retries, with no manual rerun or repeated publication.
+
+A fresh npm `@dev` install with an isolated cache passed all 35 CLI contract tests,
+version/help, tarball/lockfile integrity checks and npm signature verification.
+Provenance identified the expected repository, develop ref, workflow, source
+commit and attempt 1. `dev=0.1.0-dev.5`; `latest` remained `0.1.0-dev.1`.
+These registry checks are separate from the development-service smoke below.
 
 ## Initial local automation validation (before publication)
 
@@ -255,7 +300,7 @@ deployment state of an individual LambdaDB endpoint.
   SIGINT/SIGTERM were checked on macOS; CI targets Linux.
 - No main promotion, explicit rc/stable publication or GitHub Release workflow
   execution. Public bootstrap and automatic dev/OIDC publication are verified
-  above; the new five-minute verification behavior awaits its first develop merge.
+  above, including the five-minute verification behavior on an ordinary develop merge.
 - Mock large-response tests cover SDK routing/credential separation at 1 MiB;
   the live sample verifies combined content above 6 MiB. Neither is an exhaustive
   memory/size stress test. Imports buffer a maximum 64 MiB source file

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.0-dev.5",
+  "version": "0.1.0",
   "private": false,
   "description": "Project-scoped LambdaDB command-line tools",
   "type": "module",
@@ -52,6 +52,5 @@
   "bugs": {
     "url": "https://github.com/lambdadb/lambdadb-cli/issues"
   },
-  "license": "Apache-2.0",
-  "gitHead": "c8947e96308283ac593e712716f0732121bb1958"
+  "license": "Apache-2.0"
 }