freeze

To restrict file edits to a specific directory, you can lock a designated path boundary using a pre-tool hook that enforces Edit and Write operations, preventing unintended project-wide changes during debugging.

Preventing accidental edits outside a module while debugging is achieved by setting a persistent directory boundary in a state file, which scopes changes and blocks any Write or Edit operations outside that allowed path.

A pre-tool hook enforces directory boundaries by intercepting Edit and Write operations and checking them against a persistent boundary stored in a state file, rejecting any modifications that fall outside the allowed directory.

Yes, you can lock edits to a directory for the entire session to isolate changes to a module, ensuring the restriction persists and prevents any unintended modifications to the rest of the project.

Yes, you need to specify a target directory before freezing edits, which establishes the allowed path boundary and ensures all subsequent Write and Edit operations are restricted to that location.

When a directory is frozen, Write operations outside the allowed path are automatically blocked by the pre-tool hook, preventing unintended changes and keeping edits strictly within the designated boundary.