Repository navigation
chore: pin acp-kernel 0.0.91 - #1331
Conversation
Picks up #422/#421: syncBlocks no longer crashes processTurn on id-less host-shaped messages (0.0.90 regression from the #233 subid-coverage pass; every earlier release silently digested that shape). No bili-side changes required — both lanes normalize ids on their own paths; this keeps the pinned floor at the fixed kernel.
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-1331Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr1331.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Review complete — mergeable. Verified independently, not just trusting the pre-flight claims: ① Direction (original issue): Confirmed the fix exists where claimed. Pulled both published tarballs and diffed them: ② Regression audit (version window 0.0.90→0.0.91): Full dist diff = that single hunk only; the two packages' ③ Code & diff cleanliness: Exact pin, no caret (spec §2 decision #5 honored); lockfile refreshed with new integrity hash; 5 lines total, every line on-purpose. Branch sits directly on current master tip (60df397) — no stale-base risk. ④ CI: All 11 checks green on head 71bf3f2 (test ubuntu 22/24, windows 22/24, e2e + real-client lanes, hermetic registry e2e, version-guard, build-artifact);
No action needed from me — merge is human-only: #1331 一句话中文摘要:审核通过——kernel 0.0.91 相对 0.0.90 仅含 #422 的 syncBlocks 空 id 守卫这一处改动(已拉两个 tarball 逐行比对确认),bili 侧只动版本钉与 lockfile,CI 11 项全绿,无回归,可以合并。 |
Pin bump
acp-kernel0.0.90 → 0.0.91 (exact pin, lockfile refreshed).What it picks up
syncBlocksno longer feeds id-less host-shaped messages intobaseIdOf. Every release before 0.0.90 silently digested that shape; 0.0.90's subid-coverage pass (fix: legacy billion-context-pi entry wrongly suppressed launcher -e injection #233) turned it into a hardprocessTurnTypeError. Surfaces via kernel 0.0.90 in pi-side tests (billion-context-pi#536) and any consumer that passes unnormalized entries.Pre-flight (pinned 0.0.91)
No bili-side code changes required — both compression lanes normalize ids before the kernel sees them; this keeps the pinned floor on the fixed kernel. After this lands, master is ready for the 0.1.150 release (refold wiring #1316, receipt enhancements #1298, pi dead-path fix #1319, overflow-refold retry #1328).