chore(release): v0.5.2

README.md

@@ -93,7 +93,7 @@ PATH is auto-appended to `~/.zshrc` / `~/.bashrc` (open a new shell to pick it u
 Pin a version, change the install location, or skip PATH modification:
 
 ```bash
-curl -fsSL .../install.sh | bash -s -- -v v0.5.1         # pin a version
+curl -fsSL .../install.sh | bash -s -- -v v0.5.2         # pin a version
 INSTALL_ALIAS=mwt bash install.sh                          # avoid the Debian/Ubuntu `mw` clash
 INSTALL_DIR=~/bin bash install.sh                          # install elsewhere
 curl -fsSL .../install.sh | bash -s -- --no-modify-path    # do not touch rc files
@@ -132,17 +132,17 @@ Example:
 ```bash
 # Pick the archive that matches your platform, then verify and unpack it.
 # macOS Apple Silicon:
-curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.1/myworktree_v0.5.1_macOS_arm64.tar.gz
+curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.2/myworktree_v0.5.2_macOS_arm64.tar.gz
 # macOS Intel (replace arch in the filename):
-#   curl -LO .../myworktree_v0.5.1_macOS_amd64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_macOS_amd64.tar.gz
 # Linux amd64:
-#   curl -LO .../myworktree_v0.5.1_Linux_amd64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_Linux_amd64.tar.gz
 # Linux arm64:
-#   curl -LO .../myworktree_v0.5.1_Linux_arm64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_Linux_arm64.tar.gz
 
-curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.1/checksums.txt
+curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.2/checksums.txt
 shasum -a 256 -c checksums.txt --ignore-missing
-tar -xzf myworktree_v0.5.1_macOS_arm64.tar.gz
+tar -xzf myworktree_v0.5.2_macOS_arm64.tar.gz
 
 # Optional: install into PATH
 sudo install -m 755 ./mw /usr/local/bin/mw
@@ -161,7 +161,7 @@ mw --version
 > Or open **System Settings → Privacy & Security** and click "Allow Anyway" for the
 > blocked binaries.
 
-Start from `v0.5.1` or newer for public release binaries. The earlier `v0.1.0` GitHub Release assets were withdrawn after post-release validation uncovered severe terminal interaction issues, and `v0.5.1` is the current recommended public release.
+Start from `v0.5.2` or newer for public release binaries. The earlier `v0.1.0` GitHub Release assets were withdrawn after post-release validation uncovered severe terminal interaction issues, and `v0.5.2` is the current recommended public release.
 
 Each release archive contains `mw`, `myworktree`, `README.md`, `LICENSE`, and `CHANGELOG.md`.
 If you need a platform we do not publish, follow the source build steps below.

README.zh-CN.md

@@ -94,7 +94,7 @@ curl -fsSL https://raw.githubusercontent.com/linletian/myworktree/main/scripts/i
 可指定版本、改安装路径、跳过 PATH 修改：
 
 ```bash
-curl -fsSL .../install.sh | bash -s -- -v v0.5.1         # 指定版本
+curl -fsSL .../install.sh | bash -s -- -v v0.5.2         # 指定版本
 INSTALL_ALIAS=mwt bash install.sh                          # 避开 Debian/Ubuntu 的 `mw` 占用
 INSTALL_DIR=~/bin bash install.sh                          # 装到自定义目录
 curl -fsSL .../install.sh | bash -s -- --no-modify-path    # 不改 rc 文件
@@ -130,17 +130,17 @@ curl -fsSL .../install.sh | bash -s -- -v vX.Y.Z-beta.N
 ```bash
 # 根据你的平台选择对应压缩包，然后校验并解压
 # macOS Apple Silicon：
-curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.1/myworktree_v0.5.1_macOS_arm64.tar.gz
+curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.2/myworktree_v0.5.2_macOS_arm64.tar.gz
 # macOS Intel（替换文件名中的架构字段）：
-#   curl -LO .../myworktree_v0.5.1_macOS_amd64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_macOS_amd64.tar.gz
 # Linux amd64：
-#   curl -LO .../myworktree_v0.5.1_Linux_amd64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_Linux_amd64.tar.gz
 # Linux arm64：
-#   curl -LO .../myworktree_v0.5.1_Linux_arm64.tar.gz
+#   curl -LO .../myworktree_v0.5.2_Linux_arm64.tar.gz
 
-curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.1/checksums.txt
+curl -LO https://github.com/linletian/myworktree/releases/download/v0.5.2/checksums.txt
 shasum -a 256 -c checksums.txt --ignore-missing
-tar -xzf myworktree_v0.5.1_macOS_arm64.tar.gz
+tar -xzf myworktree_v0.5.2_macOS_arm64.tar.gz
 
 # 可选：安装到 PATH
 sudo install -m 755 ./mw /usr/local/bin/mw
@@ -157,7 +157,7 @@ mw --version
 > ```
 > 或在 **系统设置 → 隐私与安全性** 中为被阻止的二进制文件点击"仍要打开"。
 
-建议从 `v0.5.1` 或更新版本开始使用公开发布版二进制。更早的 `v0.1.0` GitHub Release 资产在补充实测中发现严重终端交互问题后已撤回，而 `v0.5.1` 是当前推荐的公开发布版本。
+建议从 `v0.5.2` 或更新版本开始使用公开发布版二进制。更早的 `v0.1.0` GitHub Release 资产在补充实测中发现严重终端交互问题后已撤回，而 `v0.5.2` 是当前推荐的公开发布版本。
 
 每个发布压缩包内都包含 `mw`、`myworktree`、`README.md`、`LICENSE` 和 `CHANGELOG.md`。
 如果你的平台暂无对应产物，就直接使用下面的源码编译步骤。

RELEASING.md

@@ -48,7 +48,7 @@ One commit, `chore(release): prepare vX.Y.Z`, touching **only**:
 
 | File | Change |
 |---|---|
-| `CHANGELOG.md` | Rename `## Unreleased` → `## vX.Y.Z (YYYY-MM-DD)` with a one-line release summary under it; keep an empty `## Unreleased` placeholder at the top. **Audit the delta for PRs that shipped without a CHANGELOG entry** (`git log --oneline <prev-tag>..develop` / merged PR list) and add the missing entries in house style (bold title — em-dash — detail — `Pinned by TestName`). |
+| `CHANGELOG.md` | Rename `## Unreleased` → `## vX.Y.Z (YYYY-MM-DD)` with a one-line release summary under it; keep an empty `## Unreleased` placeholder at the top. **Audit the delta for PRs that shipped without a CHANGELOG entry** (`git log --oneline <prev-tag>..develop` / merged PR list) and add the missing entries in house style (bold title — em-dash — detail — `Pinned by TestName`). House rule (issue #95, also in an HTML comment at the top of the file): the phrase "Pinned by N `node --test` cases" declares the TOTAL case count of `internal/ui/testdata/terminal_status.test.mjs` and EVERY occurrence must equal it — when the count grows, bump them all; use different phrasing for subset counts. |
 | `README.md` | Bump every `vA.B.C` string: download URLs, example tarball names, `-v` pin example, "current recommended public release" wording. |
 | `README.zh-CN.md` | Same sweep as `README.md`. |
 | `scripts/install.sh` | Bump the `-v` example version strings in the header/usage comments. |