removed more old references to the atomic argument

Author: ndbroadbent

docs/src/content/docs/features/atomic-identifiers.mdx

@@ -28,7 +28,7 @@ These transformations break the brand identity and can cause issues when the nam
 
 ## The Solution
 
-With atomic mode, compound identifiers are preserved as single units:
+With atomic identifiers, compound identifiers are preserved as single units:
 
 ```bash
 # With atomic mode
@@ -38,11 +38,11 @@ DocSpring → DOCSPRING (SCREAMING_SNAKE_CASE)
 DocSpring → DocSpring (PascalCase - preserved)
 ```
 
-## Using Atomic Mode
+## With Atomic Identifiers
 
 ### Command Line Flags
 
-You can specify atomic mode using CLI flags:
+You can enable atomic identifiers using CLI flags:
 
 <Tabs>
 <TabItem label="Both atomic">

docs/src/content/docs/mcp/ai-guide.mdx

@@ -57,9 +57,6 @@ When things go wrong, explain the issue and provide solutions.
 
    ```
    Tool: renamify_apply
-   Arguments: {
-     "atomic": true
-   }
    ```
 
 6. **Report the results**
@@ -277,10 +274,7 @@ Before applying changes in production:
 
 3. Review with `format: "diff"` if requested
 
-4. Apply with `atomic:
-true` always
-
-5. Consider `commit: true` for automatic git commit
+4. Consider `commit: true` for automatic git commit
 
 </Steps>
 
@@ -473,7 +467,6 @@ For AI developers integrating Renamify MCP:
 
 ```json
 {
-  "atomic": true, // Always use atomic operations
   "preview": "summary", // Best for AI agents
   "commit": false, // Let user decide
   "dryRun": false, // Unless explicitly testing

docs/src/content/docs/mcp/examples.mdx

@@ -53,9 +53,6 @@ User: "Yes, apply the changes"
 AI: Applying the renaming now:
 
 Tool: renamify_apply
-Arguments: {
-  "atomic": true
-}
 
 Result: Successfully applied 23 replacements across 8 files and renamed 2 files.
 
@@ -187,7 +184,6 @@ Summary:
    ```
    Tool: renamify_apply
    Arguments: {
-     "atomic": true,
      "commit": true
    }
    ```
@@ -269,9 +265,6 @@ Created plan: 5b2a7f9c1e4d8f3a
 Now applying the changes:
 
 Tool: renamify_apply
-Arguments: {
-  "atomic": true
-}
 
 Result: Successfully applied 42 replacements
 

docs/src/content/docs/mcp/overview.mdx

@@ -176,9 +176,6 @@ User: "Yes, apply the changes"
 AI: I'll apply the renaming plan now:
 
 Tool: renamify_apply
-Arguments: {
-  "atomic": true
-}
 
 Result: Successfully applied 47 replacements across 12 files and renamed 3 files
 ```

docs/src/content/docs/mcp/tools.mdx

@@ -120,7 +120,7 @@ Arguments: {
 }
 ```
 
-With atomic mode, compound words like "DocSpring" are treated as single units, preventing unwanted word boundary detection (e.g., `doc_spring`).
+With atomic identifiers, compound words like "DocSpring" are treated as single units, preventing unwanted word boundary detection (e.g., `doc_spring`).
 
 ### Response Example
 
@@ -151,15 +151,13 @@ Applies a renaming plan to make the actual changes to your codebase.
 | ---------- | ------- | -------- | ------- | ------------------------- |
 | `planId`   | string  | No       | Latest  | Specific plan ID to apply |
 | `planPath` | string  | No       | Auto    | Path to plan file         |
-| `atomic`   | boolean | No       | `true`  | All-or-nothing execution  |
 | `commit`   | boolean | No       | `false` | Create git commit after   |
 
 ### Example Usage
 
 ```
 Tool: renamify_apply
 Arguments: {
-  "atomic": true,
   "commit": true
 }
 ```

renamify-cli/src/replace.rs

@@ -144,7 +144,6 @@ pub fn handle_replace(
     let apply_options = renamify_core::ApplyOptions {
         create_backups: true,
         backup_dir: PathBuf::from(".renamify/backups"),
-        atomic: true,
         commit: false,
         force: force_with_conflicts,
         skip_symlinks: false,

renamify-core/src/apply.rs

@@ -15,8 +15,6 @@ pub struct ApplyOptions {
     pub create_backups: bool,
     /// Path to backup directory
     pub backup_dir: PathBuf,
-    /// Perform atomic operations
-    pub atomic: bool,
     /// Commit changes to git after successful apply
     pub commit: bool,
     /// Force apply even with conflicts
@@ -32,7 +30,6 @@ impl Default for ApplyOptions {
         Self {
             create_backups: true,
             backup_dir: PathBuf::from(".renamify/backups"),
-            atomic: true,
             commit: false,
             force: false,
             skip_symlinks: true,
@@ -621,9 +618,7 @@ pub fn apply_plan(plan: &mut Plan, options: &ApplyOptions) -> Result<()> {
                 e
             ))?;
 
-            if options.atomic {
-                rollback(&mut state)?;
-            }
+            rollback(&mut state)?;
 
             return Err(e);
         }
@@ -693,9 +688,7 @@ pub fn apply_plan(plan: &mut Plan, options: &ApplyOptions) -> Result<()> {
         if let Err(e) = perform_rename(&adjusted_from, &adjusted_to, is_dir, &mut state) {
             state.log(&format!("Error performing rename: {}", e))?;
 
-            if options.atomic {
-                rollback(&mut state)?;
-            }
+            rollback(&mut state)?;
 
             return Err(e);
         }

renamify-core/src/operations/apply.rs

@@ -44,7 +44,6 @@ pub fn apply_operation(
     let apply_options = ApplyOptions {
         backup_dir: renamify_dir.join("backups"),
         create_backups: true,
-        atomic: true,
         commit,
         force,
         skip_symlinks: false,

renamify-core/src/operations/rename.rs

@@ -381,7 +381,6 @@ fn apply_rename_changes(plan: &mut Plan, commit: bool, force_with_conflicts: boo
     let apply_options = ApplyOptions {
         create_backups: true,
         backup_dir,
-        atomic: true,
         commit,
         force: force_with_conflicts,
         skip_symlinks: false,

renamify-core/src/undo.rs

@@ -392,7 +392,6 @@ pub fn redo_renaming(id: &str, renamify_dir: &Path) -> Result<()> {
     let options = ApplyOptions {
         backup_dir: renamify_dir.join("backups"),
         create_backups: true,
-        atomic: true,
         ..Default::default()
     };