dsh-android v0.1.0-rc.4

dsh-android v0.1.0-rc.4

Windows 兼容审计版：rc.3 修完两个 Windows issue 后又通盘扫了一遍，抓出最后一个平台雷。/ The Windows-compatibility audit release: one more platform landmine caught by the sweep that followed rc.3's two Windows fixes.

🐛 修复 / Fixed

• android_logs 的 follow 模式在 Windows 上必然报错 / Follow-mode logcat always errored on Windows — 限时实时捕获靠给 adb 子进程的进程组发信号收尾（process.kill(-pid)），而 Windows 没有进程组、负 PID 直接抛异常：每个 follow 窗口都以错误告终而不是返回日志。win32 上 adb.exe 是单个客户端进程，现在改为非 detached 启动 + 普通 child.kill()（TerminateProcess）收尾，设备侧 logcat 随传输一起结束。回归测试 stub process.platform 断言窗口干净关闭且子进程确被收割。/ The bounded live capture ended by signalling the adb child's process group — but Windows has no process groups and a negative-PID kill THROWS, so every follow window errored out. On win32 the child now spawns undetached and is reaped with plain child.kill(); regression steps stub the platform and assert both the clean close and the reap marker.

✅ 审计结论 / Audit verdict

其余路径确认 Windows 安全：adb 发现（rc.3 起识别 .exe、LOCALAPPDATA SDK 路径、PATH 双名候选）、宿主侧路径全走 join/sep、adb shell 输出 CRLF 归一、截图/流走二进制安全的 exec-out、OCR 在非 macOS 宿主给出解释性错误而非崩溃。设备枚举 → boot → 实时流 → 侧栏面板的全链路已有 Windows 10 + LDPlayer 的真实用户验证（#1）。/ Everything else checked out: discovery (.exe since rc.3, LOCALAPPDATA, dual PATH candidates), join/sep paths throughout, CRLF-normalized shell output, binary-safe exec-out capture, and an explanatory non-macOS OCR refusal. The full devices → boot → stream → panel chain has real-user validation on Windows 10 + LDPlayer (#1).

📦 安装 / Install

dsh plugin --profile web add @zseven-w/dsh-android@next
dsh web

Full Changelog: v0.1.0-rc.3...v0.1.0-rc.4