file-safety

Safe editing rules prevent accidental file modification by prohibiting unsafe overwrites in protected directories like data/ and outs/, requiring explicit user confirmation when uncertain, and allowing new files with updated names instead of overwriting existing ones.

Protecting important files during automated edits involves enforcing overwrite protection rules that block modifications to original data, prompt for user confirmation when uncertain, and require creating new files with updated names instead of overwriting existing ones.

Safely renaming or moving files that other scripts depend on requires applying file safety rules that provide guidance for dependent file operations and enforce explicit user confirmation to prevent breaking script dependencies within data/ or outs/ directories.

Editing files in protected directories without explicit user confirmation is not allowed when uncertain, as safe editing rules enforce user confirmation for modifications within data/ and outs/ to ensure data integrity and prevent accidental deletion or overwrites.

Explicit user confirmation for file modifications is needed when overwriting existing files, deleting data, or moving and renaming files within protected directories like data/ and outs/ that other scripts depend on, ensuring safe editing and data integrity.

Overwrite protection does not block new file creation in data directories, as safe editing rules prohibit unsafe overwrites of existing files while explicitly allowing the creation of new files with updated names to preserve original data.