Fix config isolation, directional network metrics, and AeDebug launch

Cargo.toml

@@ -2,7 +2,7 @@
 # 这里定义包名、版本、发布构建策略，以及 Win32 API 绑定所需的功能开关。
 [package]
 name = "taskmgr-rs"
-version = "0.2.5"
+version = "0.2.6"
 authors = ["taskmgr-rs contributors"]
 description = "A classic Windows Task Manager built in Rust with native Win32 APIs."
 license = "MIT"

README.md

@@ -79,9 +79,10 @@ Pull requests and pushes to `main` run formatting, all-target checks, strict Cli
 x86_64 release build on GitHub's Windows Server 2025 / Visual Studio 2026 runner. Separate jobs
 compile i686 and ARM64; i686 tests also run under WOW64.
 
-To publish a version, first update `Cargo.toml` and `Cargo.lock`, merge the change, then push the
-matching tag such as `v0.2.5`. The Release workflow rejects a tag that does not exactly match the
-Cargo package version. It builds all three architectures in parallel, verifies the PE machine and
+To publish a version, update `Cargo.toml` and `Cargo.lock` together and merge the change to `main`.
+The Release workflow reads the package version and automatically creates the matching tag (for
+example `v0.2.6`) when it does not exist. It then builds all three architectures in parallel,
+verifies the PE machine and
 Windows version resources, writes `SHA256SUMS.txt`, creates GitHub build-provenance attestations,
 and publishes only after the uploaded sizes and digests match. A publishing failure leaves only a
 draft; a build failure creates no release, so neither path exposes a partial release.

README.zh-CN.md

@@ -79,8 +79,8 @@ Pull Request 和推送到 `main` 的提交会在 GitHub 的 Windows Server 2025
 runner 上执行格式检查、全目标 check、严格 Clippy、完整测试和 x86_64 release 构建。独立任务
 同时验证 i686 与 ARM64，i686 测试会在 WOW64 下实际执行。
 
-发布版本时，先同步修改 `Cargo.toml` 与 `Cargo.lock` 并合入主线，再推送与版本完全一致的 tag，
-例如 `v0.2.5`。Release 工作流会拒绝与 Cargo 包版本不一致的 tag，并行构建三种架构，核对 PE
+发布版本时，只需同步修改 `Cargo.toml` 与 `Cargo.lock` 并合入 `main`。Release 工作流会读取包
+版本；如果对应 tag（例如 `v0.2.6`）尚不存在，就自动创建 tag，并行构建三种架构，核对 PE
 机器类型和 Windows 版本资源，生成 `SHA256SUMS.txt` 与 GitHub 构建来源证明。只有 GitHub
 服务器上的资产大小和摘要都与本地一致时才公开 Release。发布阶段失败时只保留草稿，构建
 阶段失败时不会创建 Release，因此都不会暴露不完整发布。