Repository navigation
docs(#2079): surface the #1977 update-visibility change in the 0.1.182 notes and README en/zh - #2085
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2156-pr.2085.7396278This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2085.tgz
npm install -g packageInstall instructions are refreshed on each push. |
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
Consequences for this PR as written:
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 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. |
… 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.
Review 完成。发现一处核心事实错误,已按「小问题直接修」在 PR 分支上以标注 commit 修掉(e3b4b77,CI 14/14 全绿)。结构化结论如下: 1. 是什么问题 2. 什么原因导致的 3. 怎么修复的 4. 是否有回归问题 5. 是否破坏缓存 6. 是否改了设计方向 7. 是否引入了新的配置 判定:可合并(mergeable=true;base 落后 master 两个 commit,仅 package.json/lock 版本行,与本 PR 三文件零重叠,非阻塞)。CI 14/14 全绿(head e3b4b77)。请人工合并:#2085 |
|
冲突 |
…82 notes and README en/zh
… 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.
e3b4b77 to
2b1fb92
Compare
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.21-master.2f9cc00 # this exact build
npm install -g billion-context@master # always the newest merged build
|
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
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/acpstale-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 //acpline on OpenCode /GET /__bili/status). Propagates automatically: CI republishes the companion package on any master push touchingrelease-notes/**. Locally validated against the workflow's inline checks (schema, ≤20 entries, semver, tier enum, summary ≤400 chars — new one is 381)./acpstaleness-warning claim — it is wired into the OpenCode lane only today (src/agent/opencode-acp-command.tscallsfetchStaleNotice; the piregisterCommand("acp")and dshstatusOutcomehandlers 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.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
/acpstale-install notice missing on the pi/dsh lanes (real gap found while verifying this issue's claims). Three options listed there, including a server-side pre-footer slot that would double as [docs/ux] #1977: pending-restart updates have no persistent surfacing anymore (critical-only visibility) #2079's option-B2 pending-restart hint — design call left to owner.update.visibility) is intentionally deferred: config-surface territory per AGENTS.md, and an always-visible mode would resurrect exactly the nag shape Release-notes visibility should be silent by default (owner decision) — advisories stay the only auto-visible channel #1977 removed. Revisit alongside [update-ux] #1603 /acp stale-install notice is missing on the pi and dsh lanes (README overclaims cross-host coverage) #2084 if owner wants more stale-state visibility.