feature request: deep copy when users have existing workflows #1
Description
Problem - existing workflows
The install via copy is great, but if the user has existing workflows with collisions, then what? user has to copy each subdir individually. this is likely if a user is getting to the point of searching for this product, then there's a good chance they've tried various workflows and have things they like/dislike.
Proposed solution
script to deep copy the directory
Edge case: slash collisions
if a user happens to already have a slash command that matches the windloop commands, then what?
Possible solutions
windloop renames - would need to build an alias directory of some sort
ask user to change - easiest for starts, but not user friendly. Maybe do this initially and we can build another issue for v2
use user's script - rename the windloop script, let the user know we did it and suggest that they merge the two
AI merge - see if the user's script is compatible or similar (might be if names collide). This could be via searching for conflicting instructions, or could be via summary of intents and combine based on core vs config/tweaks.
priority based behavior - if it's a script that is core to windloop, stop and let the user know about the conflict. if it's not core, then AI merge etc.