freeze

To lock file edits to a directory during a session, you can set a predefined boundary that restricts write operations. This ensures changes stay confined to the specified folder, preventing accidental modifications to files outside the allowed path.

A directory boundary is a per-session restriction that blocks edits outside a predefined folder. You need it during module-scoped work or debugging to prevent scope creep and ensure unintended changes do not affect other parts of the project.

You can block write operations by applying a pre-check hook that denies edits targeting files outside an allowed path. The boundary is stored in a state file for the current session, actively blocking operations that exceed the directory scope.

Restricting edits to a boundary requires no external dependencies or components. It relies solely on a per-session state file to store the boundary and a validation hook to enforce the directory restrictions during your work.

Yes, when edits are blocked outside the predefined directory, the system logs boundary violations. This provides visibility into attempted scope creep during your debugging or development session.