README: update examples to v2.0.1

Author: Cod-e-Codes

README.md

@@ -9,9 +9,9 @@ Plugins are now distributed as a single binary targeted to a specific platform (
 - Expected archive name: `PLUGIN-NAME-v<version>-<goos>-<goarch>.zip`
 - Inside the archive: the single plugin binary (`.exe` on Windows), an optional `plugin.json` manifest, and a `README.md`.
 - Examples:
-  - `echo-plugin-v1.0.0-windows-amd64.zip`
-  - `echo-plugin-v1.0.0-linux-amd64.zip`
-  - `echo-plugin-v1.0.0-darwin-arm64.zip`
+  - `echo-plugin-v2.0.1-windows-amd64.zip`
+  - `echo-plugin-v2.0.1-linux-amd64.zip`
+  - `echo-plugin-v2.0.1-darwin-amd64.zip`
 
 If a user installs a plugin binary for the wrong platform, the host will refuse to start the plugin and display a helpful message indicating the required `GOOS/GOARCH`.
 
@@ -36,9 +36,9 @@ Or install directly:
 When publishing a new plugin release, build and upload one archive per target platform and provide the corresponding checksums. A typical process:
 
 1. Build platform-specific archives (see `plugins/echo/README.md` for examples and scripts):
-   - `echo-plugin-v2.0.0-windows-amd64.zip`
-   - `echo-plugin-v2.0.0-linux-amd64.zip`
-   - `echo-plugin-v2.0.0-darwin-amd64.zip`
+   - `echo-plugin-v2.0.1-windows-amd64.zip`
+   - `echo-plugin-v2.0.1-linux-amd64.zip`
+   - `echo-plugin-v2.0.1-darwin-amd64.zip`
 2. Compute SHA-256 checksums and publish alongside the archives.
 3. Update `registry.json` to point to the platform-specific archive you intend to distribute for your audience. The host will still validate at runtime and show errors on mismatch.