jinzd-ai-cli 0.4.209 → 0.4.211

package/README.md

@@ -43,7 +43,7 @@
 - **MCP Protocol** — Connect external MCP servers for dynamic tool discovery
 - **Multi-User Auth** — Web UI supports multiple users with password authentication
 - **PWA Support** — Install Web UI as a desktop/mobile app, accessible over LAN
-- **Hierarchical Context** — 3-layer context files (global / project / subdirectory) auto-injected
+- **Hierarchical Context** — 3-layer context files (global / project / subdirectory) auto-injected; supports native AICLI.md, Claude-compatible CLAUDE.md, and Codex-compatible AGENTS.md with override files
 - **Headless Mode** — `ai-cli -p "prompt"` for CI/CD pipelines and scripting
 - **44 REPL Commands** — Session management, checkpointing, code review, security review/scan, rewind, scaffolding, cross-session history search, chat-memory recall, smart model routing (`/route`), and more
 - **GitHub Actions CI/CD** — Automated testing on Node 20/22 + npm publish on release tags
@@ -329,7 +329,65 @@ Control when tools require confirmation. Rules are checked in order — first ma
 | `action` | `auto-approve` (skip confirmation), `deny` (block), `confirm` (ask user) |
 | `when.dangerLevel` | Only match when danger level is `safe`, `write`, or `destructive` |
 | `when.pathPattern` | Substring match against tool's `path` or `command` argument |
-
+
+### Permission Profiles
+
+Permission profiles provide coarse-grained safety boundaries before fine-grained `permissionRules` run. The default profile is `legacy`, so existing configs keep their old behavior.
+
+Built-in profiles:
+
+| Profile | Behavior |
+|---------|----------|
+| `legacy` | Backward-compatible mode. Uses `permissionRules` and `defaultPermission` as before. |
+| `read-only` | Allows known read-only/safe tools and safe MCP tools; blocks write and destructive tools. |
+| `workspace-write` | Allows explicit file writes only inside the workspace roots or temp dirs; destructive tools still require confirmation. |
+| `danger-full-access` | Auto-approves non-destructive tools by default; destructive tools still require confirmation. Use only in isolated environments. |
+
+```json
+{
+  "defaultPermissionProfile": "workspace-write",
+  "allowedPermissionProfiles": ["legacy", "read-only", "workspace-write", "danger-full-access"],
+  "permissionProfiles": {
+    "workspace-write": {
+      "workspaceRoots": ["D:/github/ai-cli"],
+      "allowTemp": true,
+      "rules": [
+        { "tool": "read_file", "action": "auto-approve" },
+        { "tool": "list_dir", "action": "auto-approve" }
+      ]
+    }
+  },
+  "permissionRules": [
+    { "tool": "bash", "action": "deny", "when": { "pathPattern": "rm -rf" } }
+  ]
+}
+```
+
+`/status` and `/security status` show the active profile. The Web status payload also includes `permissionProfile` for UI surfaces.
+### Network Policy
+
+`networkPolicy` is disabled by default for backward compatibility. When enabled, it governs network-facing tools before execution: `web_fetch`, `web_search`, `google_search`, MCP tools, and shell commands that look like network access (`curl`, `wget`, `git clone/fetch/pull/push`, package installs, SSH/SCP, etc.).
+
+```json
+{
+  "networkPolicy": {
+    "enabled": true,
+    "defaultAction": "confirm",
+    "allowDomains": ["github.com", "docs.anthropic.com", "platform.openai.com"],
+    "denyDomains": ["example-danger.test"],
+    "allowPrivateNetwork": false,
+    "tools": {
+      "web_fetch": "confirm",
+      "web_search": "allow",
+      "google_search": "confirm",
+      "shell": "confirm",
+      "mcp": "confirm"
+    }
+  }
+}
+```
+
+Actions are `allow`, `confirm`, or `deny`. Domain entries match the exact host or subdomains; port lists match the resolved URL port. Private/internal hosts such as `localhost`, `127.0.0.1`, `10.0.0.0/8`, `192.168.0.0/16`, and private IPv6 ranges are blocked unless `allowPrivateNetwork` is true.
 **Recommended minimal config** — auto-approve all read-only tools to reduce y/N prompts:
 
 ```json
@@ -370,11 +428,11 @@ ai-cli automatically discovers and injects context files into the system prompt:
 
 | Layer | Path | Purpose |
 |-------|------|---------|
-| Global | `~/.aicli/AICLI.md` | Personal preferences across all projects |
-| Project | `<git-root>/AICLI.md` | Project rules (commit to git for team sharing) |
-| Subdirectory | `<cwd>/AICLI.md` | Directory-specific instructions |
+| Global | `~/.aicli/<context-file>` | Personal preferences across all projects |
+| Project | `<git-root>/<context-file>` | Project rules (commit to git for team sharing) |
+| Subdirectory | `<cwd>/<context-file>` | Directory-specific instructions |
 
-Also supports `CLAUDE.md` as an alternative filename at each layer.
+At each layer, ai-cli loads the first non-empty file in this priority order: `AICLI.override.md`, `AGENTS.override.md`, `AICLI.md`, `CLAUDE.md`, `AGENTS.md`. `AICLI.md` is the native filename; `CLAUDE.md` and `AGENTS.md` are compatibility filenames for Claude Code and Codex-style projects.
 
 ### MCP Integration
 
@@ -422,6 +480,46 @@ npm run test:watch    # Watch mode
 
 79 offline test files covering: authentication, sessions, tool types & danger levels, permissions, output truncation, diff rendering, edit-file similarity, error hierarchy, config management, env loading, provider registry, web-fetch, grep-files, hub renderer, hub discussion, hub presets, dev-state, token estimator, tool registry budget, parallel tool execution, cost tracker, session tool history.
 
+## Releasing (Version Bump → npm Publish → GitHub Push)
+
+> **For contributors and AI agents: the entire release is driven by [`scripts/release.mjs`](scripts/release.mjs). Never manually bump the version or run `npm publish` yourself** — a hand-publish of `0.4.207` shipped a version that reported the wrong number and forced a corrective re-release (`0.4.208`). The script's guards exist precisely to stop that.
+
+**Prerequisites**
+
+- You are on the `main` branch and the changes to ship are already in the working tree.
+- `npx tsc --noEmit` is clean and `npm test` is green (the script enforces both and rolls the bump back on failure).
+- You are logged into npm as the package owner (`npm whoami`).
+- You have push access to the GitHub remote.
+
+**Step 1 — Write the milestone entry FIRST (Guard A).** Add a one-line entry to the `## 最近里程碑` section of [`CLAUDE.md`](CLAUDE.md) that contains the exact full-width-parenthesis marker `（vX.Y.Z）` for the target version. The script refuses to start without it. (Full narrative goes in `CHANGELOG.md`; this section is just the index line.)
+
+**Step 2 — Run the release script.**
+
+```bash
+# patch: 0.4.209 → 0.4.210  (also accepts: minor / major / an explicit x.y.z)
+node scripts/release.mjs patch -m "fix(scope): one-line commit title"
+
+# preview only — validates guards, writes nothing:
+node scripts/release.mjs patch -m "..." --dry-run
+```
+
+- Do **not** put a `(vX.Y.Z)` suffix in `-m`; the script appends it automatically.
+- On Windows PowerShell, call `node` directly — `npm run release -- -m ...` swallows the `-m` argument.
+
+**What the script does, in order:**
+
+1. **Guard A** — asserts `CLAUDE.md` contains the `（vX.Y.Z）` milestone entry.
+2. Bumps the version in **three** places: `package.json`, `src/core/constants.ts` (`VERSION`), and `CLAUDE.md` (`**当前版本**`).
+3. **Guard B** — re-reads all three files from disk and asserts every bump landed.
+4. **Guard C** — `tsc --noEmit` must be zero-error (rolls the bump back on failure).
+5. `npm test` must pass (rolls the bump back on failure).
+6. Prints the exact file list entering the release commit and blocks if any looks sensitive (`.env`, `*.pem`, `*.key`, `secret`, …). Override consciously with `--allow-sensitive`.
+7. `git add -A` + commit `"<title> (vX.Y.Z)"` (message passed via argv, not shell-interpolated).
+8. `npm publish` (the build runs automatically via `prepublishOnly`), then re-queries the registry to confirm the new version is live.
+9. `git push` to `main`.
+
+**Optional flags:** `--dry-run` · `--skip-tests` · `--no-publish` · `--no-push` · `--allow-sensitive`.
+
 ## Documentation
 
 - [`docs/USAGE.md`](docs/USAGE.md) — Complete reference manual (commands, tools, config)

package/README.zh-CN.md

@@ -35,7 +35,7 @@
 - **MCP 协议** — 接入外部 MCP 服务器，动态发现工具
 - **多用户认证** — Web UI 支持多用户密码登录
 - **PWA 支持** — Web UI 可安装为桌面/移动应用，支持局域网访问
-- **三层级上下文** — 全局 / 项目 / 子目录上下文文件自动注入
+- **三层级上下文** — 全局 / 项目 / 子目录上下文文件自动注入；支持原生 `AICLI.md`、Claude 兼容 `CLAUDE.md`、Codex 兼容 `AGENTS.md` 及 override 文件
 - **无头模式** — `aicli -p "提示词"` 用于 CI/CD 管道和脚本
 - **44 个 REPL 命令** — 会话管理、检查点、代码审查、安全审查/扫描、对话回退、脚手架、聊天记忆召回、智能模型路由（`/route`）等
 - **GitHub Actions CI/CD** — Node 20/22 自动测试 + Release tag 自动发布 npm
@@ -391,11 +391,11 @@ ai-cli 自动发现并注入上下文文件到 system prompt：
 
 | 层级 | 路径 | 用途 |
 |------|------|------|
-| 全局层 | `~/.aicli/AICLI.md` | 所有项目通用的个人偏好 |
-| 项目层 | `<git-root>/AICLI.md` | 项目级规则（提交到 git 供团队共享） |
-| 子目录层 | `<cwd>/AICLI.md` | 当前子目录的特定指令 |
+| 全局层 | `~/.aicli/<context-file>` | 所有项目通用的个人偏好 |
+| 项目层 | `<git-root>/<context-file>` | 项目级规则（提交到 git 供团队共享） |
+| 子目录层 | `<cwd>/<context-file>` | 当前子目录的特定指令 |
 
-每层也支持 `CLAUDE.md` 作为备选文件名。
+每层按以下优先级加载第一个非空文件：`AICLI.override.md` → `AGENTS.override.md` → `AICLI.md` → `CLAUDE.md` → `AGENTS.md`。`AICLI.md` 是 ai-cli 原生文件名；`CLAUDE.md` 和 `AGENTS.md` 分别用于兼容 Claude Code 与 Codex 风格项目。
 
 ### MCP 集成
 
@@ -441,6 +441,46 @@ npm run test:watch    # 监听模式
 
 26 个测试套件覆盖：认证、会话、工具类型与危险级别、权限、输出截断、diff 渲染、edit-file 相似度、错误层级、配置管理、环境变量、Provider 注册、web-fetch、grep-files、Hub 渲染、Hub 讨论、Hub 预设、开发状态、Token 估算、工具注册表预算、并行工具执行、费用追踪、会话工具历史。
 
+## 发布（版本提升 → npm 发布 → 推送 GitHub）
+
+> **给贡献者与 AI 模型：整个发布流程一律走 [`scripts/release.mjs`](scripts/release.mjs)，切勿手动 bump 版本号或自己跑 `npm publish`。** 曾经手工 publish 的 `0.4.207` 装上后 `--version` 报错版本号，被迫补发 `0.4.208` 对齐——脚本的四道守卫就是为拦住这类事故而存在。
+
+**前置条件**
+
+- 当前在 `main` 分支，待发布的改动已在工作区。
+- `npx tsc --noEmit` 零错误、`npm test` 全绿（脚本会强制校验，失败自动回滚版本号）。
+- 已登录 npm 且是包的 owner（`npm whoami`）。
+- 有 GitHub 远端推送权限。
+
+**第 1 步 —— 先写里程碑条目（Guard A）。** 在 [`CLAUDE.md`](CLAUDE.md) 的 `## 最近里程碑` 一节加一行，条目中必须含目标版本的**全角括号**标记 `（vX.Y.Z）`，否则脚本拒绝启动。（完整叙事写进 `CHANGELOG.md`，本节只留一行式索引。）
+
+**第 2 步 —— 运行发布脚本。**
+
+```bash
+# patch：0.4.209 → 0.4.210（也支持 minor / major / 显式 x.y.z）
+node scripts/release.mjs patch -m "fix(scope): 一句话 commit 标题"
+
+# 仅预览，只校验守卫、不改任何文件：
+node scripts/release.mjs patch -m "..." --dry-run
+```
+
+- `-m` 里**不要**自带 `(vX.Y.Z)` 后缀，脚本会自动追加。
+- Windows PowerShell 下请直接用 `node` 调用——`npm run release -- -m ...` 会把 `-m` 参数吞掉。
+
+**脚本执行顺序：**
+
+1. **Guard A** —— 断言 `CLAUDE.md` 已含 `（vX.Y.Z）` 里程碑条目。
+2. bump **三处**版本号：`package.json`、`src/core/constants.ts`（`VERSION`）、`CLAUDE.md`（`**当前版本**`）。
+3. **Guard B** —— 从磁盘重读这三处，逐一断言都真的改到了。
+4. **Guard C** —— `tsc --noEmit` 必须零错误（失败则回滚版本号）。
+5. `npm test` 必须全绿（失败则回滚版本号）。
+6. 打印进入发布 commit 的完整文件清单，若含疑似敏感文件（`.env`、`*.pem`、`*.key`、`secret`…）直接拦下，确认无误加 `--allow-sensitive`。
+7. `git add -A` + commit `"<标题> (vX.Y.Z)"`（消息走 argv 传参，不经 shell 拼接）。
+8. `npm publish`（build 经 `prepublishOnly` 自动跑），再回查 registry 确认新版本已上线。
+9. `git push` 推送 `main`。
+
+**可选 flag：** `--dry-run` · `--skip-tests` · `--no-publish` · `--no-push` · `--allow-sensitive`。
+
 ## 文档
 
 - [English README](README.md) — English documentation

package/dist/{batch-45WLJUVP.js → batch-DE4RXKZD.js}

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 import {
   ConfigManager
-} from "./chunk-DUZRQXIP.js";
+} from "./chunk-UOROWTGG.js";
 import "./chunk-TZQHYZKT.js";
-import "./chunk-UPMBIS4T.js";
+import "./chunk-E5XCM4A6.js";
 import {
   atomicWriteFileSync
 } from "./chunk-IW3Q7AE5.js";

package/dist/{chunk-EN63JA7N.js → chunk-6NS6643Y.js}

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   TEST_TIMEOUT
-} from "./chunk-UPMBIS4T.js";
+} from "./chunk-E5XCM4A6.js";
 
 // src/tools/builtin/run-tests.ts
 import { execSync, spawnSync } from "child_process";

package/dist/{chunk-D6M4E7SH.js → chunk-BE6ERF7M.js}

@@ -2,7 +2,7 @@
 import {
   CONFIG_DIR_NAME,
   VERSION
-} from "./chunk-UPMBIS4T.js";
+} from "./chunk-E5XCM4A6.js";
 
 // src/diagnostics/crash-log.ts
 import {