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

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 ## [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 tap publication remains a separate pending step.
+
 ### Maintenance
 
 - Synchronize the 0.1.0 release history into develop and start the 0.1.1 development

package/README.md

@@ -25,6 +25,12 @@ 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
+
+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.
+
 ### Build from source
 
 From a checkout of this repository:

package/RELEASING.md

@@ -252,6 +252,16 @@ 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 tap has not been published yet.
+
 ## Design references
 
 - LambdaDB TypeScript client `RELEASING.md` and `publish.yaml`: canonical channels,

package/VALIDATION.md

@@ -3,6 +3,37 @@
 Updated: 2026-09-19. Local contract tests use loopback servers and synthetic
 credentials. A separate authenticated development-project smoke is recorded below.
 
+## 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. 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
+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.7",
   "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": "3eefaaae29defacc80b1921aa31deace42f07afd"
 }