@functional-systems/lambdadb-cli 0.1.1-dev.6 → 0.1.1-dev.8

package/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## [Unreleased]
 
+### Added
+
+- 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 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

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
@@ -25,9 +25,30 @@ Installed CLIs do not update themselves. See
 [RELEASING.md](RELEASING.md#current-status) for release status and
 [VALIDATION.md](VALIDATION.md) for verification results and remaining limitations.
 
+### Homebrew
+
+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

@@ -252,6 +252,18 @@ live behavior, or exactly-once writes. A large result alone does not prove the
 service selected docsUrl; mock tests explicitly exercise that transport path.
 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`.
+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
+[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
 
 - LambdaDB TypeScript client `RELEASING.md` and `publish.yaml`: canonical channels,

package/VALIDATION.md

@@ -3,6 +3,70 @@
 Updated: 2026-09-19. Local contract tests use loopback servers and synthetic
 credentials. A separate authenticated development-project smoke is recorded below.
 
+## 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`
+from `packaging/homebrew/Formula/lambdadb-cli.rb` through a disposable local tap.
+The npm tarball SHA-256 was checked against the downloaded bytes, whose SHA-512
+matched registry integrity. The release lockfile resource is fixed to `c8d389f`.
+
+- Homebrew formula style, installation and `brew test` passed. The formula checks
+  CLI version, JSON configuration and mode 0600 without contacting a service.
+- A deliberately unusable `node` placed first on ambient PATH did not prevent
+  the installed wrapper from running; it selected Homebrew's Node 24.21.0.
+- All 35 CLI contracts from the stable release commit passed against the installed
+  Homebrew package. The harness uses the release commit's tests/examples so future
+  development-only features do not create false failures for an older stable CLI.
+- Simulated existing-formula and broken-executable-symlink cases both stopped the
+  harness before any installation or tap mutation.
+- The temporary CLI installation and tap were removed. The final harness disables
+  automatic dependency removal and cleanup, and does not persist developer mode.
+  Homebrew dependencies/caches remain: installing Node also upgraded the required
+  ca-certificates, openssl@3, readline, sqlite and xz packages during initial setup.
+  The existing fnm-managed Node and global npm CLI were not replaced.
+- Normal clean-install, lint, version/type checks, 59 source tests and 35 npm
+  installed-package contracts also passed. CLI runtime and SDK dependencies did
+  not change.
+
+macOS/Linux Homebrew CI is configured separately from runtime CI; current PR job
+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
 
 On 2026-09-19, [GitHub Release v0.1.0](https://github.com/lambdadb/lambdadb-cli/releases/tag/v0.1.0)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.1-dev.6",
+  "version": "0.1.1-dev.8",
   "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": "397fbfbe6977fbd4fbb3977eca73887a4899d564"
+  "gitHead": "225dec37f48dd5603af7fe777c1eb24d9041188c"
 }