Git Wortree Set Up & Spawn Orchestrator

New functionalities

• The spawn command is now connected to the orchestrator in the package.json so that it can later be publish in npm and make it fully global accessible in the developer system by using the -g flag
• Config changes memory: Every time the system changes the system-config.json the changes are automatically staged and commit so that they are present in the new worktree

Testing

• Created two integration automated test using jest that stress test the spawn engine under different scenarios and flags, implement a cool ghost typist so that no questions arise why testing, since those are handle by the ghost typist and test itself.
• Performed an e2e test in an isolated enviroment within my computer, finding some bugs and fixing them properly. (The video shows the e2e test in action)

Fixes

• The system faced a config path mismatch when the command was trigger when the worktree was outside of a prefix folder and then moved to it, making the config file ENOENT.

e2e test

e2e spawn engine in action

1. Create a folder with the prefix if not previously created and move the main worktree dir and other worktrees present there
2. Handle the config-system.json presence if not handle its creation
3. Create a new worktree with the artifact in lowercase as name and branch to work within the folder with the project identifier prefix
4. Connect the docs of the new worktree to the folder in the markdown editor
5. Open a VS code instance