Prepare base-bash-libs for Homebrew core packaging

[codeforester]

Context

If Base is ever accepted into Homebrew/core under a non-conflicting formula name such as basefoundry, the reusable Bash library package should also be available from Homebrew/core. Base should not require users to tap or trust basefoundry/base just to resolve its runtime Bash library dependency.

The intended user-facing path is:

brew install basefoundry

That install should automatically install base-bash-libs as a Homebrew dependency from official Homebrew sources.

Desired outcome

• Submit or prepare base-bash-libs as a Homebrew/core formula.
• Keep the formula name base-bash-libs unless Homebrew maintainers require a different name.
• Ensure the future basefoundry Homebrew/core formula can declare depends_on "base-bash-libs".
• Avoid requiring brew trust basefoundry/base for the core install path.
• Keep the current tap formula available until the core path exists and migration guidance is ready.

Acceptance criteria

• base-bash-libs has a Homebrew/core-ready formula shape, license metadata, test block, and stable release URL.
• brew audit --new --formula base-bash-libs issues are resolved or explicitly understood.
• The Base core packaging plan documents basefoundry depending on base-bash-libs.
• User docs distinguish the current tap path from the future core path.

Notes

This is a Future milestone item. It should be picked up only when we are actively pursuing Homebrew/core packaging for Base.

[codeforester]

Homebrew/core acceptance criteria to check

This is about submitting one or more formulae to homebrew/core, not getting the existing basefoundry/base tap approved into core. The likely future shape is:

• basefoundry as the user-facing Homebrew/core formula for Base.
• base-bash-libs as a separate Homebrew/core dependency.
• basefoundry declares depends_on "base-bash-libs" so brew install basefoundry installs the reusable Bash libraries automatically.
• The core path should not require brew trust basefoundry/base.

Current Homebrew/core acceptance checklist from official docs:

• Build and pass tests on the latest three supported macOS versions, on Apple Silicon and Intel, and on x86_64 Linux. If upstream does not support a platform, the formula may need to be disabled there.
• Be open source with a Debian Free Software Guidelines-compatible license, or public-domain equivalent, and be built from source or produce cross-platform binaries. Binary-only packages belong in casks, not core formulae.
• Avoid proprietary dependencies, cask dependencies, and automatic runtime installation of casks or proprietary software.
• Use a stable upstream release with a tagged version. Tarballs are preferred over Git checkouts, and release tarballs should include the version in the filename when possible.
• Be stable, maintainable, and not require extensive patching or carry known unpatched security vulnerabilities.
• Meet Homebrew notability expectations. The docs cite GitHub examples of at least 30 forks, 30 watchers, or 75 stars. For self-submitted software, the threshold is three times higher, e.g. 90 forks, 90 watchers, or 225 stars.
• Be used by someone other than the author, such as a third-party submitter or an external request to add it to Homebrew.
• Have a homepage users can open in a browser to learn about the project.
• Avoid self-update behavior in the formula path. Homebrew wants package upgrades managed by Homebrew.
• Avoid install scripts that fetch unversioned default-branch content or unchecksummed tarballs.
• Build as a command-line tool or library by default, not a native .app or GUI-first package.
• Build with the latest stable Xcode Clang.
• Avoid heavy manual pre/post-install intervention.
• Avoid bundling multiple separate upstream projects where Homebrew can package them separately; for Base, this supports keeping base-bash-libs as a dependency rather than hiding it inside basefoundry.
• Use a non-conflicting formula name. Homebrew naming guidance says newer formulae must adapt if a name would confuse users or collide with an existing formula. This supports basefoundry instead of base.
• Pass Homebrew checks, especially brew audit --new --formula <formula>, build-from-source install, and the formula test do block.
• Submit formula changes to Homebrew/homebrew-core as pull requests, with one formula per commit and one commit per formula.
• If AI assistance is used to create the Homebrew issue or PR, Homebrew requires disclosure in the initial issue or PR and human review before asking maintainers to review it.

Useful references:

• Acceptable Formulae: https://docs.brew.sh/Acceptable-Formulae
• Formula Cookbook: https://docs.brew.sh/Formula-Cookbook
• How to Open a Homebrew Pull Request: https://docs.brew.sh/How-To-Open-a-Homebrew-Pull-Request