The separation of base-bash-libs into an external repository is architecturally non-obvious and affects contributor setup, Homebrew formula structure, and CI configuration. Neither FAQ.md nor any other onboarding document explains why this separation was made. Users encountering BASE-D007 findings in doctor output, or seeing the three-step resolution order in base-bash-libs.md, have no single FAQ entry to consult for the rationale.
Fix: Add a FAQ entry: "Why does Base require an external base-bash-libs checkout or package?" covering: the standalone reusability goal, the Homebrew/core readiness path, the three resolution modes (explicit env var, sibling checkout, Homebrew), and what to do when the library is missing (which doctor finding fires and what the fix command is).
File: FAQ.md
The separation of
base-bash-libsinto an external repository is architecturally non-obvious and affects contributor setup, Homebrew formula structure, and CI configuration. NeitherFAQ.mdnor any other onboarding document explains why this separation was made. Users encounteringBASE-D007findings in doctor output, or seeing the three-step resolution order inbase-bash-libs.md, have no single FAQ entry to consult for the rationale.Fix: Add a FAQ entry: "Why does Base require an external
base-bash-libscheckout or package?" covering: the standalone reusability goal, the Homebrew/core readiness path, the three resolution modes (explicit env var, sibling checkout, Homebrew), and what to do when the library is missing (which doctor finding fires and what the fix command is).File:
FAQ.md