freeze

You can restrict file edits to a specific directory by loading a boundary from a state file, which blocks any modifications outside the allowed path. This enforces scoped safety for your debugging session.

The best way to prevent accidental changes outside a single module folder is to enforce a frozen boundary via a pre-use hook. This hook denies edits outside the designated directory, ensuring modifications remain scoped.

Directory freeze enforcement works by intercepting Edit and Write operations through a pre-use hook. The hook checks the requested path against a boundary stored in a state file and denies any edit falling outside that allowed directory.

Yes, you can update the allowed directory boundary by re-running the setup process. Redefining the allowed path in the state file rolls back the previous boundary and applies the new scope to your current session.

You should use directory scoping for file modifications during debugging or when making scoped changes to a single module. It confines modifications to one folder, preventing accidental edits to unrelated project files.

A limitation of freezing edits to a directory is that the boundary remains active for the entire session unless you re-run setup to redefine the path. It also relies on a state file to enforce the boundary.