Skip to content

docs(#2079): surface the #1977 update-visibility change in the 0.1.182 notes and README en/zh - #2085

Merged
ranxianglei merged 2 commits into
masterfrom
2026-10-04_update-visibility-docs
Oct 4, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-10-04_update-visibility-docs

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Closes #2079

What

Docs-only follow-up to the v0.1.182 release (#1977 visibility policy from PR #2058): makes the "update notices are silent by default" behavior change visible where users actually look. No code changes, no behavior changes.

Changes

  1. release-notes/package.json — amend the already-published 0.1.182 entry. The entry as shipped only described the max_tokens integer-floor fix (bili 0.1.181:clampOutputBudget 把小数写进 max_tokens,上游 400 max_tokens: Input should be a valid integer / 422 Endpoint is unavailable #2011) and ended "Only this fix, on top of v0.1.181" — but v0.1.182 also shipped the Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977 critical-only visibility gate and the auto-update installs but never activates on long-lived plugin hosts; unwritable install dir retries every 3-min cycle for 11+ days #1603 /acp stale-install line. The new summary covers both: the bili 0.1.181:clampOutputBudget 把小数写进 max_tokens,上游 400 max_tokens: Input should be a valid integer / 422 Endpoint is unavailable #2011 fix, plus "Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #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", with pointers to the standing staleness cues (web banner / /acp line on OpenCode / GET /__bili/status). Propagates automatically: CI republishes the companion package on any master push touching release-notes/**. Locally validated against the workflow's inline checks (schema, ≤20 entries, semver, tier enum, summary ≤400 chars — new one is 381).
  2. README.md / README.zh-CN.md (Self-update section):
    • Qualify the /acp staleness-warning claim — it is wired into the OpenCode lane only today (src/agent/opencode-acp-command.ts calls fetchStaleNotice; the pi registerCommand("acp") and dsh statusOutcome handlers never do). The old wording sat inside the paragraph covering all three plugin hosts, i.e. it promised it for pi/dsh too. Coverage gap now tracked in #2084.
    • Add one paragraph stating the Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977 policy explicitly (silent by default since v0.1.182; only critical-tier surfaces as CRITICAL UPDATE READY/AVAILABLE; where to check staleness otherwise), so manual-restart / auto-update-disabled setups know the cue was moved, not removed.

Behavior change disclosure

None — documentation-only. The underlying behavior change (pending-restart/recommended releases no longer rendered on the panel footer / acp_status) shipped in v0.1.182 via PR #2058; this PR only documents it. No config surface touched (the opt-in knob suggested in #2079 is deliberately NOT added — see below).

Follow-up filed

@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-04_update-visibility-docs (2b1fb92)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2156-pr.2085.7396278

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2085.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

Reviewing #2085 (docs-only, 3 files). CI on head is green (14/14 checks). Fact-checking the claims against code/tags found one core factual error; fixing it directly on the branch per the 小问题直接修 rule, then I'll give the full structured verdict.

Error: the #1977 visibility policy (and the #1603 /acp stale line) shipped in v0.1.183, not v0.1.182. Three independent sources agree:

  • Tag ancestry: git merge-base --is-ancestor — fix(#1977) (78276c0) and feat(agent): surface stale install in the /acp status panel (#1603) (a2999ff) are NOT ancestors of tag v0.1.182; both ARE ancestors of tag v0.1.183.
  • Published artifact: grepped the actual dist/index.js of the npm billion-context@0.1.182 tarball — zero occurrences of the CRITICAL UPDATE READY/AVAILABLE strings, zero of fetchStaleNotice. Users on 0.1.182 do not have these behaviors.
  • GitHub Release v0.1.183 (published 2026-10-04T11:02Z, npm live) lists fix(#1977) in What's Changed.

Consequences for this PR as written:

  1. Amending the already-published 0.1.182 entry to claim "Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977: update visibility is silent by default" writes false history — the original text ("Only this fix, on top of v0.1.181") is actually correct for 0.1.182.
  2. README en/zh "silent by default since v0.1.182" points users at a version that still nags on recommended/pending-restart — actively misleading.

Fix plan (labeled additive commit, same branch): restore the 0.1.182 entry verbatim, add a 0.1.183 entry carrying the #1977 note (tier routine, ≤400-char validated), point the README paragraphs at v0.1.183. Everything else in the PR verifies true (OpenCode-only fetchStaleNotice wiring at src/agent/opencode-acp-command.ts:133 vs pi.ts:573 / dsh statusOutcome; visible: critical gate at src/update-notes.ts:193; validator rules reproduced locally).

Record-correction note: #2079 floor 2 asserted "Both policy changes shipped in v0.1.182" — that verification was against master state, not the tag; correcting it here.

ranxianglei pushed a commit that referenced this pull request Oct 4, 2026
… in v0.1.183, not v0.1.182

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.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

Review 完成。发现一处核心事实错误,已按「小问题直接修」在 PR 分支上以标注 commit 修掉(e3b4b77,CI 14/14 全绿)。结构化结论如下:

1. 是什么问题
本 PR 是 #2079 的 docs-only 跟进:让「更新提示默认静默」(#1977)这一行为变更在 release notes 与 README en/zh 中可见。Review 中发现其版本归属写错:PR 声称该行为随 v0.1.182 发布并据此改写已发布的 0.1.182 条目、README 写 "since v0.1.182" —— 实际它随 v0.1.183 发布。

2. 什么原因导致的
撰写 PR 时按 master 状态而非 release tag 验证:#1977 (78276c0) 与 #1603 /acp stale line (a2999ff) 合入 master 后是在 v0.1.183 发布分支切出前进入的;而 v0.1.182 走 carve-out 通道(#2011)从只含该单修的分支切出,tag 内容与 master 状态脱节。证据(三路独立一致):① tag 祖先关系——两 commit 均非 v0.1.182 祖先、均为 v0.1.183 祖先;② npm billion-context@0.1.182 实际产物 dist/index.js 中无 CRITICAL UPDATE READY/AVAILABLE、无 fetchStaleNotice;③ GitHub Release v0.1.183(npm 已上线)What's Changed 明列 fix(#1977)。#2079 floor 2 早前"shipped in v0.1.182"的判断同源出错,在此更正记录。

3. 怎么修复的
commit e3b4b77(docs(#2079 review): correct version attribution):① 0.1.182 条目逐字还原为原发布文本——原文("Only this fix, on top of v0.1.181")本就正确,无需修正,PR 的改写反而是写入虚假历史;② 新增 0.1.183 条目承载 #1977 说明(tier=routine,summary 367 字符,本地复跑 release-notes.yml 全部 validator 约束通过,schema/数量≤20/semver/去重/tier 枚举/长度/date);③ README en/zh 两处 "since v0.1.182 / 自 v0.1.182 起" → v0.1.183。作者其余内容(OpenCode-only 限定句、staleness cues 段、#2084 引用)未动。

4. 是否有回归问题
无代码改动,纯文档。既有行为逐项过:已发布的 0.1.182 条目文本保持与 npm 上真实发布一致(companion 包合并后 republish 不会覆盖为错误历史);新 payload 通过 validator(本地跑过,CI 侧 release-notes 工作流将在合并后 push 触发时再验一次);PR 其余声明逐一核实为真——fetchStaleNotice(src/agent/shared.ts:293)唯一调用点 src/agent/opencode-acp-command.ts:133,pi.ts:573 与 dsh statusOutcome 均不调用 → OpenCode-only 表述准确;visible: critical 门(src/update-notes.ts:193)、CRITICAL UPDATE READY/AVAILABLE 文案(src/acp-status.ts:164-166)、advisory (#1481) 为唯一自动可见严重路径——均与代码一致。无阈值/时序/输出格式漂移;"Behavior change disclosure: None" 一节维持成立。

5. 是否破坏缓存
不涉及。

6. 是否改了设计方向
无架构变化。两个判断点报备:① 0.1.183 条目 tier 定为 routine(先例:0.1.181 精度波次同为 routine;且 #1977 下 routine/recommended 对用户均不可见、纯记录元数据——若你想标 recommended 说一声即可改);② issue 标题写 "0.1.182 notes",但 OP 正文本身是 "v0.1.182/183",证据明确归属 0.1.183,故按证据改投目标而非标题字面。

7. 是否引入了新的配置
无(update.visibility opt-in knob 维持刻意不加,与 PR 立场一致)。

判定:可合并(mergeable=true;base 落后 master 两个 commit,仅 package.json/lock 版本行,与本 PR 三文件零重叠,非阻塞)。CI 14/14 全绿(head e3b4b77)。请人工合并:#2085

@ranxianglei

Copy link
Copy Markdown
Owner Author

冲突

ework-agent added 2 commits October 4, 2026 22:30
… in v0.1.183, not v0.1.182

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.
@ranxianglei
ranxianglei force-pushed the 2026-10-04_update-visibility-docs branch from e3b4b77 to 2b1fb92 Compare October 4, 2026 14:33
@ranxianglei
ranxianglei merged commit 2f9cc00 into master Oct 4, 2026
14 checks passed
@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.21-master.2f9cc00 (rolling master tag).

npm install -g billion-context@0.0.21-master.2f9cc00  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[docs/ux] #1977: pending-restart updates have no persistent surfacing anymore (critical-only visibility)

1 participant