@functional-systems/lambdadb-cli 0.1.1-dev.7 → 0.1.1-dev.9

package/CHANGELOG.md

@@ -7,13 +7,20 @@
 - A Homebrew formula for the published stable CLI, with a managed Node 24 runtime,
   checksummed npm/lockfile inputs and isolated production dependencies.
 - Local Homebrew installation checks, installed CLI contracts and macOS/Linux PR
-  validation. Public tap publication remains a separate pending step.
+  validation.
+- Public installation with `brew install lambdadb/tap/lambdadb-cli`, backed by the
+  LambdaDB Homebrew tap and remote installation checks.
 
 ### Maintenance
 
 - Synchronize the 0.1.0 release history into develop and start the 0.1.1 development
   line. Stable installs use npm's default channel; dev builds remain opt-in.
 
+### Documentation
+
+- Document the published stable npm channel, public Homebrew installation and
+  completed release verification on the default branch.
+
 ## [0.1.0] - 2026-09-19
 
 ### Added

package/README.md

@@ -6,10 +6,10 @@ pagination, bulk transfers and large response downloads.
 
 ## Install and run
 
-Requires Node.js 22.14 or newer and npm.
-
 ### Install from npm
 
+Requires Node.js 22.14 or newer and npm.
+
 Install the stable channel:
 
 ```sh
@@ -27,13 +27,28 @@ Installed CLIs do not update themselves. See
 
 ### Homebrew
 
-Homebrew support is being prepared for macOS and Linux. The formula and local
-installation checks are in [the maintainer guide](https://github.com/lambdadb/lambdadb-cli/tree/develop/packaging/homebrew#readme).
-The public tap is not published yet; use npm for installation today.
+On macOS or Linux with [Homebrew](https://brew.sh/) installed:
+
+```sh
+brew install lambdadb/tap/lambdadb-cli
+lambdadb --version
+lambdadb --help
+```
+
+The [LambdaDB tap](https://github.com/lambdadb/homebrew-tap) installs the stable CLI
+and its Node 24 runtime. No separate Node/npm setup is needed. Update with
+`brew update` followed by `brew upgrade lambdadb/tap/lambdadb-cli`; remove with
+`brew uninstall lambdadb/tap/lambdadb-cli`.
+
+If another installation provides `lambdadb`, check `command -v lambdadb` before
+switching package managers. Follow Homebrew's formula trust prompts without
+disabling trust checks. See the
+[maintainer guide](https://github.com/lambdadb/lambdadb-cli/tree/develop/packaging/homebrew#readme)
+for packaging and validation details.
 
 ### Build from source
 
-From a checkout of this repository:
+Requires Node.js 22.14 or newer and npm. From a checkout of this repository:
 
 ```sh
 npm ci

package/RELEASING.md

@@ -14,11 +14,12 @@ unqualified npm install passed all 35 CLI contracts, version/help, integrity,
 provenance and signature checks. Version/tag and attestation metadata propagated
 separately; verification used read retries without republishing.
 
-The post-release synchronization brings main history back into develop with
-`0.1.1-dev.1` as the next development base. Its promotion PR must preserve shared
-ancestry with a merge commit. Once merged, the normal develop push workflow
-publishes a numbered `0.1.1-dev.N` build on `dev`; it does not move `latest`.
-No separate stable release or tag is needed for this maintenance step.
+The post-release synchronization merged main history back into develop with
+`0.1.1-dev.1` as its development base. After the Homebrew documentation merge,
+[develop CI](https://github.com/lambdadb/lambdadb-cli/actions/runs/35434313586)
+published and verified `0.1.1-dev.8` from `225dec3` on 2026-09-19. Registry and
+provenance metadata identify that commit; `latest` remains `0.1.0`. Development
+builds do not require a separate stable release or tag.
 
 Bootstrap `0.1.0-dev.1` and the first OIDC development builds were verified on
 2026-09-18. The ordinary develop merge published `0.1.0-dev.5` in
@@ -254,13 +255,16 @@ Use existing known development tag/alias refs for additional live ref evidence.
 
 ## Homebrew handoff
 
-The stable formula is maintained in `packaging/homebrew/Formula/lambdadb-cli.rb`.
+The stable formula is maintained on develop in
+[`packaging/homebrew/Formula/lambdadb-cli.rb`](https://github.com/lambdadb/lambdadb-cli/blob/develop/packaging/homebrew/Formula/lambdadb-cli.rb).
 It consumes the verified npm artifact and the lockfile from its immutable release
 commit. Development publication does not update Homebrew. After each stable npm
 release, follow the [Homebrew maintainer guide](https://github.com/lambdadb/lambdadb-cli/tree/develop/packaging/homebrew#readme) to
 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 tap has not been published yet.
+automatic tap update is configured. The public
+[LambdaDB tap](https://github.com/lambdadb/homebrew-tap) provides stable `0.1.0`;
+installation evidence is recorded in [VALIDATION.md](VALIDATION.md#homebrew-publication).
 
 ## Design references
 

package/VALIDATION.md

@@ -3,6 +3,54 @@
 Updated: 2026-09-19. Local contract tests use loopback servers and synthetic
 credentials. A separate authenticated development-project smoke is recorded below.
 
+## Development publication after Homebrew documentation
+
+On 2026-09-19, the [develop push workflow](https://github.com/lambdadb/lambdadb-cli/actions/runs/35434313586)
+completed successfully for `225dec37f48dd5603af7fe777c1eb24d9041188c`, the merge of
+PR #8. Node 22/24 validation and tests of the exact publication tarball passed.
+The publish job accepted `0.1.1-dev.8`, retried registry reads during propagation,
+and finished with `result=published` without repeating the write.
+
+Subsequent read-only registry checks confirmed `dev=0.1.1-dev.8`,
+`latest=0.1.0`, and the package's `gitHead` matching the merge commit. Decoded
+provenance metadata identifies that same commit, `refs/heads/develop`,
+`.github/workflows/publish.yaml` and workflow attempt 1; its subject digest matches
+registry integrity. This metadata inspection did not repeat signature verification,
+a consumer installation or the LambdaDB live smoke.
+
+## Homebrew publication
+
+On 2026-09-19, the public
+[lambdadb/homebrew-tap](https://github.com/lambdadb/homebrew-tap) was initialized at
+`ca84485149d7915131df686b4c68868d47c00cd5`. Its CLI formula is byte-for-byte equal
+to the formula merged in CLI PR #7 (`3eefaaa`), selecting stable `0.1.0` and the
+release lockfile at `c8d389f`.
+
+- Local macOS 26.4 arm64 / Homebrew 6.0.17 verification used the tap's new harness
+  in both local and remote modes. Remote mode invoked
+  `brew install --formula lambdadb/tap/lambdadb-cli` with no existing tap or CLI,
+  exercising automatic public tap discovery and formula-specific trust.
+- Installation, downloaded formula equality, Homebrew style, `brew test`, version
+  `0.1.0`, JSON configuration with mode 0600, and the wrapper with an unusable
+  ambient Node all passed. No trust checks were disabled.
+- Test installations and taps were removed; existing taps, fnm Node and CLI
+  `.env.local` were preserved. Dependencies and caches remain installed.
+- [Tap CI](https://github.com/lambdadb/homebrew-tap/actions/runs/35433096180)
+  passed remote installation, style, smoke, runtime selection and cleanup on both
+  macOS 15 and Ubuntu 24.04 at the published tap commit.
+- Simulated existing CLI, broken prefix executable symlink and existing remote
+  tap cases stopped the new harness before mutations; invalid mode returned 2
+  without invoking Homebrew.
+- Tap main protection requires both installation checks, one approving review,
+  resolved conversations and an up-to-date base; force pushes and deletion are
+  disabled. Organization-level default-branch rules also apply.
+
+This publishes an installation path for the existing stable artifact, without a
+new npm release or another LambdaDB live-service smoke. Upgrade behavior between
+two distinct stable versions remains unverified until the next formula update.
+The earlier 35-contract Homebrew verification below used the same stable artifact;
+this tap publication ran the installation smoke checks rather than repeating it.
+
 ## Homebrew preparation
 
 On 2026-09-19, macOS 26.4 arm64 / Homebrew 6.0.17 installed stable `0.1.0`
@@ -29,9 +77,9 @@ matched registry integrity. The release lockfile resource is fixed to `c8d389f`.
   not change.
 
 macOS/Linux Homebrew CI is configured separately from runtime CI; current PR job
-results are the authority for hosted-runner coverage. No public tap repository
-was created and installation from a public tap remains unverified. No new npm
-version was published by this work. LambdaDB service smoke was not repeated for
+results are the authority for hosted-runner coverage. This initial preparation
+did not create the public tap; publication evidence is recorded above. No new npm
+version was published by the preparation. LambdaDB service smoke was not repeated for
 this packaging-only change; the stable candidate evidence below remains separate.
 
 ## Stable 0.1.0 publication

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.1-dev.7",
+  "version": "0.1.1-dev.9",
   "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": "3eefaaae29defacc80b1921aa31deace42f07afd"
+  "gitHead": "513af6e4d262edd380013c86d51a20aad16274d7"
 }