@logicseek/hello-cc 0.1.7 → 0.1.9

package/CHANGELOG.md

@@ -16,6 +16,113 @@ the release description from the current changelog section. Use
 `npm run release:github` with `GH_TOKEN` or `GITHUB_TOKEN` only for local
 backfills.
 
+## 0.1.9
+
+### Summary
+
+hello-cc 0.1.9 publishes the post-0.1.8 Web runtime and provider shim
+hardening work. It tightens Web peer action identity, makes runtime cleanup
+safer, and keeps Claude/Codex shims from attaching unrelated projects to a
+global Web runtime.
+
+### Highlights
+
+- Hardened Web runtime cleanup so starting `hcc web` from a wrapper shell does
+  not terminate the current parent process chain while still removing stale
+  orphan runtimes for the same project.
+- Returned structured `BAD_REQUEST` JSON for malformed Web API request bodies
+  instead of surfacing raw JSON parse failures.
+- Replaced Web-runtime-token reuse for mutating peer actions with independent
+  per-session action tokens.
+- Changed provider shims to fall back to the real Claude/Codex CLI when no
+  current-project Web runtime is available.
+- Made provider shims use only the current project's `.hello-cc/runtime.json`
+  during managed launches, avoiding accidental attachment through a global Web
+  runtime from another project.
+- Kept shim-only environment variables out of restarted provider sessions.
+
+### Compatibility Notes
+
+- No breaking CLI command changes are intended in this release.
+- `hcc web --local` is still Web mode; use `hcc up` when you only want local
+  coordination commands without the Web console or shims.
+- Starting `claude` or `codex` in a directory without a local
+  `.hello-cc/runtime.json` now runs the real provider CLI instead of implicitly
+  using a global hello-cc Web runtime.
+
+### Validation
+
+The 0.1.9 release should be validated with:
+
+```bash
+git diff --check
+node --check bin/hcc.mjs
+find lib -name '*.mjs' -print0 | xargs -0 -n1 node --check
+node --check scripts/github-release.mjs
+node --check scripts/regression.mjs
+node --check scripts/release-notes.mjs
+npm run release:check
+npm run release:github:dry-run -- --version 0.1.9
+npm pack --dry-run --json
+npm publish --dry-run --registry=https://registry.npmjs.org/ --access public
+npm test
+```
+
+The expected full regression marker is:
+
+```text
+FULL_REGRESSION_OK
+```
+
+## 0.1.8
+
+### Summary
+
+hello-cc 0.1.8 is a targeted patch release for Claude/Codex shim
+self-repair. It fixes generated shims that could stay pinned to a removed
+provider binary after Claude or Codex was reinstalled.
+
+### Highlights
+
+- Fixed `hcc shim ensure` so it only reuses an existing `# Real binary:` path
+  when that binary still exists.
+- Preserved the existing fast path for valid generated shims while falling back
+  to the requested binary or rediscovering the provider from `PATH` when the
+  recorded path is stale.
+- Added regression coverage for the reinstall case where a generated shim
+  points at a deleted provider binary but a working provider is available on
+  `PATH`.
+
+### Compatibility Notes
+
+- No CLI command or package surface changes are intended in this release.
+- Existing generated shims will self-heal on the next `hcc shim ensure` or shim
+  launch when their recorded provider binary has disappeared.
+
+### Validation
+
+The 0.1.8 release should be validated with:
+
+```bash
+git diff --check
+node --check bin/hcc.mjs
+find lib -name '*.mjs' -print0 | xargs -0 -n1 node --check
+node --check scripts/github-release.mjs
+node --check scripts/regression.mjs
+node --check scripts/release-notes.mjs
+npm run release:check
+npm run release:github:dry-run -- --version 0.1.8
+npm pack --dry-run --json
+npm publish --dry-run --registry=https://registry.npmjs.org/ --access public
+npm test
+```
+
+The expected full regression marker is:
+
+```text
+FULL_REGRESSION_OK
+```
+
 ## 0.1.7
 
 ### Summary

package/README.md

@@ -49,7 +49,12 @@ doing.
 
 ## Install And Manage
 
-Node.js 24 or newer is required.
+hello-cc supports Linux and macOS. Node.js 24 or newer is required, and
+browser-controllable terminals require `tmux`. Native Windows shells are not
+currently supported; use WSL for a Linux-like environment.
+
+Linux has richer process auto-discovery through `/proc`. On macOS, use
+hello-cc shims or `hcc peer start` for reliable tmux-managed terminal sessions.
 
 ```bash
 npm install -g @logicseek/hello-cc
@@ -67,7 +72,7 @@ Or run it without a global install:
 npx @logicseek/hello-cc web
 ```
 
-Remove hooks and shims from this machine:
+Remove hooks, shims, and the shell PATH entry from this machine:
 
 ```bash
 hcc uninstall
@@ -102,12 +107,16 @@ local: http://127.0.0.1:8787/?token=<saved-token>&project=/path/to/project
 Use `--local` to bind only to `127.0.0.1`, or `--port N` to request a specific
 port. `hcc web` initializes the project bus, installs Claude/Codex hooks and
 shims, starts or reuses the Web console, and returns the terminal to you.
+`hcc web --local` is still Web mode; it only limits the listener to loopback.
+Use `hcc up` when you want local coordination commands without the Web console
+or shims.
 
-After the first shim install, open a new terminal or reload your shell:
+After the first shim install, open a new terminal or reload the rc file for
+your shell:
 
-```bash
-source ~/.bashrc
-```
+- bash: `source ~/.bashrc`
+- zsh: `source ~/.zshrc`
+- fish: `source ~/.config/fish/config.fish`
 
 Start normal agent sessions from the project:
 
@@ -119,7 +128,11 @@ codex resume <session-id>
 ```
 
 Those sessions become tmux-backed peers that can be seen and controlled from
-Web while remaining usable from the local terminal.
+Web while remaining usable from the local terminal. The shims only use the
+current project's runtime file. If you start `claude` or `codex` in a directory
+where `hcc web` has not created `.hello-cc/runtime.json`, the shim falls back to
+the real provider CLI instead of using the global Web runtime or creating a new
+project database.
 
 ## Basic Workflow
 

package/README.zh-CN.md

@@ -38,7 +38,11 @@
 
 ## 安装和维护
 
-需要 Node.js 24 或更新版本。
+hello-cc 支持 Linux 和 macOS。需要 Node.js 24 或更新版本；可被浏览器控制的
+终端需要 `tmux`。当前不支持原生 Windows shell；Windows 用户建议使用 WSL。
+
+Linux 可以通过 `/proc` 做更完整的进程自动发现。macOS 上建议通过 hello-cc
+shim 或 `hcc peer start` 启动会话，以获得可靠的 tmux 托管终端。
 
 ```bash
 npm install -g @logicseek/hello-cc
@@ -56,7 +60,7 @@ hcc update
 npx @logicseek/hello-cc web
 ```
 
-移除本机 hooks 和 shims：
+移除本机 hooks、shims 和 shell PATH 配置：
 
 ```bash
 hcc uninstall
@@ -90,12 +94,14 @@ local: http://127.0.0.1:8787/?token=<saved-token>&project=/path/to/project
 使用 `--local` 可以只绑定 `127.0.0.1`，使用 `--port N` 可以指定请求端口。
 `hcc web` 会初始化项目总线，安装 Claude/Codex hooks 和 shims，启动或复用 Web
 控制台，然后把终端还给你。
+`hcc web --local` 仍然是 Web 模式，只是限制监听在本机 loopback。只想使用本地
+协作命令、不启动 Web 控制台、不安装 shims 时，使用 `hcc up`。
 
-第一次安装 shim 后，打开新终端或重新加载 shell：
+第一次安装 shim 后，打开新终端，或根据当前 shell 重新加载配置：
 
-```bash
-source ~/.bashrc
-```
+- bash: `source ~/.bashrc`
+- zsh: `source ~/.zshrc`
+- fish: `source ~/.config/fish/config.fish`
 
 在项目目录中正常启动 agent：
 
@@ -107,6 +113,9 @@ codex resume <session-id>
 ```
 
 这些会话会成为 tmux-backed peer，可以继续在本地终端里使用，也可以被 Web 控制台观察和操作。
+shim 只使用当前项目自己的 runtime 文件。如果你在没有通过 `hcc web` 创建
+`.hello-cc/runtime.json` 的目录里启动 `claude` 或 `codex`，shim 会回退到真实
+provider CLI，不会使用全局 Web runtime，也不会为这个目录新建项目数据库。
 
 ## 基本流程