Repository navigation
[PR] chore: sync plugin manifests to 0.1.207 - #4735
ranxianglei wants to merge 16 commits into
Conversation
…ment #4316 PR3/3 (restampRefsToLedger) re-homes citation numbers once on every full-mode cold load; goldens pinning exact ref numbers are born-red. Re-pin the 7 storage-lane tests (engine-proofs x6 + orphan-recovery x1) modulo that renumbering — zero production code touched. - golden-storage-drive.ts: per-turn citation-normalized digest (shaCiteNorm) and state digest modulo stripOneTimeAlignment (stateDigestAligned); the deep-sort helper is hoisted into golden-canonical.ts for sharing. - corrupt-index-child.ts: new stripOneTimeAlignment normalizer — strips the refLedgerAligned stamp and re-homes refs onto canonical raw-id order so a clean full-mode read and the legacy fallback load compare equal. - storage-engine-proofs.test.ts: wire legs assert shaCiteNorm equality vs the legacy restart leg and the committed goldens; state legs assert stateDigestAligned; rollback leg now spells BILI_STORAGE_UNIFIED=legacy explicitly (#3818 flip: absent resolves to full, deleting the env would vacate the legacy path). - storage-orphan-recovery.test.ts: pins the content-addressable byRaw->byRef round-trip instead of a counter-era m00003 literal. - golden/storage-render/*.json regenerated with shaCiteNorm/stateDigestAligned. Converges the master-red storage-lane family (#4599 plan A, owner directive).
The four plugin manifests (.agents/plugins/marketplace.json, .claude-plugin/marketplace.json + .claude-plugin/plugin.json, plugins/codex/.codex-plugin/plugin.json) sat at 0.1.205 while package.json is 0.1.207 — the #4449 gate (node scripts/sync-codex-plugin-version.mjs --check) fails on master, so any release branch cut now would be rejected by release.yml's pre-tag check, and the Codex/Claude marketplaces have not offered updates since v0.1.206. Run the sync script (no code changes).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5959-pr.4735.3010d31This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4735.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) 收到。这是已完成的 [PR] 工作(正文带 agent PR 标记),不重做——正在核对:① diff 是否确实只有 4 个 manifest 各 1 行版本号变更;② master 上 |
(ai: vllm-qwen/qwen3.8-27b) 审核结论:内容正确、可合;CI 红为继承性,已在分支上同步 ci-fixes 重跑中。 查重:不重复——无其他 open issue/PR 覆盖同一 manifest 漂移;关联项即本 PR 指向的 #4729(已链接)。 逐项核对(全部实测,非读 PR 描述):
CI(原 head 2e74143):静态门禁/guard/build/e2e 车道全绿;5 个 test 分片红 = 继承性失败。已逐片下载日志核对,失败用例全部落在 #4599 在册的 master 级簇:storage-render golden wire ×4(#4571 engineLane 戳导致 metadata digest 漂移)、storage-engine-proofs full-mode ×4 + rollback + corrupt-db(#4316 restamp 簇)、orphan-freeze cold load、plugin-fork A 族(待 #4652)、web-blogfeed probing + runLaunch opencode-inline(master 级红)。master head bb7c249 自身同签名 6 片红(u22s3/u24s3/w22s2/s3/s4/s5)⊇ 本 PR 的 5 片,与本 PR diff(4 个 JSON 版本号)零交集。ci-fixes 哨兵(18f5146,存储车道 re-pin)已合入分支(并行会话先推的 merge commit 八问:
判定:PR 内容验证通过(diff 精确、门禁红→绿实测成立),等重跑 CI 转绿后即可由 owner 合并;若重跑后仅剩在册 master 簇残留红,那属于 #4599 哨兵车道的事,不构成拦本 PR 的理由。 |
…dger parity masks The #4316 one-time renumbering restamped messageRefs but left state.tokenSnapshot keyed by the OLD refs, so post-restart bodies carried stale per-message token counts (1.3K vs 1.4K) and the full-mode-restart wire drifted off the legacy baseline (#4599). persist.ts: two-pass remap (stage moves, delete old keys, then write new keys) so entries whose new ref collides with another move's old ref survive; fires only when superseded refs exist. Aligned normalizer (corrupt-index-child.ts): the cacheLedger's segment bookkeeping (be/bl/bs, unfinalized tail line), the derived agg block, and per-line miss-attribution (prov/seam) are restart experience, not content — no-restart and restart legs legitimately differ there. Masked in the aligned view only; raw digests keep full accounting. Goldens regenerated (stateDigest + aligned). storage-engine-proofs 12/12, golden-storage-render 5/5 locally.
(ai: vllm-qwen/qwen3.8-27b) CI 重跑(新 head 逐片核对(5 个红分片日志全量下载比对两轮):
判定维持:PR 内容验证通过(diff 精确、门禁红→绿实测成立、无回归),等上述 master 车道簇收敛后 CI 即转绿;若 owner 不想等,这些残留红均已有 #4599 归因与修法,不构成拦合本 PR 的理由。合并权在你。 |
…persisted state (#4599) The fork-survival test asserted immediately after the compress tool response, but the fold lands in the live session state asynchronously (#3573 replay semantics). Slow CI runners persisted the pre-fold state ('0 block(s) (compressions=0)' cold load) and the deepEqual diverged. Bounded 5s wait on the in-memory fold; fast machines exit on the first iteration. Product semantics unchanged.
The #4316 cold-load alignment reads the unified sidecar; its ingest of just-flushed records completes asynchronously. Slow runners compared the pre-ingest state and saw refLedgerAligned missing while the fold itself had landed. Poll (bounded 5s) until the loaded state carries the flag; fast machines exit on the first probe.
Git-for-Windows autocrlf checks the bundled .md posts out with CRLF; the exact-match '---' fences then failed to parse and every post lost its title/excerpt/date frontmatter (Windows CI: 'bundled meet-bili post found' assertion). Normalize CRLF to LF inside parseFrontmatter when the fence is CRLF-shaped; LF content is byte-identical as before. Regression test with a CRLF fixture.
… storage mode (#4599) The #4316 cold-load alignment sets refLedgerAligned only when the unified store is available; config-clean machines (CI runners) run legacy mode where it is an honest skip. The test asserted the flag unconditionally, so every shard carrying this file was born-red on CI while unified-config machines passed. Expectation now mirrors store.replicasAvailable(); verified 49/49 in BOTH modes locally.
(ai: vllm-qwen/qwen3.8-27b) CI auto-fix lane(attempt 1/2)结论:继承性失败,已 merge ci-fixes 新 tip 重跑;无需 decision request(残留红均已在 #4599 在册归因,非待拍板项)。 查重:不重复——本条是 #4735 自身 CI 的协调重触发,无新 issue/PR 覆盖;处理全程按 #4599 CI 总控协议走。 本轮做了什么(全部实测):
八问:
判定:新 head |
…mspec wrap on win32 (#4599)
The ci-check lane's expectation change (c496cfb) exposed a real Windows bug: stripInheritedProxy builds inlineEnv as a spread copy of process.env, which keeps the original key casing (ComSpec) — Windows env vars are case-insensitive but plain objects are not. planClientSpawn's exact env.COMSPEC probe then missed it and silently degraded every wrapped spawn to the bare-name 'cmd.exe' fallback (verified by repro on a real win32 box: childEnv.COMSPEC=undefined while process.env.COMSPEC was set). Fix: probe COMSPEC/ComSpec/comspec in planClientSpawn and planDshSpawn. Verified on real Windows (Node 22): launcher-opencode-inline + fix-679 + dsh-refresh 37/37; host tsc clean, 35 pass / 2 win32-skips.
…OMSPEC case-probe c496cfb re-derived the win32 expectation from ambient process.env, which still mismatches production: Node's process.env member access is case-insensitive on Windows while the child env handed to the planner is a plain object whose key keeps the OS casing (ComSpec), so the exact env.COMSPEC probe fell through to the bare-name fallback. The assertion now derives from the child's OWN captured env/options and probes COMSPEC/ComSpec/comspec exactly like planClientSpawn does post-dfeea8a11 — self-contained under any concurrent-test env churn in single-process CI shards — and additionally pins windowsVerbatimArguments=true on the wrap.
(ai: zhipuai-lb/glm-5.3)
Fixes #4729
四个插件市场 manifest 停在 0.1.205,
package.json是 0.1.207 —— master 实测node scripts/sync-codex-plugin-version.mjs --checkexit 1,从 master 切任何 release 分支会被release.yml:46拒发;Codex/Claude 市场自 v0.1.206 起不再提示更新。本 PR 只跑同步脚本(4 个文件各 1 行版本号 0.1.205→0.1.207),无代码变更,--check已验证转绿。package.json(0.1.207),本 PR 不碰版本号本身