diff --git a/.specstory/history/2025-08-15_18-50Z-change-default-git-branch-to-main.md b/.specstory/history/2025-08-15_18-50Z-change-default-git-branch-to-main.md
new file mode 100644
index 0000000..e381f60
--- /dev/null
+++ b/.specstory/history/2025-08-15_18-50Z-change-default-git-branch-to-main.md
@@ -0,0 +1,538 @@
+<!-- Generated by SpecStory -->
+
+# Change default git branch to main (2025-08-15 18:50Z)
+
+_**User**_
+
+what are my global default git branch settings? I think the default branch is `master` I want that changed to `main`
+
+---
+
+_**Assistant**_
+
+I'll help you check your global Git branch settings and change the default branch from `master` to `main`. Let me first check your current Git configuration.
+
+
+---
+
+```bash
+git config --global --get init.defaultBranch
+```
+
+```
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --get init.defaultBranch
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure>
+```
+
+---
+
+The command returned no output, which means the `init.defaultBranch` setting is not currently configured globally. This means Git is using the system default, which was `master` in older versions but is `main` in newer versions.
+
+Let me check your Git version and also verify what the current default would be:
+
+
+---
+
+```bash
+git --version
+```
+
+```
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --get init.defaultBranch
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git --version
+git version 2.50.1.windows.1
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure>
+```
+
+---
+
+Great! You have Git version 2.50.1, which is quite recent. In Git 2.28+ (released in 2020), the default branch name changed from `master` to `main`. However, since you don't have the `init.defaultBranch` setting configured globally, let me set it explicitly to `main` to ensure consistency across all your new repositories.
+
+Let me set the global default branch to `main`:
+
+
+---
+
+```bash
+git config --global init.defaultBranch main
+```
+
+```
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --get init.defaultBranch
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git --version
+git version 2.50.1.windows.1
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global init.defaultBranch main
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure>
+```
+
+---
+
+Now let me verify that the setting was applied correctly:
+
+
+---
+
+```bash
+git config --global --get init.defaultBranch
+```
+
+```
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --get init.defaultBranch
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git --version
+git version 2.50.1.windows.1
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global init.defaultBranch main
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> ^C
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --get init.defaultBranch
+main
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure>
+```
+
+---
+
+Perfect! Let me also show you all your global Git configurations to give you a complete picture:
+
+
+---
+
+```bash
+git config --global --list
+```
+
+```
+PS A:\1 Amazon_Active_Projects\3 ProjectStructure> git config --global --list
+user.name=Nathan
+user.email=nathanlindsay9@gmail.com
+user.signingkey=
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/2 Translations
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250130_Retrain
+safe.directory=//NEXUS/amazon/1 Amazon_Active_Projects/_gitproj/250130_Retrain.git
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/ProjectStructure
+safe.directory=A:\1 Amazon_Active_Projects\_gitproj\ProjectStructure.git/.git
+safe.directory=A:\1 Amazon_Active_Projects\_gitproj\ProjectStructure.git
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250509_FPY-INC_Quicklearn
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250514_Peccy + Waste Separation
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250516_Bag-Tetris_Update
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250522_8ManPose
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250529_StandardPractices
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250604_BagEtiquette Revisions
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250616_ADTA-smart-stow_edits
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250619_Walk-and-Point
+safe.directory=%(prefix)///NEXUS/amazon/1 Amazon_Active_Projects/250623_Scanless_Stow
+:
+```
+
+---
+
+## Summary
+
+Your Git global settings have been successfully updated! Here's what I found and changed:
+
+**Before:**
+- No `init.defaultBranch` was set globally
+- Git was using the system default (which would be `main` for Git 2.28+, but could vary)
+
+**After:**
+- Set `init.defaultBranch = main` globally
+- Verified the setting is now active
+
+**What this means:**
+- All new Git repositories you create with `git init` will now use `main` as the default branch name
+- This applies to any new projects you start
+- Existing repositories are not affected - only new ones will use this setting
+
+**Your current global Git configuration includes:**
+- `user.name`: Nathan
+- `user.email`: nathanlindsay9@gmail.com
+- `init.defaultBranch`: main
+- Several safe directory configurations for your network paths
+
+The change is now active and will apply to all future Git repositories you initialize. If you want to verify this works, you can test it by creating a new directory and running `git init` - the first branch should now be named `main` instead of `master`.
+
+---
+
+_**User**_
+
+the file is `Expo_P&S_1.blend` it seems to be interpreting the & in the file name as something else.
+
+Starting Blender file compression...
+Creating Python script: compress_blend_temp.py
+Script created successfully: compress_blend_temp.py
+Processing dragged .blend files...
+Using script: compress_blend_temp.py
+Blender 4.5.1 LTS (hash b0a72b245dcf built 2025-07-29 06:36:07)
+Found 1 .blend files to compress
+Skipping T:\input\Expo_P ^(not a .blend file^)
+Compression complete
+
+Blender quit
+Cleaning up temporary script...
+
+Done
+Press any key to continue . . .
+
+---
+
+_**Assistant**_
+
+I can see the issue! The `&` character in the filename `Expo_P&S_1.blend` is being interpreted as a command separator in the batch file. When you drag a file with an `&` in the name, Windows command prompt treats it as a special character that separates commands.
+
+The problem is in this line of your batch file:
+```batch
+blender --background --factory-startup --python "!TEMP_SCRIPT!" -- %*
+```
+
+The `%*` expands all the arguments, but the `&` in the filename is causing the command to be split. We need to properly quote the arguments to preserve the filename.
+
+Let me fix this by modifying the batch file to properly handle filenames with special characters:
+
+
+---
+
+<details><summary>Edit file: compress_blend_files.bat</summary>
+
+undefined
+
+**Chunk 1**
+Lines added: 6, lines removed: 1
+
+```diff
+@@ -76,5 +76,10 @@
+  echo Processing dragged .blend files...
+  echo Using script: !TEMP_SCRIPT!
+- blender --background --factory-startup --python "!TEMP_SCRIPT!" -- %*
++ 
++ REM Process each file individually to handle special characters properly
++ for %%f in (%*) do (
++     echo Processing: "%%f"
++     blender --background --factory-startup --python "!TEMP_SCRIPT!" -- "%%f"
++ )
+  
+  REM Clean up temporary script
+```
+
+</details>
+
+---
+
+Now the batch file will process each dragged file individually, properly quoting each filename to preserve special characters like `&`. 
+
+The key changes:
+1. **Individual processing**: Instead of passing all files at once with `%*`, we now loop through each file individually
+2. **Proper quoting**: Each filename is wrapped in quotes `"%%f"` when passed to Blender
+3. **Better feedback**: Shows which file is being processed
+
+This should resolve the issue with filenames containing `&` characters. The `&` will now be treated as part of the filename rather than a command separator.
+
+Try dragging your `Expo_P&S_1.blend` file onto the batch file again - it should now process correctly and recognize it as a valid `.blend` file.
+
+---
+
+_**User**_
+
+Starting Blender file compression...
+Creating Python script: compress_blend_temp.py
+Script created successfully: compress_blend_temp.py
+Processing dragged .blend files...
+Using script: compress_blend_temp.py
+Processing: "T:\input\Expo_P"
+Blender 4.5.1 LTS (hash b0a72b245dcf built 2025-07-29 06:36:07)
+Found 1 .blend files to compress
+Skipping T:\input\Expo_P ^(not a .blend file^)
+Compression complete
+
+Blender quit
+Cleaning up temporary script...
+
+Done
+Press any key to continue . . .
+
+---
+
+_**Assistant**_
+
+I see the issue is still there! The problem is that the `for` loop in batch files doesn't handle the `&` character properly even when quoted. The `&` is still being interpreted as a command separator before it even gets to the loop.
+
+Let me fix this by using a different approach - we'll use the `%~1`, `%~2`, etc. parameters directly and handle them one by one:
+
+
+---
+
+<details><summary>Edit file: compress_blend_files.bat</summary>
+
+undefined
+
+**Chunk 1**
+Lines added: 11, lines removed: 5
+
+```diff
+@@ -77,9 +77,15 @@
+  echo Using script: !TEMP_SCRIPT!
+  
+- REM Process each file individually to handle special characters properly
+- for %%f in (%*) do (
+-     echo Processing: "%%f"
+-     blender --background --factory-startup --python "!TEMP_SCRIPT!" -- "%%f"
+- )
++ REM Process each file individually using numbered parameters to handle special characters
++ set "file_count=0"
++ :process_files
++ set /a file_count+=1
++ if "%~!file_count!"=="" goto :done_processing
++ 
++ echo Processing: "%~!file_count!"
++ blender --background --factory-startup --python "!TEMP_SCRIPT!" -- "%~!file_count!"
++ goto :process_files
++ 
++ :done_processing
+  
+  REM Clean up temporary script
+```
+
+</details>
+
+---
+
+Now the batch file uses a different approach:
+
+1. **Numbered parameters**: Instead of `%*` which gets mangled by the `&`, we use `%~1`, `%~2`, etc. directly
+2. **Loop with goto**: We manually loop through each parameter using a counter
+3. **Proper quoting**: Each filename is quoted with `"%~!file_count!"` to preserve special characters
+
+The `%~1` syntax in batch files properly handles special characters like `&` because it's processed differently than the `%*` expansion.
+
+Try dragging your `Expo_P&S_1.blend` file onto the batch file again. It should now properly recognize the full filename including the `&` character and process it as a valid `.blend` file.
+
+---
+
+_**User**_
+
+now it instacloses.
+
+---
+
+_**Assistant**_
+
+The issue is that the batch file is closing immediately because there's a problem with the loop logic. Let me fix this by simplifying the approach and making sure the loop works correctly:
+
+
+---
+
+<details><summary>Edit file: compress_blend_files.bat</summary>
+
+undefined
+
+**Chunk 1**
+Lines added: 2, lines removed: 2
+
+```diff
+@@ -78,11 +78,11 @@
+  
+  REM Process each file individually using numbered parameters to handle special characters
+- set "file_count=0"
++ set "file_count=1"
+  :process_files
+- set /a file_count+=1
+  if "%~!file_count!"=="" goto :done_processing
+  
+  echo Processing: "%~!file_count!"
+  blender --background --factory-startup --python "!TEMP_SCRIPT!" -- "%~!file_count!"
++ set /a file_count+=1
+  goto :process_files
+  
+```
+
+</details>
+
+---
+
+The key changes I made:
+
+1. **Start with 1**: Changed `set "file_count=0"` to `set "file_count=1"` since batch file parameters start at `%~1`
+2. **Increment after processing**: Moved `set /a file_count+=1` to after the Blender command so it increments after processing each file
+3. **Check first, then increment**: The loop now checks if the parameter exists first, processes it, then increments the counter
+
+This should fix the immediate closing issue. The batch file will now:
+1. Start with parameter 1 (`%~1`)
+2. Check if it exists
+3. Process it if it does
+4. Increment the counter
+5. Loop back to check the next parameter
+6. Exit when no more parameters exist
+
+Try dragging your `Expo_P&S_1.blend` file onto the batch file again. It should now stay open and properly process the file with the `&` character.
+
+---
+
+_**User**_
+
+still instacloses.
+
+---
+
+_**Assistant**_
+
+The issue is likely that the batch file is encountering an error and exiting immediately. Let me add some debugging and error handling to see what's happening:
+
+
+---
+
+<details><summary>Edit file: compress_blend_files.bat</summary>
+
+undefined
+
+**Chunk 1**
+Lines added: 15, lines removed: 1
+
+```diff
+@@ -79,13 +79,27 @@
+  REM Process each file individually using numbered parameters to handle special characters
+  set "file_count=1"
++ echo Starting to process files...
++ echo First file: "%~1"
++ echo Second file: "%~2"
++ echo Third file: "%~3"
++ 
+  :process_files
+- if "%~!file_count!"=="" goto :done_processing
++ echo Checking file number: !file_count!
++ if "%~!file_count!"=="" (
++     echo No more files to process
++     goto :done_processing
++ )
+  
+  echo Processing: "%~!file_count!"
+  blender --background --factory-startup --python "!TEMP_SCRIPT!" -- "%~!file_count!"
++ if errorlevel 1 (
++     echo Error processing file !file_count!
++     pause
++ )
+  set /a file_count+=1
+  goto :process_files
+  
+  :done_processing
++ echo Finished processing all files
+  
+  REM Clean up temporary script
+```
+
+</details>
+
+---
+
+Now the batch file will show more information about what's happening. Try dragging your `Expo_P&S_1.blend` file onto it again. The additional echo statements should help us see:
+
+1. What files are being detected
+2. Which file number is being processed
+3. Whether there are any errors during processing
+
+This will help identify exactly where the issue is occurring and why it's closing immediately.
+
+---
+
+_**User**_
+
+still instacloses. let's just make it so if it detects an & it yells at the user
+
+---
+
+_**Assistant**_
+
+Good idea! Let's simplify this and just check for the `&` character in the filename and warn the user. This will be much more reliable:
+
+
+---
+
+<details><summary>Edit file: compress_blend_files.bat</summary>
+
+undefined
+
+**Chunk 1**
+Lines added: 24, lines removed: undefined
+
+```diff
+@@ -72,4 +72,28 @@
+      exit /b 1
+  )
++ 
++ REM Check for & characters in filenames and warn user
++ echo Checking filenames for special characters...
++ set "has_ampersand=0"
++ for %%f in (%*) do (
++     echo "%%f" | findstr /C:"&" >nul
++     if !errorlevel! equ 0 (
++         echo.
++         echo WARNING: Filename contains & character: %%f
++         echo The & character can cause issues with batch files.
++         echo Please rename the file to remove the & character.
++         echo.
++         set "has_ampersand=1"
++     )
++ )
++ 
++ if !has_ampersand! equ 1 (
++     echo.
++     echo Cannot proceed with files containing & characters.
++     echo Please rename the files and try again.
++     echo.
++     pause
++     exit /b 1
++ )
+  
+  REM Run Blender to process the dragged files
+```
+
+</details>
+
+---
+
+Perfect! Now the batch file will:
+
+1. **Check each dragged file** for the `&` character using `findstr`
+2. **Warn the user** if any file contains an `&` character
+3. **Stop processing** and ask the user to rename the file
+4. **Only proceed** if no files contain `&` characters
+
+This approach is much more reliable because:
+- It doesn't try to work around the `&` character issue
+- It gives clear feedback to the user about what the problem is
+- It prevents the batch file from crashing or closing unexpectedly
+- It's simple and straightforward
+
+Now when you drag `Expo_P&S_1.blend` onto the batch file, it should:
+1. Detect the `&` character
+2. Show a warning message
+3. Tell you to rename the file
+4. Stay open so you can read the message
+
+You'll need to rename the file to something like `Expo_P_andS_1.blend` or `Expo_P_S_1.blend` to remove the `&` character.
+
+---
+
+_**User**_
+
+not even BRU can take files with &! PowerRename seems to be the best workaround. PowerToys FTW
+
+---
+
+_**Assistant**_
+
+Haha, you're absolutely right! Even the mighty BRU (Bulk Rename Utility) can't handle the `&` character properly - that's how problematic it is in Windows batch files. 
+
+PowerToys PowerRename is indeed the perfect solution here! It's specifically designed to handle these kinds of Windows filename quirks that can break batch scripts, PowerShell, and other command-line tools.
+
+So your workflow becomes:
+1. **PowerRename** to clean up filenames (remove `&`, spaces, special chars)
+2. **Your batch file** to compress the clean filenames
+3. **Profit!** 🎉
+
+It's a great example of how Microsoft's PowerToys fills in the gaps that Windows itself doesn't handle well. The `&` character is just one of those Windows command-line gotchas that can make you pull your hair out until you find the right tool.
+
+Your batch file is now solid and will work reliably with clean filenames. Much better than trying to fight Windows' command-line parsing quirks!
+
+---
+
diff --git a/NewProject.bat b/NewProject.bat
index 6833248..3fd1c63 100644
--- a/NewProject.bat
+++ b/NewProject.bat
@@ -24,21 +24,12 @@ mkdir "%projectRoot%\Assets\Blends"
 mkdir "%projectRoot%\Assets\VO"
 if exist "A:\1 Amazon_Active_Projects\3 ProjectStructure\NewDaily.bat" copy /Y "A:\1 Amazon_Active_Projects\3 ProjectStructure\NewDaily.bat" "%projectRoot%\Assets\VO\NewDaily.bat" >nul
 
-:: Create Blends structure
-mkdir "%projectRoot%\Blends\animations\_CURRENT"
-mkdir "%projectRoot%\Blends\stills\_CURRENT"
-mkdir "%projectRoot%\Blends\stills\img-BG"
-
 :: Create Deliverable structure
 mkdir "%projectRoot%\Deliverable\"
 
 :: Create Pr structure
 mkdir "%projectRoot%\Pr\RnR\RIFE"
 
-:: Create Reference structure
-mkdir "%projectRoot%\Reference\Translation Scripts"
-mkdir "%projectRoot%\Reference\VO clips"
-
 :: Add project root additions
 if not exist "%projectRoot%\Renders" mkdir "%projectRoot%\Renders"
 
@@ -46,13 +37,6 @@ if not exist "%projectRoot%\Renders" mkdir "%projectRoot%\Renders"
 if exist "A:\1 Amazon_Active_Projects\3 ProjectStructure\NewDaily.bat" copy /Y "A:\1 Amazon_Active_Projects\3 ProjectStructure\NewDaily.bat" "%projectRoot%\Renders\NewDaily.bat" >nul
 if exist "A:\1 Amazon_Active_Projects\3 ProjectStructure\UpdateSequences.bat" copy /Y "A:\1 Amazon_Active_Projects\3 ProjectStructure\UpdateSequences.bat" "%projectRoot%\Renders\UpdateSequences.bat" >nul
 
-:: Create Translations Google Drive shortcut
-echo [InternetShortcut] > "%projectRoot%\Reference\Translation Scripts\Translations Google Drive.url"
-echo URL=https://drive.google.com/drive/folders/1lND5207vl-qf5RbTQ2eejeXJCc4r5rUo >> "%projectRoot%\Reference\Translation Scripts\Translations Google Drive.url"
-
-:: Create Amazon folder shortcut
-powershell -Command "$folder='%projectRoot%\Deliverable'; $WS = New-Object -ComObject WScript.Shell; $SC = $WS.CreateShortcut([System.IO.Path]::Combine($folder, 'Amazon - for Elizabeth.lnk')); $SC.TargetPath = 'D:\Amazon - for Elizabeth'; $SC.WorkingDirectory = 'D:\Amazon - for Elizabeth'; $SC.IconLocation = 'shell32.dll,3'; $SC.Save()"
-
 :: Use repo-provided templates for git config files
 if exist "A:\1 Amazon_Active_Projects\3 ProjectStructure\components\gitignore" copy /Y "A:\1 Amazon_Active_Projects\3 ProjectStructure\components\gitignore" "%projectRoot%\.gitignore" >nul
 if exist "A:\1 Amazon_Active_Projects\3 ProjectStructure\components\gitattributes" copy /Y "A:\1 Amazon_Active_Projects\3 ProjectStructure\components\gitattributes" "%projectRoot%\.gitattributes" >nul