Context
The pre-execution action verification feature added in #1630 introduced [security.pre_execution_verify] config section. The interactive --init wizard does not yet offer a configuration step for this section.
Required
Add a wizard step in the --init flow that:
- Asks whether to enable pre-execution verification (default: yes)
- Optionally allows adding allowed paths for
DestructiveCommandVerifier
- Shows the current shell_tools default list (
bash, shell, terminal)
Labels
enhancement