From 164d2910d63aefd20b5a2fec3cb2c52066a2c51e Mon Sep 17 00:00:00 2001 From: ework-agent Date: Sun, 4 Oct 2026 18:54:24 +0800 Subject: [PATCH 1/2] docs(#2079): call out the #1977 update-visibility change in the 0.1.182 notes and README en/zh --- README.md | 4 +++- README.zh-CN.md | 4 +++- release-notes/package.json | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c3c489547b..0684ac0d09 100644 --- a/README.md +++ b/README.md @@ -385,7 +385,9 @@ The proxy checks npm on startup and every 3 minutes; a newer version is installe While the running process is behind the on-disk install ("stale"), the web UI shows a banner (running vs installed version, auto-restart state) and `GET /__bili/status` returns `{version, diskVersion, stale, autoRestartOnUpdate, advisory, inFlight}` for scripting (`advisory` is the active critical-defect entry or `null`, see below). Disable permanently via `"autoUpdate": false` in config or `ACP_AUTO_UPDATE=0`. -In **plugin mode** (`bili opencode` / `bili pi` / `bili dsh` — the proxy runs embedded in a long-lived host), "restart bili" means restarting the **host**: the embedded process cannot exit on its own, so a host left open keeps serving whatever code it started with, silently missing every fix auto-update reports as installed (#1603). Enable `--auto-restart-on-update` to have it self-restart at a safe point, or run `/acp` — the status panel now appends a one-line staleness warning (running vs installed version) whenever the on-disk install is ahead of the live process. +In **plugin mode** (`bili opencode` / `bili pi` / `bili dsh` — the proxy runs embedded in a long-lived host), "restart bili" means restarting the **host**: the embedded process cannot exit on its own, so a host left open keeps serving whatever code it started with, silently missing every fix auto-update reports as installed (#1603). Enable `--auto-restart-on-update` to have it self-restart at a safe point, or run `/acp` (OpenCode hosts today — pi/dsh coverage tracked in #2084) — the status panel appends a one-line staleness warning (running vs installed version) whenever the on-disk install is ahead of the live process. + +**Update visibility is silent by default since v0.1.182 (#1977):** routine/recommended releases no longer render an update line on the `/acp` panel footer or in `acp_status` — only a `critical`-tier release surfaces there (`CRITICAL UPDATE READY/AVAILABLE`). The standing ways to check an installed-but-not-restarted release are the stale cues above: web UI banner, the `/acp` one-line warning, and `GET /__bili/status`. Deliberately no always-on nag; the advisory channel (#1481) remains the only auto-visible critical path. When an install keeps failing (unwritable or host-managed dir, network error, …), auto-update no longer re-downloads and retries on every 3-minute cycle forever. After three consecutive failures it backs off exponentially (5 min → 10 → 20 …, capped at 6 h), logs a one-time actionable hint (fix permissions / npm prefix, reinstall user-level, or disable via `"autoUpdate": false` / `ACP_AUTO_UPDATE=0`), and logs nothing further about the failure while cooling down (no download, no retry line); it resumes as soon as the failure clears or a different version is targeted (#1603). diff --git a/README.zh-CN.md b/README.zh-CN.md index 3ddaeab0bc..5fa6fc6a17 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -303,7 +303,9 @@ bili --no-auto-update # 本次启动禁用自动更新 代理启动时和每 3 分钟检查 npm 是否有新版本。发现新版本就原位安装并打印通知 —— **重启 `bili` 才能生效**,除非启用可选自重启(`--auto-restart-on-update` 参数 / `ACP_AUTO_RESTART_ON_UPDATE=1` 环境变量 / 配置 `"autoRestartOnUpdate": true`,默认关闭):零在途请求时校验新安装、停止接收连接、排空、在同一端口拉起替代进程并在其开始接受连接后退出(客户端自动重连;会话状态在磁盘上保留)。安全门:排空窗口全程零在途、re-exec 前安装完整性检查、10 分钟冷却标记防止版本抖动循环重启;任何失败恢复原监听器并回落到普通提醒。运行进程落后于磁盘安装("stale")时,Web UI 显示横幅,`GET /__bili/status` 返回 `{version, diskVersion, stale, autoRestartOnUpdate, advisory, inFlight}` 供脚本使用(`advisory` 为生效中的严重缺陷公告或 `null`,见下节)。永久禁用:配置(`"autoUpdate": false`)或环境变量(`ACP_AUTO_UPDATE=0`)。 -**插件模式**(`bili opencode` / `bili pi` / `bili dsh` —— 代理内嵌在长驻宿主里运行时),"重启 bili"指的是重启**宿主**:内嵌进程无法自行退出,所以一直开着的宿主会持续运行它启动时的那份代码,默默地错过自动更新报告为"已安装"的每一处修复(#1603)。启用 `--auto-restart-on-update` 可让它在安全点自重启;或运行 `/acp` —— 当磁盘安装领先于运行进程时,状态面板现在会追加一行过期警告(运行版本 vs 已安装版本)。 +**插件模式**(`bili opencode` / `bili pi` / `bili dsh` —— 代理内嵌在长驻宿主里运行时),"重启 bili"指的是重启**宿主**:内嵌进程无法自行退出,所以一直开着的宿主会持续运行它启动时的那份代码,默默地错过自动更新报告为"已安装"的每一处修复(#1603)。启用 `--auto-restart-on-update` 可让它在安全点自重启;或运行 `/acp`(当前仅 OpenCode 宿主,pi/dsh 覆盖见 #2084)—— 当磁盘安装领先于运行进程时,状态面板会追加一行过期警告(运行版本 vs 已安装版本)。 + +**自 v0.1.182 起,更新提示默认静默(#1977):**routine/recommended 版本不再在 `/acp` 面板脚注或 `acp_status` 中渲染更新行 —— 只有 `critical` 级别的版本会在那里显示(`CRITICAL UPDATE READY/AVAILABLE`)。检查"已安装未重启"版本的常设途径即上文所列的过期线索:Web UI 横幅、`/acp` 单行警告、以及 `GET /__bili/status`。刻意不设常驻提醒;严重缺陷公告通道(#1481)仍是唯一自动可见的严重路径。 当安装反复失败(目录不可写或受宿主托管、网络错误等)时,自动更新不再每个 3 分钟周期都重复下载并重试。连续失败三次后,它按指数退避(5 分钟 → 10 → 20 …,上限 6 小时),打印一次性的可操作提示(修复权限 / npm prefix、以用户级重装,或用 `"autoUpdate": false` / `ACP_AUTO_UPDATE=0` 禁用),并在冷却期间不再为这次失败输出日志(不下载、不打重试行);一旦故障消除或目标版本变化即恢复(#1603)。 diff --git a/release-notes/package.json b/release-notes/package.json index 040837ce2a..6be3fec03e 100644 --- a/release-notes/package.json +++ b/release-notes/package.json @@ -21,7 +21,7 @@ "version": "0.1.182", "date": "2026-10-04", "tier": "recommended", - "summary": "Emergency carve-out: the output-budget clamp now floors to an integer, so max_tokens / max_completion_tokens / max_output_tokens are always whole numbers. Strict OpenAI-compatible upstreams no longer reject requests with 'max_tokens: Input should be a valid integer' (400) or 'Endpoint is unavailable' (422) — which killed whole agent turns (#2011). Only this fix, on top of v0.1.181." + "summary": "max_tokens & completion/output variants now floor to integers — OpenAI-compatible upstreams stop rejecting requests that killed whole agent turns (#2011). #1977: update visibility is silent by default — routine/recommended releases no longer nag on the /acp panel or acp_status; only critical-tier entries surface (staleness: web banner, /acp line on OpenCode, GET /__bili/status)." }, { "version": "0.1.181", From 2b1fb921905037f48834199a79db93202bab14d9 Mon Sep 17 00:00:00 2001 From: ework-agent Date: Sun, 4 Oct 2026 19:14:39 +0800 Subject: [PATCH 2/2] =?UTF-8?q?docs(#2079=20review):=20correct=20version?= =?UTF-8?q?=20attribution=20=E2=80=94=20#1977/#1603=20shipped=20in=20v0.1.?= =?UTF-8?q?183,=20not=20v0.1.182?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #2085 as written amended the published 0.1.182 release-notes entry and pointed the README at v0.1.182, but tag ancestry (fix(#1977)=78276c01, /acp stale line=a2999ff4 are not ancestors of v0.1.182, both are of v0.1.183) and the published npm 0.1.182 artifact (no CRITICAL UPDATE / fetchStaleNotice strings in dist) prove the visibility policy shipped in v0.1.183. Restoring the 0.1.182 entry verbatim (its original text is correct as shipped), adding the 0.1.183 entry carrying the #1977 note (tier routine, 367 chars, validator-clean), and pointing README en/zh at v0.1.183. --- README.md | 2 +- README.zh-CN.md | 2 +- release-notes/package.json | 8 +++++++- 3 files changed, 9 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0684ac0d09..f328a39e5e 100644 --- a/README.md +++ b/README.md @@ -387,7 +387,7 @@ While the running process is behind the on-disk install ("stale"), the web UI sh In **plugin mode** (`bili opencode` / `bili pi` / `bili dsh` — the proxy runs embedded in a long-lived host), "restart bili" means restarting the **host**: the embedded process cannot exit on its own, so a host left open keeps serving whatever code it started with, silently missing every fix auto-update reports as installed (#1603). Enable `--auto-restart-on-update` to have it self-restart at a safe point, or run `/acp` (OpenCode hosts today — pi/dsh coverage tracked in #2084) — the status panel appends a one-line staleness warning (running vs installed version) whenever the on-disk install is ahead of the live process. -**Update visibility is silent by default since v0.1.182 (#1977):** routine/recommended releases no longer render an update line on the `/acp` panel footer or in `acp_status` — only a `critical`-tier release surfaces there (`CRITICAL UPDATE READY/AVAILABLE`). The standing ways to check an installed-but-not-restarted release are the stale cues above: web UI banner, the `/acp` one-line warning, and `GET /__bili/status`. Deliberately no always-on nag; the advisory channel (#1481) remains the only auto-visible critical path. +**Update visibility is silent by default since v0.1.183 (#1977):** routine/recommended releases no longer render an update line on the `/acp` panel footer or in `acp_status` — only a `critical`-tier release surfaces there (`CRITICAL UPDATE READY/AVAILABLE`). The standing ways to check an installed-but-not-restarted release are the stale cues above: web UI banner, the `/acp` one-line warning, and `GET /__bili/status`. Deliberately no always-on nag; the advisory channel (#1481) remains the only auto-visible critical path. When an install keeps failing (unwritable or host-managed dir, network error, …), auto-update no longer re-downloads and retries on every 3-minute cycle forever. After three consecutive failures it backs off exponentially (5 min → 10 → 20 …, capped at 6 h), logs a one-time actionable hint (fix permissions / npm prefix, reinstall user-level, or disable via `"autoUpdate": false` / `ACP_AUTO_UPDATE=0`), and logs nothing further about the failure while cooling down (no download, no retry line); it resumes as soon as the failure clears or a different version is targeted (#1603). diff --git a/README.zh-CN.md b/README.zh-CN.md index 5fa6fc6a17..57ee4f5412 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -305,7 +305,7 @@ bili --no-auto-update # 本次启动禁用自动更新 **插件模式**(`bili opencode` / `bili pi` / `bili dsh` —— 代理内嵌在长驻宿主里运行时),"重启 bili"指的是重启**宿主**:内嵌进程无法自行退出,所以一直开着的宿主会持续运行它启动时的那份代码,默默地错过自动更新报告为"已安装"的每一处修复(#1603)。启用 `--auto-restart-on-update` 可让它在安全点自重启;或运行 `/acp`(当前仅 OpenCode 宿主,pi/dsh 覆盖见 #2084)—— 当磁盘安装领先于运行进程时,状态面板会追加一行过期警告(运行版本 vs 已安装版本)。 -**自 v0.1.182 起,更新提示默认静默(#1977):**routine/recommended 版本不再在 `/acp` 面板脚注或 `acp_status` 中渲染更新行 —— 只有 `critical` 级别的版本会在那里显示(`CRITICAL UPDATE READY/AVAILABLE`)。检查"已安装未重启"版本的常设途径即上文所列的过期线索:Web UI 横幅、`/acp` 单行警告、以及 `GET /__bili/status`。刻意不设常驻提醒;严重缺陷公告通道(#1481)仍是唯一自动可见的严重路径。 +**自 v0.1.183 起,更新提示默认静默(#1977):**routine/recommended 版本不再在 `/acp` 面板脚注或 `acp_status` 中渲染更新行 —— 只有 `critical` 级别的版本会在那里显示(`CRITICAL UPDATE READY/AVAILABLE`)。检查"已安装未重启"版本的常设途径即上文所列的过期线索:Web UI 横幅、`/acp` 单行警告、以及 `GET /__bili/status`。刻意不设常驻提醒;严重缺陷公告通道(#1481)仍是唯一自动可见的严重路径。 当安装反复失败(目录不可写或受宿主托管、网络错误等)时,自动更新不再每个 3 分钟周期都重复下载并重试。连续失败三次后,它按指数退避(5 分钟 → 10 → 20 …,上限 6 小时),打印一次性的可操作提示(修复权限 / npm prefix、以用户级重装,或用 `"autoUpdate": false` / `ACP_AUTO_UPDATE=0` 禁用),并在冷却期间不再为这次失败输出日志(不下载、不打重试行);一旦故障消除或目标版本变化即恢复(#1603)。 diff --git a/release-notes/package.json b/release-notes/package.json index 6be3fec03e..79791ba3d7 100644 --- a/release-notes/package.json +++ b/release-notes/package.json @@ -17,11 +17,17 @@ "tier": "critical", "summary": "Desktop (dsh): after 0.1.179, an update could make bili tools vanish until restart (#2082) — now self-healing, broken desktop updates roll back; re-activating the plugin after a healthy boot also re-registers its tools (#2101); also fixes tool-call misrouting (#2072). Restart dsh once. 丨 桌面版修复:0.1.179 后升级会使 bili 工具消失(#2082),现已自愈;损坏的桌面更新自动回滚;健康运行后重激活插件也会重新注册工具(#2101);另修 #2072 调用错路由。升级后重启一次 dsh。" }, + { + "version": "0.1.183", + "date": "2026-10-04", + "tier": "routine", + "summary": "Update visibility is silent by default (#1977): routine/recommended releases no longer nag on the /acp panel or acp_status — only critical-tier entries surface (CRITICAL UPDATE READY/AVAILABLE). Staleness cues for an installed-but-not-restarted release: web UI banner, /acp one-line warning (#1603, OpenCode hosts today — pi/dsh tracked in #2084), GET /__bili/status." + }, { "version": "0.1.182", "date": "2026-10-04", "tier": "recommended", - "summary": "max_tokens & completion/output variants now floor to integers — OpenAI-compatible upstreams stop rejecting requests that killed whole agent turns (#2011). #1977: update visibility is silent by default — routine/recommended releases no longer nag on the /acp panel or acp_status; only critical-tier entries surface (staleness: web banner, /acp line on OpenCode, GET /__bili/status)." + "summary": "Emergency carve-out: the output-budget clamp now floors to an integer, so max_tokens / max_completion_tokens / max_output_tokens are always whole numbers. Strict OpenAI-compatible upstreams no longer reject requests with 'max_tokens: Input should be a valid integer' (400) or 'Endpoint is unavailable' (422) — which killed whole agent turns (#2011). Only this fix, on top of v0.1.181." }, { "version": "0.1.181",