@logicseek/hello-cc 0.1.0 → 0.1.2

package/docs/guide.md

@@ -0,0 +1,339 @@
+# hello-cc User Guide
+
+This guide covers the practical workflow for installing, starting, and using
+hello-cc. For a compact command list, use the [Command Reference](commands.md).
+
+## Install, Update, And Uninstall
+
+Install hello-cc globally:
+
+```bash
+npm install -g @logicseek/hello-cc
+```
+
+Update an existing global install:
+
+```bash
+hcc update
+```
+
+`hcc update` runs `npm install -g @logicseek/hello-cc@latest`. Use
+`hcc update --help` to see the available update options. `hcc task update`
+updates a coordination task, not the installed package.
+
+Remove hooks and shims from this machine:
+
+```bash
+hcc uninstall
+```
+
+Remove the current project's `.hello-cc` data and guidance blocks too:
+
+```bash
+hcc uninstall --purge --yes
+```
+
+Remove the global npm package:
+
+```bash
+npm uninstall -g @logicseek/hello-cc
+```
+
+## Default Entry
+
+Run one command in the project directory:
+
+```bash
+cd /path/to/project
+hcc web
+```
+
+`hcc web` automatically:
+
+1. Initializes `.hello-cc/mesh.db` in the current directory
+2. Writes bounded guidance blocks: `.hello-cc/HCC.md`, `CLAUDE.md`, `AGENTS.md`
+3. Installs or refreshes Claude Code hooks: `~/.claude/settings.json`
+4. Installs or refreshes Codex hooks: `~/.codex/hooks.json`
+5. Installs `~/.hcc-shims/claude` and `~/.hcc-shims/codex`
+6. Adds `~/.hcc-shims` to the shell PATH
+7. Ensures `tmux` is available, with best-effort automatic install and a clear
+   install command if that fails
+8. Starts or reuses the global web console, registers the current project,
+   prints URL/PID/runtime/log, then returns the terminal to you
+
+Example output:
+
+```text
+hello-cc web started in background
+pid: 12345
+project: /path/to/project
+database: /path/to/project/.hello-cc/mesh.db
+runtime: /path/to/project/.hello-cc/runtime.json
+log: /path/to/project/.hello-cc/web.log
+open: http://<machine-ip>:8787/?project=%2Fpath%2Fto%2Fproject
+local: http://127.0.0.1:8787/?project=%2Fpath%2Fto%2Fproject
+shims: installed claude, codex
+PATH updated in ~/.bashrc; open a new terminal or source it
+stop: hcc down
+```
+
+`hcc web` uses a single global web runtime. Running `hcc web` again from
+another project directory does not open another port; it registers that project
+with the same web console. The frontend Project selector switches between
+registered roots. Each project still keeps its own `.hello-cc/mesh.db`, so
+tasks, messages, locks, and peers stay isolated.
+
+After the first shim install, open a new terminal or run:
+
+```bash
+source ~/.bashrc
+```
+
+Then direct project-local commands are wrapped automatically:
+
+```bash
+claude
+codex
+claude --resume <session-id>
+codex resume <session-id>
+```
+
+The wrappers create or reuse local persistent tmux terminals:
+
+- The local terminal attaches to the same tmux session and remains usable.
+- The web console controls the same tmux pane, not a temporary browser-only
+  terminal.
+- `hcc down` stops only the web runtime. It does not kill tmux sessions.
+- Running `hcc web` again reattaches live recorded tmux panes.
+
+For local coordination without Web or shims, use:
+
+```bash
+hcc up
+```
+
+Most users should start with `hcc web`.
+
+## Project Boundary
+
+By default, the project boundary is the current working directory. If the
+current directory has no `.hello-cc/mesh.db`, hello-cc creates one on first use:
+
+```text
+/repo-a/.hello-cc/mesh.db
+/repo-a/subdir/.hello-cc/mesh.db
+```
+
+Those are two different projects by default. Sessions communicate naturally
+when they start from the same project path.
+
+To share one bus across paths or worktrees, opt in explicitly:
+
+```bash
+hcc --root /path/to/project web
+export HCC_ROOT=/path/to/project
+export HCC_DB=/path/to/project/.hello-cc/mesh.db
+```
+
+hello-cc does not automatically inherit a parent directory's bus. That avoids
+subdirectory sessions joining a broader project by accident.
+
+## Communication Model
+
+hello-cc is not point-to-point CLI messaging and does not require MCP. The core
+is a project-local SQLite WAL bus:
+
+```text
+Claude/Codex/plain shell
+  -> hooks / hcc commands / web runtime
+  -> .hello-cc/mesh.db
+  -> peers / tasks / messages / locks / handoffs / events
+  -> tmux-backed terminal control
+```
+
+Tasks and messages have different read semantics:
+
+- Tasks are project facts. Every peer sees tasks until they become `done` or
+  `abandoned`.
+- Messages are addressed mailbox items. `hcc msg inbox` defaults to unread
+  messages for the current peer, and `hcc msg ack` records per-peer read state.
+- `ask` and `broadcast` write durable messages. With `--inject`, they also send
+  live input to runtime-attached terminals.
+- Locks use SQLite transactions and TTLs. They are coordination locks, not a
+  filesystem sandbox.
+
+## How Claude/Codex Knows Other Sessions
+
+The primary path is hook injection, not `CLAUDE.md`.
+
+`hcc web` installs Claude Code and Codex hooks. On session start, user prompt
+submit, tool events, and idle events, hooks inject the current hello-cc snapshot
+into the model context:
+
+- current peer identity
+- active peer list
+- open tasks
+- unread messages for the current peer
+- active locks
+- suggested commands such as `hcc status`, `hcc peers`, `hcc task list`,
+  `hcc msg inbox`, and `hcc lock list`
+
+When an attached Claude/Codex session is asked what other sessions are doing,
+it should answer from the latest hello-cc state instead of generic isolation
+knowledge.
+
+If a session still says it cannot know, likely causes are:
+
+- `hcc web` has not been run in the project directory
+- the terminal has not loaded `~/.hcc-shims` into PATH
+- Codex hooks are not enabled or the installed hook has not been trusted in
+  Codex's hook review flow
+- the CLI was started in a different project directory
+- the session was an already-open raw terminal before hello-cc was installed
+- the provider CLI version did not fire the expected hook
+
+To verify Claude Code hook injection directly, run a one-shot debug call from
+the same project:
+
+```bash
+claude -p 'Do you see hello-cc open tasks?' --debug hooks --debug-file /tmp/hcc-claude-hooks.log
+```
+
+The debug log should contain `Hook UserPromptSubmit ... provided
+additionalContext` and the `hello-cc coordination` block.
+
+## Web Console
+
+Start local and LAN-visible control:
+
+```bash
+hcc web
+```
+
+Use a token only when you want one:
+
+```bash
+HCC_WEB_TOKEN='choose-a-long-token' hcc web --host 0.0.0.0 --port 8787
+```
+
+Open from another machine on the same network:
+
+```text
+http://<machine-ip>:8787/
+```
+
+The web console can:
+
+- switch between multiple registered project roots on one port
+- register another project path from the browser
+- show project state: peers, tasks, messages, locks, handoffs, events
+- operate local terminals: start Claude/Codex/shell, send keyboard input, view
+  output, detach runtime control
+
+Browser-controlled sessions are local tmux terminals:
+
+- sessions started by the web form
+- sessions started by `hcc peer start`
+- direct `claude` / `codex` sessions started through shims
+- existing tmux panes attached with `hcc peer attach`
+
+Already-open raw terminals cannot be captured or controlled unconditionally
+unless they started under tmux, screen, or a hello-cc shim. They can still
+participate in tasks, messages, and locks through hooks and `hcc` commands.
+
+## Command Reference
+
+Use `hcc --help` for the command list and `hcc <command> --help` for a specific
+command. The maintained summary lives in the [Command Reference](commands.md).
+
+## Stable Peer Identity
+
+hello-cc tries to keep peer IDs stable across resumed sessions:
+
+| Launch pattern | Peer ID |
+|---|---|
+| `claude --resume abc12345...` | `claude-abc12345` |
+| `claude --session-id abc12345...` | `claude-abc12345` |
+| `claude --continue` | terminal-derived ID first, then hooks record real session metadata |
+| `claude --fork-session --resume abc12345...` | terminal-derived ID first, then hooks record new session metadata |
+| `codex resume abc12345...` | `codex-abc12345` |
+| `codex resume --last` | terminal-derived ID first, then discovery records real session metadata |
+| plain shell | `shell-<terminal>` |
+| manual `HCC_PEER=xxx` | uses `xxx` |
+
+Known resume IDs keep the same peer ID after restart. Launch modes that do not
+expose the real provider session ID before startup use a terminal-derived ID
+first, then record provider metadata after hooks or discovery run.
+
+## Typical Workflow
+
+Create a task:
+
+```bash
+hcc task create --title "Refactor router diagnostics" \
+  --body "Keep changes scoped." --priority 20
+```
+
+Claim and lock:
+
+```bash
+hcc task next
+hcc lock acquire --resource vllm/router --ttl 900 --reason "implement diagnostics"
+```
+
+Message or inject:
+
+```bash
+hcc msg send --to claude-a --body "Implementation is ready for review."
+hcc ask claude-a "Please review the current implementation." --inject
+hcc broadcast "Pause edits under vllm/router until this task finishes." --inject
+```
+
+Finish with a handoff:
+
+```bash
+hcc handoff create --to claude-a \
+  --summary "Implemented router diagnostics changes." \
+  --tests "pytest tests/router" \
+  --risks "Full benchmark not run"
+
+hcc task done --id 1 --summary "Done and handed off."
+hcc lock release --resource vllm/router
+```
+
+## Environment Variables
+
+| Variable | Purpose |
+|---|---|
+| `HCC_PEER` | default peer identity |
+| `HCC_ROOT` | override project root |
+| `HCC_DB` | override database path |
+| `HCC_WEB_TOKEN` | optional token for web access |
+| `HCC_RUNTIME_URL` | direct runtime URL |
+| `HCC_NO_AUTO_INSTALL_TMUX=1` | disable tmux auto-install, mainly for tests |
+
+The `claude` / `codex` shims and `hcc peer start` create tmux-backed sessions
+from the environment of the local terminal that launched them, not from the
+older environment of the background web runtime. This lets you open a new
+terminal, export provider variables such as `ANTHROPIC_*` or
+`CLAUDE_CODE_*`, then run `claude` / `codex`.
+
+An already-running CLI process cannot have its environment changed in place by
+the operating system. The `claude` / `codex` shims call `hcc peer start` with
+`--restart-env`, so hello-cc records a launch environment fingerprint for the
+same resume/session peer. If you start that peer again from a new terminal and
+the environment changed, hello-cc automatically restarts the tmux session with
+the new environment when there are no attached tmux clients or Web clients. If
+the session is actively attached, hello-cc asks you to detach/close Web clients
+or run `hcc peer stop <peer>` before starting it again.
+
+When you call `hcc peer start` directly, add `--restart-env` if you want the
+same restart-on-environment-change behavior.
+
+The shims only manage interactive terminal sessions. Metadata and maintenance
+commands pass through to the real provider CLI, including `claude --help`,
+`claude --version`, `claude --print`, `claude --bare`, `claude --safe-mode`,
+`codex --help`, `codex --version`, and non-interactive Codex subcommands such as
+`codex exec`, `codex review`, `codex doctor`, and `codex mcp`. Interactive
+`claude`, `claude --resume ...`, `codex`, `codex resume ...`, and `codex fork
+...` are tmux-backed and visible in the Web console.

package/docs/guide.zh-CN.md

@@ -0,0 +1,292 @@
+# hello-cc 用户指南
+
+这份文档说明安装、启动和日常使用流程。紧凑命令清单见
+[命令参考](commands.zh-CN.md)。
+
+## 安装、更新和卸载
+
+全局安装 hello-cc：
+
+```bash
+npm install -g @logicseek/hello-cc
+```
+
+更新已有的全局安装：
+
+```bash
+hcc update
+```
+
+`hcc update` 会执行 `npm install -g @logicseek/hello-cc@latest`。使用
+`hcc update --help` 可以查看更新选项。`hcc task update` 更新的是协作任务状态，不是安装包版本。
+
+移除本机 hooks 和 shims：
+
+```bash
+hcc uninstall
+```
+
+同时移除当前项目的 `.hello-cc` 数据和指导块：
+
+```bash
+hcc uninstall --purge --yes
+```
+
+移除全局 npm 包：
+
+```bash
+npm uninstall -g @logicseek/hello-cc
+```
+
+## 默认入口
+
+在项目目录运行：
+
+```bash
+cd /path/to/project
+hcc web
+```
+
+`hcc web` 会自动完成：
+
+1. 在当前目录初始化 `.hello-cc/mesh.db`
+2. 写入受控项目指导块：`.hello-cc/HCC.md`、`CLAUDE.md`、`AGENTS.md`
+3. 安装或刷新 Claude Code hooks：`~/.claude/settings.json`
+4. 安装或刷新 Codex hooks：`~/.codex/hooks.json`
+5. 安装 `~/.hcc-shims/claude` 和 `~/.hcc-shims/codex`
+6. 将 `~/.hcc-shims` 加入 shell PATH
+7. 检查 `tmux`，缺失时尽量自动安装；安装失败会打印明确的系统安装命令
+8. 后台启动或复用全局 Web 控制台，注册当前项目，打印 URL、PID、runtime 文件和日志文件，然后把当前终端还给用户
+
+输出示例：
+
+```text
+hello-cc web started in background
+pid: 12345
+project: /path/to/project
+database: /path/to/project/.hello-cc/mesh.db
+runtime: /path/to/project/.hello-cc/runtime.json
+log: /path/to/project/.hello-cc/web.log
+open: http://<machine-ip>:8787/?project=%2Fpath%2Fto%2Fproject
+local: http://127.0.0.1:8787/?project=%2Fpath%2Fto%2Fproject
+shims: installed claude, codex
+PATH updated in ~/.bashrc; open a new terminal or source it
+stop: hcc down
+```
+
+`hcc web` 使用单个全局 Web runtime。你在另一个项目目录再次运行 `hcc web` 时，不会再开一个端口，而是把那个项目注册到同一个 Web 控制台。前端 Project 下拉框可以在不同项目 root 之间切换；每个项目仍然使用自己的 `.hello-cc/mesh.db`，任务、消息、锁和 peers 不会混在一起。
+
+第一次安装 shim 后，需要打开一个新终端，或执行：
+
+```bash
+source ~/.bashrc
+```
+
+之后在这个项目目录中直接输入：
+
+```bash
+claude
+codex
+claude --resume <session-id>
+codex resume <session-id>
+```
+
+这些命令会被 hello-cc shim 包装为本机 tmux 常驻终端：
+
+- 本地终端会 attach 到同一个 tmux 会话，仍然可以像普通 Claude/Codex 一样交互。
+- Web 控制台看到并操作的是同一个 tmux pane，不是浏览器里临时创建的假终端。
+- `hcc down` 只停止 Web runtime，不会杀掉这些 tmux 会话。
+- 重新运行 `hcc web` 后，只要 tmux pane 还活着，Web 会重新接管。
+
+如果只想初始化本地通信、不启动 Web、不安装 shim，可使用：
+
+```bash
+hcc up
+```
+
+普通用户优先使用 `hcc web`。
+
+## 项目边界
+
+默认项目边界就是当前工作目录。如果当前目录没有 `.hello-cc/mesh.db`，hello-cc 会在首次使用时创建：
+
+```text
+/repo-a/.hello-cc/mesh.db
+/repo-a/subdir/.hello-cc/mesh.db
+```
+
+这两个目录默认是两个不同项目，不会互相看到任务和消息。想让多个终端自然通信，就在同一个项目目录启动它们。
+
+如果确实要让多个路径或 worktree 共用一个总线，需要显式指定：
+
+```bash
+hcc --root /path/to/project web
+export HCC_ROOT=/path/to/project
+export HCC_DB=/path/to/project/.hello-cc/mesh.db
+```
+
+hello-cc 不会自动向父目录继承项目边界，这样可以避免子目录会话误加入上层项目。
+
+## 通信模型
+
+hello-cc 的通信不是 CLI 之间点对点互发，也不是必须依赖 MCP。核心是项目本地 SQLite WAL 总线：
+
+```text
+Claude/Codex/普通 shell
+  -> hooks / hcc 命令 / Web runtime
+  -> .hello-cc/mesh.db
+  -> peers / tasks / messages / locks / handoffs / events
+  -> tmux-backed terminal control
+```
+
+任务和消息的读取规则不同：
+
+- 任务是项目事实。所有 peer 默认都能看到未 `done` 且未 `abandoned` 的任务。
+- 消息是带收件人的邮箱消息。`hcc msg inbox` 默认读取当前 peer 的未读消息，`hcc msg ack` 记录每个 peer 的已读状态。
+- `ask` 和 `broadcast` 会写入持久消息；加 `--inject` 时，还会把内容实时注入到 Web runtime 已接管的终端。
+- 锁使用 SQLite 事务和 TTL，是协作式冲突避免，不是文件系统强制沙箱。
+
+## Claude/Codex 如何知道其他会话状态
+
+主链路是 hooks 注入，不是依赖 `CLAUDE.md`。
+
+`hcc web` 会安装 Claude Code 和 Codex hooks。在会话启动、用户提交 prompt、工具调用前后、会话空闲等事件中，hooks 会把 hello-cc 当前快照注入给模型，包括：
+
+- 当前 peer 身份
+- 活跃 peer 列表
+- 未完成任务
+- 当前 peer 的未读消息
+- 活跃锁
+- 建议执行的 `hcc status`、`hcc peers`、`hcc task list`、`hcc msg inbox`、`hcc lock list`
+
+因此，当你在已接入的 Claude/Codex 里问“其他会话在做什么”，模型应该基于 hello-cc 注入的最新状态回答，而不是回答“我无法知道其他会话”。
+
+如果仍然回答不知道，通常是这些原因：
+
+- 没有先在项目目录运行 `hcc web`
+- 当前终端还没有加载 `~/.hcc-shims` PATH
+- Codex hooks 没有开启，或安装后的 hook 还没有在 Codex 的 hook review 流程里信任
+- Claude/Codex 是在不同项目目录启动的
+- 当前会话是 `hcc web` 之前打开的 raw 终端，只能靠下一次 hook 事件加入通信，不能被 Web 视觉接管
+- 对应 CLI 版本没有触发预期 hook
+
+可以在同一个项目目录用一次性 debug 调用确认 Claude Code 是否真实注入：
+
+```bash
+claude -p 'Do you see hello-cc open tasks?' --debug hooks --debug-file /tmp/hcc-claude-hooks.log
+```
+
+debug 日志里应该出现 `Hook UserPromptSubmit ... provided additionalContext`，并包含 `hello-cc coordination` 块。
+
+## Web 控制台
+
+默认本机和内网访问：
+
+```bash
+hcc web
+```
+
+需要令牌时再显式开启：
+
+```bash
+HCC_WEB_TOKEN='choose-a-long-token' hcc web --host 0.0.0.0 --port 8787
+```
+
+同一内网机器打开：
+
+```text
+http://<machine-ip>:8787/
+```
+
+Web 控制台能做这些事：
+
+- 在一个端口里切换多个已注册项目 root
+- 直接在浏览器里注册新的项目路径
+- 查看项目状态：peers、tasks、messages、locks、handoffs、events
+- 操作本地终端：启动 Claude/Codex/shell、发送键盘输入、查看输出、停止接管
+
+Web 操作的是 hello-cc 管理的本机 tmux 终端：
+
+- 通过 Web 表单启动的新会话
+- 通过 `hcc peer start` 启动的新会话
+- 通过 shim 直接输入 `claude` / `codex` 启动的新会话
+- 通过 `hcc peer attach` 接入的已有 tmux pane
+
+已经打开的普通 raw 终端不能被无条件捕获或控制，除非它原本就在 tmux、screen 或 hello-cc shim 之下。它仍然可以通过 hooks 和 `hcc` 命令参与任务、消息和锁。
+
+## 命令参考
+
+使用 `hcc --help` 查看命令列表，使用 `hcc <command> --help` 查看单个命令。
+维护中的命令摘要见 [命令参考](commands.zh-CN.md)。
+
+## 稳定 peer 身份
+
+hello-cc 会尽量让恢复会话复用稳定 peer ID：
+
+| 启动方式 | peer ID |
+|---|---|
+| `claude --resume abc12345...` | `claude-abc12345` |
+| `claude --session-id abc12345...` | `claude-abc12345` |
+| `claude --continue` | 先使用终端派生 ID，随后 hooks 记录真实 session 元数据 |
+| `claude --fork-session --resume abc12345...` | 先使用终端派生 ID，随后 hooks 记录新 session 元数据 |
+| `codex resume abc12345...` | `codex-abc12345` |
+| `codex resume --last` | 先使用终端派生 ID，随后 discovery 记录真实 session 元数据 |
+| 普通 shell | `shell-<terminal>` |
+| 手动 `HCC_PEER=xxx` | 使用 `xxx` |
+
+已知 resume ID 的会话重启后会保持同一个 peer ID。启动前不知道真实 provider session ID 的模式，会先用终端派生 ID，启动后再记录真实 provider session 元数据。
+
+## 典型工作流
+
+创建任务：
+
+```bash
+hcc task create --title "重构路由诊断" \
+  --body "保持变更范围小。" --priority 20
+```
+
+认领并加锁：
+
+```bash
+hcc task next
+hcc lock acquire --resource vllm/router --ttl 900 --reason "实现路由诊断"
+```
+
+发消息或实时注入：
+
+```bash
+hcc msg send --to claude-a --body "实现已准备好供审查。"
+hcc ask claude-a "请审查当前实现。" --inject
+hcc broadcast "暂停编辑 vllm/router，等待任务完成。" --inject
+```
+
+完成并交接：
+
+```bash
+hcc handoff create --to claude-a \
+  --summary "已实现路由诊断变更。" \
+  --tests "pytest tests/router" \
+  --risks "未跑完整基准"
+
+hcc task done --id 1 --summary "已完成并交接。"
+hcc lock release --resource vllm/router
+```
+
+## 环境变量
+
+| 变量 | 用途 |
+|---|---|
+| `HCC_PEER` | 默认 peer 身份 |
+| `HCC_ROOT` | 覆盖项目根目录 |
+| `HCC_DB` | 覆盖数据库路径 |
+| `HCC_WEB_TOKEN` | 可选 Web 访问令牌 |
+| `HCC_RUNTIME_URL` | 直接指定 runtime URL |
+| `HCC_NO_AUTO_INSTALL_TMUX=1` | 禁用 tmux 自动安装，主要用于测试 |
+
+`claude` / `codex` shim 和 `hcc peer start` 会使用当前启动终端的环境变量创建 tmux-backed 会话，不使用后台 Web runtime 启动时的旧环境。这样你可以在新终端里先 `export ANTHROPIC_*`、`CLAUDE_CODE_*` 或其他 provider 变量，再运行 `claude` / `codex`。
+
+已经运行的 CLI 进程不能被操作系统原地修改环境变量。`claude` / `codex` shim 会用 `--restart-env` 调用 `hcc peer start`，因此 hello-cc 会为同一个 resume/session peer 记录启动环境指纹。当你从新终端再次启动它且环境已变化时，如果对应 tmux 会话没有本地 tmux client 或 Web client 正在连接，hello-cc 会自动重启这个 tmux 会话并应用新环境。如果会话正在被操作，会提示先 detach/关闭 Web 连接，或运行 `hcc peer stop <peer>` 后再启动。
+
+如果直接调用 `hcc peer start`，需要加 `--restart-env` 才会启用同样的环境变化自动重启行为。
+
+shim 只接管交互式终端会话。元命令和维护命令会直通真实 provider CLI，例如 `claude --help`、`claude --version`、`claude --print`、`claude --bare`、`claude --safe-mode`、`codex --help`、`codex --version`，以及 `codex exec`、`codex review`、`codex doctor`、`codex mcp` 等非交互 Codex 子命令。交互式的 `claude`、`claude --resume ...`、`codex`、`codex resume ...`、`codex fork ...` 会走 tmux-backed，会出现在 Web 控制台里。

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@logicseek/hello-cc",
-  "version": "0.1.0",
-  "description": "Project-local peer mesh for Claude Code, Codex, and other coding CLI sessions.",
+  "version": "0.1.2",
+  "description": "Local control plane for coordinating Claude Code, Codex, and other coding CLI sessions.",
   "type": "module",
   "bin": {
     "hcc": "bin/hcc.mjs",
@@ -11,8 +11,10 @@
     "bin/",
     "lib/",
     "scripts/",
+    "assets/",
     "README.md",
     "README.zh-CN.md",
+    "CHANGELOG.md",
     "LICENSE",
     "docs/"
   ],
@@ -20,6 +22,8 @@
     "node": ">=24.0.0"
   },
   "scripts": {
+    "release:notes": "node ./scripts/release-notes.mjs",
+    "release:check": "node ./scripts/release-notes.mjs --check",
     "smoke": "node ./bin/hcc.mjs --help",
     "test": "node ./scripts/regression.mjs",
     "test:regression": "node ./scripts/regression.mjs"