Step 6 of the "Mac Bootstrap Sequence" says "basectl setup prepares the managed shell startup model with basectl update-profile." This is factually wrong: setup does not invoke update-profile automatically. Every installation guide — README.md, CONTRIBUTING.md, and the newcomer orientation — shows these as two distinct steps that the user must run separately. A user reading this sequence will believe their shell is automatically configured after basectl setup, then be confused when their shell does not reflect the Base runtime after a fresh install.
Fix: Change step 6 to say that the user must explicitly run basectl update-profile as a separate step after setup, and note it only needs to be run once or when updating shell dotfiles.
File: docs/architecture.md
Step 6 of the "Mac Bootstrap Sequence" says "
basectl setupprepares the managed shell startup model withbasectl update-profile." This is factually wrong: setup does not invoke update-profile automatically. Every installation guide — README.md, CONTRIBUTING.md, and the newcomer orientation — shows these as two distinct steps that the user must run separately. A user reading this sequence will believe their shell is automatically configured afterbasectl setup, then be confused when their shell does not reflect the Base runtime after a fresh install.Fix: Change step 6 to say that the user must explicitly run
basectl update-profileas a separate step after setup, and note it only needs to be run once or when updating shell dotfiles.File:
docs/architecture.md