farming-code 2.2.14 → 2.2.17

package/README.md

@@ -15,7 +15,7 @@
   <a href="https://github.com/zhuwenzhuang/farming/releases"><img alt="Release" src="https://img.shields.io/github/v/release/zhuwenzhuang/farming?label=release"></a>
   <a href="https://www.npmjs.com/package/farming-code"><img alt="npm" src="https://img.shields.io/npm/v/farming-code?label=npm"></a>
   <a href="./LICENSE"><img alt="License" src="https://img.shields.io/github/license/zhuwenzhuang/farming"></a>
-  <img alt="Node.js 22+" src="https://img.shields.io/badge/node-%3E%3D22-339933?logo=nodedotjs&amp;logoColor=white">
+  <img alt="Node.js 22.13 LTS or 24+" src="https://img.shields.io/badge/node-22.13_LTS_%7C_24%2B-339933?logo=nodedotjs&amp;logoColor=white">
   <img alt="macOS and Linux" src="https://img.shields.io/badge/platform-macOS%20%7C%20Linux-555">
 </p>
 
@@ -25,7 +25,7 @@ Farming runs on the same development machine as your repositories and coding CLI
 
 ## Quick Start
 
-With Node.js 22 or newer and at least one supported coding CLI installed and signed in:
+With Node.js 22.13 LTS (22.x) or Node.js 24+ and at least one supported coding CLI installed and signed in:
 
 ```bash
 npm install --global farming-code@latest && farming daemon
@@ -119,7 +119,7 @@ farming logs
 farming stop
 ```
 
-The startup token is stored in `~/.farming/.session-token` and reused across restarts and upgrades. **Settings → Updates** can upgrade npm installations in place. GitHub Releases also provide standalone CLI and directory bundles; see [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases) for current artifacts.
+The startup token is stored in `~/.farming/.session-token` and reused across restarts and upgrades. **Settings → Updates** can upgrade npm installations in place. npm updates first use the machine's configured registry and retry the registry shown in Settings only when that registry lacks the selected version. Before installing, Farming verifies that npm will update the same package root that launched the server. GitHub Releases also provide standalone CLI and directory bundles; see [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases) for current artifacts.
 
 To run from source with the same port and base path:
 

package/README.zh_cn.md

@@ -15,7 +15,7 @@
   <a href="https://github.com/zhuwenzhuang/farming/releases"><img alt="Release" src="https://img.shields.io/github/v/release/zhuwenzhuang/farming?label=release"></a>
   <a href="https://www.npmjs.com/package/farming-code"><img alt="npm" src="https://img.shields.io/npm/v/farming-code?label=npm"></a>
   <a href="./LICENSE"><img alt="License" src="https://img.shields.io/github/license/zhuwenzhuang/farming"></a>
-  <img alt="Node.js 22+" src="https://img.shields.io/badge/node-%3E%3D22-339933?logo=nodedotjs&amp;logoColor=white">
+  <img alt="Node.js 22.13 LTS or 24+" src="https://img.shields.io/badge/node-22.13_LTS_%7C_24%2B-339933?logo=nodedotjs&amp;logoColor=white">
   <img alt="macOS and Linux" src="https://img.shields.io/badge/platform-macOS%20%7C%20Linux-555">
 </p>
 
@@ -25,7 +25,7 @@ Farming 与代码仓库和 Coding CLI 运行在同一台开发机上。Agent 进
 
 ## 快速开始
 
-准备好 Node.js 22 或更新版本，以及至少一个已安装、已登录的受支持 Coding CLI：
+准备好 Node.js 22.13 LTS（22.x）或 Node.js 24+，以及至少一个已安装、已登录的受支持 Coding CLI：
 
 ```bash
 npm install --global farming-code@latest && farming daemon
@@ -119,7 +119,7 @@ farming logs
 farming stop
 ```
 
-启动 Token 存放在 `~/.farming/.session-token`，重启和升级会继续复用。**Settings → Updates** 可以原地升级 npm 安装。GitHub Releases 也提供独立 CLI 和目录 Bundle；当前产物见 [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases)。
+启动 Token 存放在 `~/.farming/.session-token`，重启和升级会继续复用。**Settings → Updates** 可以原地升级 npm 安装。npm 升级会先使用机器配置的 registry；只有该 registry 缺少所选版本时，才会回退到 Settings 展示版本所用的 registry。安装前 Farming 会校验 npm 将更新的包根目录与启动当前服务的包根目录一致。GitHub Releases 也提供独立 CLI 和目录 Bundle；当前产物见 [GitHub Releases](https://github.com/zhuwenzhuang/farming/releases)。
 
 从源码运行，并使用相同的端口与 Base Path：
 

package/THIRD_PARTY_NOTICES.md

@@ -27,7 +27,7 @@ preserved in bundled `node_modules` when bundled dependencies are enabled.
 | `ansi-to-html` | 0.7.2 | MIT | ANSI text rendering support |
 | `chokidar` | 5.0.0 | MIT | Filesystem watching |
 | `diff` | 9.0.0 | BSD-3-Clause | Character-level diff ranges for code review |
-| `express` | 4.22.1 | MIT | HTTP API server |
+| `express` | 4.22.2 | MIT | HTTP API server |
 | `ghostty-web` | 0.4.0 | MIT | Optional/debug terminal renderer assets |
 | `highlight.js` | 11.11.1 | BSD-3-Clause | Syntax highlighting |
 | `katex` | 0.17.0 | MIT | Mathematical notation rendering |
@@ -58,6 +58,22 @@ beside the vendored files at `frontend/vendor/ghostty-web/LICENSE`.
 If vendored assets are updated, keep this notice in sync with the package name,
 version, and license.
 
+Farming's TypeScript token-history scanner adapts the cumulative Codex
+accounting and copied-prefix classification semantics from
+[`CodexBar`](https://github.com/steipete/CodexBar) 0.45.2 at commit
+`91560ca98e776b96fdf910d4a0423c2f0c07a3b9` (MIT, Copyright (c) 2026 Peter
+Steinberger). It adapts Claude assistant usage extraction, streaming message-id
+deduplication, and cached-input normalization from
+[`cc-statistics`](https://github.com/androidZzT/cc-statistics) 1.1.0 at commit
+`c98be0af52bbc7f09a1f277747744ace48d9e014` (MIT, Copyright (c) 2026
+androidZzT).
+
+Farming does not bundle either application's runtime. The adapted TypeScript
+scanner, incremental filesystem checkpoints, SQLite schema, scan budgeting,
+and product result shape are maintained by Farming. Exact source files,
+adaptation scope, revisions, and both MIT licenses are retained under
+`backend/vendor/usage-parsers/`.
+
 The CRT skin bundles one font file under `frontend/skins/crt/fonts/`:
 
 | Font | License | Purpose |

package/backend/acp/packaged-codex-acp.js

@@ -0,0 +1,13 @@
+const PACKAGED_CODEX_ACP_ARG = '--farming-codex-acp';
+
+function runPackagedCodexAcp() {
+  if (!process.pkg) {
+    throw new Error('The packaged Codex ACP entry is available only in a standalone Farming CLI');
+  }
+  require('../../dist/acp/codex-acp-1.1.4.js');
+}
+
+module.exports = {
+  PACKAGED_CODEX_ACP_ARG,
+  runPackagedCodexAcp,
+};