Configuration recipes

Choose a setup profile

Use a core profile for a narrower command-line setup and defer optional features by gate. Preserve the command and its output with a machine record so the resulting state is explainable.

1
cd ~/dotfiles
2
DF_PROFILE=core \
3
DF_DO_AUTH=0 \
4
DF_DO_LOCAL_LLM=0 \
5
DF_DO_MACOS_SERVICES=0 \
6
./bootstrap.sh

The authoritative gate list is the header of bootstrap.sh. Skipping a stage leaves it unreconciled; tools from earlier runs may still be installed. Final verification skips the corresponding check too. A disabled gate is not an uninstall operation.

Change a managed shell setting

Edit the chezmoi source, inspect the deployment, apply it, then test in a new login shell:

1
"${EDITOR:-vi}" ~/dotfiles/home/dot_zshrc.tmpl
2
chezmoi diff
3
chezmoi apply
4
exec zsh -l

This edits the authoritative source before deployment. chezmoi edit ~/.zshrc edits only the source; add --apply to deploy after the editor exits. The rendered target is useful for observation but is not the source of truth. See chezmoi setup.

Diagnose runtime resolution

1
printf 'DF_USE_PLAT=%s\n' "${DF_USE_PLAT:-unset}"
2
printf 'LOCAL=%s\n' "${_LOCAL_PLAT:-unset}"
3
command -v node npm python cargo lean
4
bash ~/dotfiles/install/verify-path.sh
5
bash ~/dotfiles/install/verify-tools.sh

Use verify-path.sh for ordering and stale-symlink problems; use verify-tools.sh for selected runtime postconditions. If a bootstrap run reports degradations, repair the named component before assuming unrelated commands are healthy. The troubleshooting guide contains established symptom-to-cause procedures.