freeze

Locking file edits to a directory restricts Edit and Write operations to an allowed absolute path, blocking modifications to source files outside that boundary. A state file persists the restriction across session restarts.

Directory path normalization resolves relative input to an absolute path and enforces trailing slashes to avoid false matches like /src vs /src-old. This ensures the edit restriction boundary applies strictly to the intended folder.

Yes, persisting a freeze boundary across session restarts is supported via a state file. The directory lock remains active until you explicitly reset it using the unfreeze command.

Resetting an edit restriction boundary during a session requires issuing the unfreeze command. This simple mechanism deactivates the directory lock and restores unrestricted Write and Edit operations.

Preventing source file drift during a session involves locking edits to a designated directory. This blocks accidental modifications to files outside the allowed path and survives restarts through a persistent state file.

Yes, the freeze lock applies to both Edit and Write operations. Any attempt to modify files outside the designated directory boundary is blocked to prevent unintended changes to source files.