freeze

Restricting file edits to a specific directory involves setting a persistent boundary that blocks Edit and Write operations outside that path. This prevents unintended changes by enforcing the rule via a PreToolUse hook for the current session.

Preventing accidental file modifications outside your project scope requires locking edits to a chosen directory. By resolving a user-specified path to an absolute directory, a boundary file persists across actions to block any out-of-scope operations.

A PreToolUse hook enforces a directory boundary by intercepting Edit and Write operations before execution. It checks the target path against a persistent boundary file and blocks any operation attempting to modify files outside the resolved absolute directory.

Safeguarding critical code areas while debugging is possible without dependencies by activating a session boundary. You provide a directory path to freeze edits to, and the boundary restricts all writes to that specific scope until the session ends.

The edit boundary persists across multiple actions in the same session by using a persistent boundary file. Once activated, it continuously restricts Edit and Write operations to the specified directory until the current session explicitly ends.

Locking writes to a single directory to prevent scope drift is necessary when edits might escape intended boundaries and cause unintended changes. Constraining operations to a user-specified directory safeguards against mistakes during sensitive debugging or refactoring tasks.