docs: update release tag instructions for v2.0.1 in root README.md

README.md

@@ -372,8 +372,8 @@ Releases can be built and published through three complementary channels:
 ### 1. Tag Push Automation (Gitea Actions)
 Pushing a release tag automatically triggers the build workflows:
 ```bash
-git tag v2.0.0
-git push origin v2.0.0
+git tag v2.0.1
+git push origin v2.0.1
 ```
 The consolidated workflow **`release.yml`** defines two parallel jobs:
 - **`release-linux`** (`ubuntu-latest`): Compiles standalone native ELF binaries (`Linux_Client.bin`, `Server.bin`) and checksums.
@@ -382,7 +382,7 @@ The consolidated workflow **`release.yml`** defines two parallel jobs:
 ### 2. Manual Workflow Dispatch (Gitea UI)
 Workflows can be manually triggered on demand from the Gitea web interface:
 1. Navigate to **Actions** $\rightarrow$ **Release Binaries & Installers** (`release.yml`).
-2. Click **Run workflow**, set the release tag (defaults to `v2.0.0`), and run.
+2. Click **Run workflow**, set the release tag (defaults to `v2.0.1`), and run.
 
 ### 3. Native Local Windows Build & Direct Release Upload
 For environments without a registered Windows CI runner, Windows executables can be built and published directly to Gitea releases:
@@ -391,5 +391,5 @@ For environments without a registered Windows CI runner, Windows executables can
 python compilation/package_dist.py --target windows
 
 # 2. Upload assets and release notes directly to the Gitea release
-python compilation/upload_release.py --tag v2.0.0 --token <GITEA_TOKEN> --skip-build
+python compilation/upload_release.py --tag v2.0.1 --token <GITEA_TOKEN> --skip-build
 ```