Organize release scripts into Release/ directory

[Copilot]

Moved all ZeaZDev-Release* files from repository root into Release/ directory to reduce top-level clutter.

Changes:

• Relocated 29 release script files (ZeaZDev-Release.sh, ZeaZDev-Release-v5.2.sh through v10.1.sh)
• Preserved git history using git mv
• Replaced placeholder Release/ZeaZDev-Release.sh with actual release script

Result:

Before: 29 release files at repo root
After:  All release files consolidated in Release/

Original prompt

Problem: Move all top-level and matching ZeaZDev-Release* files currently in the repository into a new Release/ directory, preserving original relative paths where necessary to avoid filename collisions. Create a branch named move-release-files (already exists) and commit the file moves to that branch, then open a pull request from move-release-files → main.

Requirements and constraints:

• Target repository: ZeaZDev/ZeaZDev
• Base branch (target for PR): main
• Use branch: move-release-files (if it exists, update it; otherwise create it)
• Move all files whose path basename matches the pattern ZeaZDev-Release* (case-sensitive). This includes files at the repo root and any in subdirectories.
• Preserve original directory structure under the Release/ folder to avoid collisions: for a file at path dir1/dir2/ZeaZDev-Release-foo.sh, move it to Release/dir1/dir2/ZeaZDev-Release-foo.sh. For files at repo root, move to Release/.
• Use git mv (or equivalent) so history is preserved where possible.
• Commit message: "Move ZeaZDev-Release files into Release folder (preserve paths)"
• If any file already exists at the destination path, do not overwrite silently — the script should rename to avoid overwrite by appending a numeric suffix, and record this in the commit message.
• Create a pull request from move-release-files into main with title: "Move ZeaZDev-Release files into Release/" and a description that lists the moved files and notes any renames to avoid collisions.
• Ensure the PR is ready for review and not marked as draft.
• If any errors occur while moving files (permissions, missing files), abort and report the error in the PR description or as a comment on the commit.

Files to move (discovered earlier):

• ZeaZDev-Release.sh (root)
• ZeaZDev-Release-v6.9.sh (root)
• ZeaZDev-Release-v7.0.sh
• ZeaZDev-Release-v7.6.sh
• ZeaZDev-Release-v9.0.sh
• ZeaZDev-Release-v9.1.sh
• ZeaZDev-Release-v9.2.sh
• ZeaZDev-Release-v9.3.sh
• ZeaZDev-Release-v9.4.sh
• ZeaZDev-Release-v10.0.sh
• ZeaZDev-Release-v10.1.sh

Action plan for the coding agent:

1. Checkout or create branch move-release-files based on main.
2. For each file matching pattern ZeaZDev-Release* in the repository (search across the repo):
   a. Determine its current path relative to repo root.
   b. Compute destination path under Release/ preserving directory structure.
   c. If destination path already exists, compute a non-colliding name by appending -1, -2, etc.
   d. Run git mv to move the file to destination.
3. git add / commit with the provided commit message.
4. Push branch move-release-files to origin.
5. Open a pull request from move-release-files → main with the given title and a description listing original -> new paths and any renames or errors.
6. Return the PR URL and list of moved files.

Notes:

• Include the full list of moved files and any renames in the PR description.
• Do not modify file contents beyond moving/renaming.
• If the branch move-release-files already contains previous work (we earlier added Release/ZeaZDev-Release.sh), update it consistently (avoid duplicate moves). Ensure resulting tree contains exactly one copy of each release file under Release/ with preserved paths.

Please perform the actions and report back with the PR URL and summary of changes.

This pull request was created as a result of the following prompt from Copilot chat.

Problem: Move all top-level and matching ZeaZDev-Release* files currently in the repository into a new Release/ directory, preserving original relative paths where necessary to avoid filename collisions. Create a branch named move-release-files (already exists) and commit the file moves to that branch, then open a pull request from move-release-files → main.

Requirements and constraints:

• Target repository: ZeaZDev/ZeaZDev
• Base branch (target for PR): main
• Use branch: move-release-files (if it exists, update it; otherwise create it)
• Move all files whose path basename matches the pattern ZeaZDev-Release* (case-sensitive). This includes files at the repo root and any in subdirectories.
• Preserve original directory structure under the Release/ folder to avoid collisions: for a file at path dir1/dir2/ZeaZDev-Release-foo.sh, move it to Release/dir1/dir2/ZeaZDev-Release-foo.sh. For files at repo root, move to Release/.
• Use git mv (or equivalent) so history is preserved where possible.
• Commit message: "Move ZeaZDev-Release files into Release folder (preserve paths)"
• If any file already exists at the destination path, do not overwrite silently — the script should rename to avoid overwrite by appending a numeric suffix, and record this in the commit message.
• Create a pull request from move-release-files into main with title: "Move ZeaZDev-Release files into Release/" and a description that lists the moved files and notes any renames to avoid collisions.
• Ensure the PR is ready for review and not marked as draft.
• If any errors occur while moving files (permissions, missing files), abort and report the error in the PR description or as a comment on the commit.

Files to move (discovered earlier):

• ZeaZDev-Release.sh (root)
• ZeaZDev-Release-v6.9.sh (root)
• ZeaZDev-Release-v7.0.sh
• ZeaZDev-Release-v7.6.sh
• ZeaZDev-Release-v9.0.sh
• ZeaZDev-Release-v9.1.sh
• ZeaZDev-Release-v9.2.sh
• ZeaZDev-Release-v9.3.sh
• ZeaZDev-Release-v9.4.sh
• ZeaZDev-Release-v10.0.sh
• ZeaZDev-Release-v10.1.sh

Action plan for the coding agent:

1. Checkout or create branch move-release-files based on main.
2. For each file matching pattern ZeaZDev-Release* in the repository (search across the repo):
   a. Determine its current path relative to repo root.
   b. Compute destination path under Release/ preserving directory structure.
   c. If destination path already exists, compute a non-colliding name by appending -1, -2, etc.
   d. Run git mv to move the file to destination.
3. git add / commit with the provided commit message.
4. Push branch move-release-files to origin.
5. Open a pull request from move-release-files → main with the given title and a description listing original -> new paths and any renames or errors.
6. Return the PR URL and list of moved files.

Notes:

• Include the full list of moved files and any renames in the PR description.
• Do not modify file contents beyond moving/renaming.
• If the branch move-release-files already contains previous work (we earlier added Release/ZeaZDev-Release.sh), update it consistently (avoid duplicate moves). Ensure resulting tree contains exactly one copy of each release file under Release/ with preserved paths.

Please perform the actions and report back with the PR URL and summary of changes.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.