Problem
PR #753 identified measurable per-call hook process-spawn overhead. Maintainer direction there was to keep hooks enabled by default, add an opt-out, and persist the user's choice so later installs and updates respect it.
Proposed behavior
install --no-hooks disables CBM-managed lifecycle/tool hooks.install --hooks re-enables them.- Bare
install keeps hooks enabled by default and reads the persisted preference.
- The preference is stored as
install_hooks in the existing CLI config database.
- All current hook-capable install surfaces obey the same policy.
- MCP, skills, instructions, profiles, and other non-hook integration remain unchanged.
- Plan and dry-run reflect the effective policy without persisting preview flags.
- Existing foreign/user hooks remain untouched.
This follows the maintainer-approved direction in #753.
Problem
PR #753 identified measurable per-call hook process-spawn overhead. Maintainer direction there was to keep hooks enabled by default, add an opt-out, and persist the user's choice so later installs and updates respect it.
Proposed behavior
install --no-hooksdisables CBM-managed lifecycle/tool hooks.install --hooksre-enables them.installkeeps hooks enabled by default and reads the persisted preference.install_hooksin the existing CLI config database.This follows the maintainer-approved direction in #753.