guard

Preventing destructive commands during production maintenance requires enabling guard mode to warn before executing destructive actions and lock edits to a defined directory. It combines pre-checks and freeze boundaries to restrict tool usage.

Restricting edits to a specific directory during live debugging involves activating guard mode to enforce a freeze boundary. This locks file modifications outside your selected directory while warning against destructive commands.

Yes, you can combine pre-checks and freeze boundaries by enabling guard mode. It relies on sibling safety mechanisms to perform pre-checks and enforce a directory-scoped freeze boundary before tool usage, ensuring strict change boundaries.

Guard mode requires selecting a restricted directory to function properly. Without defining this boundary, it cannot enforce directory-scoped edit restrictions or apply its safety checks to prevent accidental damage during operations.

You should not use unrestricted edits during prod maintenance when strict change boundaries are required. Guard mode applies warnings for destructive commands and locks edits outside a defined directory to prevent accidental or malicious damage.