chore: Backup local Module-Data-Groups before subtree re-initialization

Author: Tarawally

git-subtree-repo-issue.md

@@ -0,0 +1,17 @@
+I am currently working on a feature branch within my main Git repository, which I refer to as the 'labyrinth' project. My principal objective is to establish and correctly maintain a completely separate project—a **Git Subtree**—inside a specific directory: `projects/code-your-future/Module-Data-Groups`.
+
+**The Key Problem I Created (The 'Dirty' Commit):**
+My fundamental issue arose when I incorrectly packaged my work. I was preparing my Sprint 2 code for a Pull Request, but I mistakenly included file changes and commits that actually belonged to a completely separate assignment, Sprint 3. As a result, my feature branch history contained code for *both* sprints, which is simply unacceptable for the Sprint 2 Pull Request.
+
+**The Fix and The Clean-up:**
+To resolve this, I performed a complex operation: an **interactive rebase**. This is essentially an advanced 'undo' facility that allows one to rewrite history.
+*   I successfully edited the past commits to surgically **remove all traces of the Sprint 3 files and changes**.
+*   This also included sorting out other temporary files and the directory I had created for backup (`...-BACKUP`).
+
+**The Current Situation (The Structural Damage):**
+Whilst my *commit history* is now clean of the Sprint 3 files, the process broke the physical structure of my repository.
+1.  **Misplaced Files:** Key module components, such as the `Sprint-2` directory, were unintentionally moved from their correct subfolder location and dumped directly into the **root** of my main 'labyrinth' repository.
+2.  **Missing Files:** Other necessary framework files for the module (like the main `package.json` or `README.md`) were completely deleted during the rebase process.
+
+**The Critical Constraint:**
+I cannot simply update the module by pulling from its original source (the remote repository). The remote branch itself is 'dirty'—it contains Sprint 3 code and modifications that I was specifically trying to remove. Pulling from it would only re-introduce the problem.