freeze

You can restrict code edits to a single directory by activating a boundary lock that records the allowed path and blocks any file modifications outside that directory while still permitting read access.

To prevent accidental changes outside your target scope during refactoring, enforce a directory boundary that records the allowed folder on activation and blocks edits to any files outside that specific path.

Yes, freezing a directory boundary still allows reading files outside the scope. The restriction specifically blocks write operations and file modifications, ensuring read access remains unaffected for debugging and code reviews.

The best way to contain code changes to a specific path for a focused review is to lock edits to a single directory, which enforces the boundary before every file modification and prevents accidental updates elsewhere.

You lock edits to a directory by issuing the command 'freeze to <directory>', which records the allowed directory on activation and enforces the boundary by blocking edits outside that path.