Skip to content

[PR] chore: sync plugin manifests to 0.1.207 - #4735

Closed
ranxianglei wants to merge 16 commits into
masterfrom
2026-10-25_sync-plugin-manifests
Closed

ranxianglei wants to merge 16 commits into
masterfrom
2026-10-25_sync-plugin-manifests

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

(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 --check exit 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 不碰版本号本身
  • 下一次发版照常在 release 分支上跑同步(§5 流程不变)

ci-check and others added 2 commits October 25, 2026 23:02
…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).
@ranxianglei ranxianglei changed the title chore: sync plugin manifests to 0.1.207 [PR] chore: sync plugin manifests to 0.1.207 Oct 25, 2026
@github-actions

github-actions Bot commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-25_sync-plugin-manifests (e7f105c)

Latest build — install this exact version

npm install -g billion-context@0.0.5959-pr.4735.3010d31

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

Recent builds (commit → version)

commit version build
e7f105c billion-context@0.0.5959-pr.4735.3010d31 build
8d0c118 billion-context@0.0.5859-pr.4735.4ea0174 build
81db313 billion-context@0.0.5829-pr.4735.a2d472c build
99a4edb billion-context@0.0.5775-pr.4735.87e152e build
2e74143 billion-context@0.0.5769-pr.4735.de47fc0 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4735.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

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

收到。这是已完成的 [PR] 工作(正文带 agent PR 标记),不重做——正在核对:① diff 是否确实只有 4 个 manifest 各 1 行版本号变更;② master 上 sync-codex-plugin-version.mjs --check 红 / 分支上转绿;③ CI 状态与可合并性。结论稍后补在本帖。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

审核结论:内容正确、可合;CI 红为继承性,已在分支上同步 ci-fixes 重跑中。

查重:不重复——无其他 open issue/PR 覆盖同一 manifest 漂移;关联项即本 PR 指向的 #4729(已链接)。
标签:bug / codex / claude-code / scope-ci / p2(缺陷修复;涉及 Codex+Claude Code 两个市场 manifest;属发版管线面;p2=用户侧可用但市场不再提示更新、维护侧发版被门禁卡死)。

逐项核对(全部实测,非读 PR 描述):

  • diff:master(bb7c249)..head 恰好 4 个文件各 1 行版本号 0.1.205→0.1.207(.agents/plugins/marketplace.json、.claude-plugin/marketplace.json、.claude-plugin/plugin.json、plugins/codex/.codex-plugin/plugin.json),零代码变更,不碰 package.json(唯一真相源保持 0.1.207)。
  • 门禁红→绿:在真实 master 树上跑 node scripts/sync-codex-plugin-version.mjs --check → exit 1(4 文件全漂移);在 PR head 树上 → exit 0。与 PR 描述一致。
  • release.yml 门禁位置确认:manifest --check 步骤在 is_release 时先于 CI dispatch/tag/publish 执行,漂移即拒发——master 现状下从它切任何 release 分支必被拦。

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 99a4edb53,与我本地合并结果逐字节一致),CI 正在新 head 上重跑,静态门已绿。预期残留红仍是 master 车道待修项(golden 重录 + #4652 等),不阻塞本 PR 的正确性判定。

八问:

  1. 是什么问题:四个插件市场 manifest 的版本号停在 0.1.205,落后 package.json 的 0.1.207,导致发版门禁拒发、Codex/Claude 市场自 v0.1.206 起不再提示更新。
  2. 什么原因导致的:v0.1.206/v0.1.207 走 carve-out/一键通道发布,§5 流程里的 manifest 同步步骤只在 release 分支上跑,其提交从未落到 master,master 上的 manifest 就此冻结在两版之前。
  3. 影响范围与严重程度:用户侧 bili 功能不受影响(手动更新可用),但 Codex/Claude 市场用户收不到更新提示;维护侧任何从 master 切的 release 分支都会被 release.yml 门禁拒发——p2。
  4. 怎么修复的:只跑既有同步脚本把 4 个 manifest 对齐到唯一真相源 0.1.207,不引入新机制、不改脚本本身。
  5. 是否有回归问题:无。审过的既有行为:市场更新探测(版本号对齐后恢复按版本比较,正是设计意图)、发版门禁语义(不变,漂移才拦)、安装/运行时路径(src/dist 零 diff,不受影响);CI 红项逐条归因到 master 继承簇,无本 PR 引入的新红。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及——package.json 仍为唯一真相源,下次发版照常在 release 分支跑同步,[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449 契约不变。
  8. 是否引入了新的配置:无。

判定: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.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

CI 重跑(新 head 99a4edb53,已含 ci-fixes re-pin 18f5146)完成,结论不变:残留红全部是 #4599 在册的 master 车道项,本 PR 零新增红。

逐片核对(5 个红分片日志全量下载比对两轮):

判定维持:PR 内容验证通过(diff 精确、门禁红→绿实测成立、无回归),等上述 master 车道簇收敛后 CI 即转绿;若 owner 不想等,这些残留红均已有 #4599 归因与修法,不构成拦合本 PR 的理由。合并权在你。

ranxianglei and others added 6 commits October 26, 2026 01:03
…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.
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(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 总控协议走。

本轮做了什么(全部实测):

  1. master 红/绿判定:master bb7c249 最新 run 红 6 片(u22s3/u24s3/w22s2/s3/s4/s5/w24s4),失败签名 = storage-render golden ×4、full-mode restart ×4 + rollback contract + corrupt index.db、HTTP fork revision——与本 PR 红分片同簇,继承性成立。本 PR diff 仅 4 个 manifest 各 1 行版本号,与任何测试行为零交集。
  2. 按协议 merge origin/ci-fixes 新 tip 1fa93735d(plugin-fork refLedgerAligned unified-mode-only 修正)进分支并推送,新 head 8d0c1184a,本地 typecheck 绿(merge 仅带入 tests/plugin-fork.test.ts 7+/14-,src 零 diff,无冲突)。CI 已在新 head 起跑。
  3. 逐条分账本轮红项(旧 head 81db313):

八问:

  1. 是什么问题:本 PR 的 CI test 分片红,但红的不是 PR 改的东西——是 master 级在册测试簇在含 master 的所有分支上复红。
  2. 什么原因导致的:master 存在多个在册缺陷簇(restamp/refLedgerAligned 存储一致性簇、win32 launcher 断言簇等),对应测试文件在所有分支恒红;本 PR 的 4 行版本号 diff 不构成任何因果。
  3. 影响范围与严重程度:只影响本 PR 的 CI 判定(要等 master 簇收敛才能全绿);bili 功能零影响(本 PR 无代码变更)。严重度维持 issue 本身的 p2。
  4. 怎么修复的:按 CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 协调协议把哨兵分支 origin/ci-fixes 的最新收敛(含 plugin-fork 修正)merge 进 PR 分支重跑——master 级修复统一由哨兵收敛到 ci-fixes,不在 PR 分支重复修(协议明令禁止)。
  5. 是否有回归问题:无。本轮 merge 只带入一个测试文件改动(已在 ci-fixes 车道验证过),src/dist/配置零触碰;市场更新探测与发版门禁语义不变(前两轮已实测红→绿)。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:无。

判定:新 head 8d0c1184a 重跑中,预期 plugin-fork 簇转绿;若仅剩 opencode-inline(win32 断言,在册簇 #5)与偶发 flake,均属哨兵车道事项,不构成拦合本 PR 的理由——PR 内容正确性前两轮已钉死(diff 精确、门禁红→绿实测)。合并权在你。

ci-check and others added 4 commits October 26, 2026 09:14
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.
@ranxianglei

Copy link
Copy Markdown
Owner Author

(ai: zhipuai-lb/glm-5.3)

已随 PR #4725 合入 master(merge 931c66a),本 PR 内容成为其子集,关闭以避免重复合并。

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Four plugin-market manifests stuck at 0.1.205 while package.json is 0.1.207 — release gate fails, marketplaces stopped offering updates

1 participant