Skip to content

[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) - #4449

Merged
ranxianglei merged 7 commits into
ranxianglei:masterfrom
Chrockution:2026-10-23_codex-plugin
Oct 24, 2026
Merged

ranxianglei merged 7 commits into
ranxianglei:masterfrom
Chrockution:2026-10-23_codex-plugin

Conversation

@Chrockution

Copy link
Copy Markdown

背景

上游仓库已经有 .claude-plugin/(Claude Code 生态),但没有 Codex 生态的
清单,所以 codex plugin marketplace add ranxianglei/billion-context 装下来的
插件里没有 .mcp.json,codex mcp list 查不到 bili,四个上下文工具
(compress / decompress / search_context / acp_status)在 Codex 里根本不可用。

这个 PR 补上 Codex 侧的清单与 MCP 外壳,让同一份仓库同时服务两个生态。

为什么用 Git marketplace,而不是 npm 源

Codex 的插件更新检测依赖 PluginSummary.version(源宣告)与
localVersion(已装)的差异。实测四种源类型:

源类型 version 字段 能检测更新
local 恒为 null 否
npm 恒为 null(Codex 不解析 registry 版本) 否
git 随上游推进 是
remote 由后端给 是(需 ChatGPT 登录)

只有 Git 源有版本推进语义,而且 Codex 内置了 plugins-marketplace-auto-upgrade
会后台 git pull。所以 README 和安装脚本都引导用户走
codex plugin marketplace add ranxianglei/billion-context。

改动

.agents/plugins/marketplace.json(新增)
Codex marketplace 清单,指向 ./plugins/codex。Codex 的 marketplace 名取自
清单的 name 字段,所以 marketplace 就叫 billion-context。

plugins/codex/(新增)

文件 作用
.codex-plugin/plugin.json Codex 插件清单 + interface(显示名/简介/品牌色/默认提示词)
.mcp.json 注册 bili MCP server
mcp-server.mjs 定位并拉起 dist/mcp.js 的 stdio 外壳
scripts/install.ps1 一键安装
README.md 安装 / 用法 / 排障

mcp-server.mjs 按优先级找入口:BILI_MCP_ENTRY → 全局 npm 安装目录 →
仓库源码布局 → 插件目录自身。全找不到时把已尝试的路径打到 stderr,而不是
静默失败。

必须 spawn 而不是 import():dist/mcp.js 的 stdio 循环只在「作为脚本被直接
执行」时启动(src/mcp.ts:417 的 argv 守卫),被 import 时只会导出
runMcpStdio,不接管 stdin。

scripts/sync-codex-plugin-version.mjs(新增)

以 package.json 为唯一真相源,同步四份清单的版本号。写这个脚本的直接原因是
仓库里已经存在版本漂移:package.json 是 0.1.204,而 .claude-plugin/
还写着 0.1.188 —— Codex 侧会因此显示过期版本,永远等不到「有更新」。

--check 模式供 CI 使用。

.github/workflows/release.yml(修改)

发布前先 --check 校验四份清单与 package.json 一致,不一致直接让 release
失败,避免版本漂移再次进入发布产物。

验证

在 Codex 26.1016(Windows)实测:

  • Git marketplace 装上后 codex mcp list 出现 bili
  • 六个工具可用:compress / decompress / search_context / acp_status /
    acp_cache / acp_read_original_image
  • 模拟上游发新版:codex plugin marketplace upgrade 后已装缓存从 1.0.0
    自动刷新到 2.0.0,插件列表版本同步推进
  • mcp-server.mjs 在插件目录 / 根目录 / 用户目录三种 cwd 下都能定位入口并完成
    MCP 握手
  • npm run typecheck 通过
  • node scripts/sync-codex-plugin-version.mjs --check 通过

兼容性

  • 不改动 src/、dist/、kernel/,不影响现有任何客户端车道
  • plugins/codex/ 不进 npm 包(package.json 的 files 未改动),
    只走 Git marketplace 分发
  • 未修改 package.json 的 version(遵循 AGENTS.md §4:版本只在 release
    分支变更)

已知限制

  • Codex 的 MCP App 不能自我声明为默认常驻侧栏入口
    (visibleByDefault 只对内置 code-review 开放)。用户手动 pin 一次后
    会跨启动保留,README 里已说明。
  • 插件的 MCP server 需要 bili CLI 在 PATH 上(README 有排障说明)
  • 仅装了插件、没跑代理时,工具会出现但 tools/list 报 proxy unreachable;
    要让压缩真正生效需要 bili start 或 bili codex

Codex Adapter added 2 commits October 24, 2026 01:50
把 billion-context 适配成 Codex 桌面版可安装的插件,并让更新检测可用。

为什么必须是 Git marketplace:
Codex 的 PluginSummary.version 只在 Git 源下才有版本语义;local / npm 源的
version 恒为 null,插件页面永远看不到「有更新」。Git 源会被 Codex 识别成
sourceType=git,走内置的 plugins-marketplace-auto-upgrade 后台拉取上游更新。

改动:
- .agents/plugins/marketplace.json:Codex marketplace 清单,指向 plugins/codex
- plugins/codex/:Codex 插件本体
  - .codex-plugin/plugin.json:清单 + interface(显示名/简介/品牌色/默认提示词)
  - .mcp.json + mcp-server.mjs:注册 bili 的 MCP server(stdio JSON-RPC 转发)
  - scripts/install.ps1:一键安装(CLI 检查 → marketplace → 插件 → enable_mcp_apps)
  - README.md:安装、用法、排障
- scripts/sync-codex-plugin-version.mjs:以 package.json 为唯一真相源,同步所有
  插件清单的版本号(顺带修掉 .claude-plugin 里 0.1.188 的陈旧版本漂移)
- .github/workflows/release.yml:发布前校验并同步清单版本,防止版本号漂移
  再次进入 release

验证(本地实测 Codex 26.1016):
- Git marketplace 装上后 codex mcp list 出现 bili,六个工具可用
  (compress / decompress / search_context / acp_status / acp_cache /
  acp_read_original_image)
- 模拟上游发新版:marketplace upgrade 后已装缓存 1.0.0 → 2.0.0,插件列表
  版本同步推进(即插件页面的「有更新」)
- mcp-server.mjs 在插件目录 / 根目录 / 用户目录三种 cwd 下都能定位入口并握手
Follow-up to the Codex plugin manifest work: rebasing onto current master
bumped package.json to 0.1.205, so the four manifests that mirror it had to
move too:

- .agents/plugins/marketplace.json
- plugins/codex/.codex-plugin/plugin.json
- .claude-plugin/marketplace.json
- .claude-plugin/plugin.json

This is exactly the drift the sync script exists to catch: before the script
existed, .claude-plugin/ still said 0.1.188 while package.json said 0.1.204,
which is what makes Codex's plugin page report a stale version.

No behavioral change; `node scripts/sync-codex-plugin-version.mjs --check`
now passes.
@ranxianglei ranxianglei changed the title feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) [PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) Oct 23, 2026
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

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

查重:不重复。 相关条目比对:

  • PR #3176(open):同属「让 Codex 用上 bili」方向,但机制不同——那是 bili plugin install codex CLI 车道(写 ~/.codex/config.toml 的 MCP 块/模型路由/hook/skill),本 PR 走 Codex 原生插件 marketplace(.agents/plugins/marketplace.json + plugins/codex/,codex plugin marketplace add 安装)。两条车道互不冲突、可共存,不判重复。
  • [native] codex: three-mode alignment (proxy / launcher / native plugin) + runtime-info #965([native] codex 三模式对齐,closed):讲的是 config.toml 里 proxy/launcher/native 三模式,与插件生态清单无关。
  • 检索 open+closed 的 issue/PR,无其他覆盖「Codex 插件 marketplace + .mcp.json 清单」的条目。

标签:codex / scope/wiring / p3(新客户端车道功能请求,非缺陷;客户端接入层)

开始按 PR 审查规范做完整审阅(方向 → 回归 → 代码 → 测试有效性 → diff 整洁度),结论稍后以结构化八问给出。

ci-check added 4 commits October 24, 2026 03:54
…nxianglei#4449)

Review alignment for ranxianglei#4449: the original gate sat AFTER 'Create tag' in
release.yml only, and its --check step fails by design under the documented
flow (a release branch carries a package.json bump but not yet synced
manifests) — every release would go red with an orphan pushed tag, and the
manual/bugfix lanes had no gate at all (they would silently ship drift).

- release.yml: move the --check gate before any CI dispatch/tag/publish and
  drop the dead write+git-diff tail (the check already exits on drift); the
  synced manifests now ride as their own commit on the release branch
  (reference/release.md step 3.5)
- release-manual.yml: run the sync inside its in-CI bump step and widen the
  'Verify bump diff' allowlist to the four manifest files
- release-bugfix.yml: add the same --check gate against the frozen head
The new release gate fails unless release branches carry a manifest-sync
commit, so the flow must say how to produce one: AGENTS.md §5 lists the step
and its rationale; reference/release.md gains step 3.5 (run the sync script
after the bump, own 'chore:' commit, idempotent) and the bugfix carve-out
process now requires the synced manifests on the frozen head.
…bustness (ranxianglei#4449)

Review alignment for ranxianglei#4449:

- install.ps1: read/write config.toml through [System.IO.File] instead of
  Get/Set-Content — PS 5.1 Get-Content decodes as ANSI/GBK and would write
  mojibake back over non-ASCII (e.g. Chinese comments); Set-Content -Encoding
  UTF8 adds a BOM under 5.1 (double-BOM edge). Also resolve codex once up
  front with a clear error instead of invoking a potentially null command.
- mcp-server.mjs: the header comment listed the probe priority in the wrong
  order (code prefers the repo layout over a possibly-stale global install —
  keep the code, fix the comment); drop two candidate paths that can never
  resolve ('npm prefix -g' joined as an install dir, and an _npx layout that
  does not match npx's real <hash>/node_modules structure) — zero behavior
  change; handle child spawn 'error' instead of crashing on an unhandled event.
- .mcp.json: pass through XDG_CONFIG_HOME/XDG_DATA_HOME/XDG_STATE_HOME/TMPDIR
  alongside HOME for Linux/macOS completeness.
- README.md: list all four lookup tiers in the troubleshooting section.
…anglei#4449)

Hermetic regression tests for the two load-bearing pieces of ranxianglei#4449 that had
no coverage:

- codex-plugin-version-sync.test.ts: runs the real sync script against a temp
  fixture — --check must fail (exit 1, naming every drifted file) when the
  manifests lag package.json, pass when aligned, converge without clobbering
  untouched manifest fields, stay idempotent, and skip a marketplace with no
  billion-context entry instead of drifting it.
- codex-mcp-shell.test.ts: copies the real shell two levels deep so its
  repo-layout probe cannot hit a real build — no resolvable entry must exit 1
  listing every attempted path, repo layout must win over plugin-dir self,
  stdio must relay byte-exact from a foreign cwd, and SIGTERM must reach the
  MCP child (POSIX runners).
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

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

PR #4449 审核结论(外部贡献,按规范直接对齐重构)

方向正确、schema 全部核实无误,但原稿的 release 校验门在文档化发布流程下必然失败(回归),另有若干健壮性缺陷。已按「外部提交质量不达标即直接对齐重构」的规范把修复作为 4 个附加 commit 推到了你的分支(af8e5dc80,不替换你的原始提交),等 CI 绿后由人合并。

独立验证做了什么(不复述 PR 描述):

  • 逐个字段对照 openai/codex 主源码的 serde 定义(marketplace / plugin manifest / mcp-types)——四份清单与 .mcp.json 的所有字段、路径前缀 ./、policy 取值全部合法;.agents/plugins/marketplace.json 在 Codex 的发现顺序里优先于 .claude-plugin/,两个生态互不干扰。
  • 决定性实验:模拟下一次发布分支(package.json +1、清单未同步)跑原稿的 --check → exit 1。证实原稿门禁自相矛盾:它放在 Create tag 之后,而文档化流程里 release 分支只有版本号 commit、没有清单同步 commit → 每次发布必红,且 tag 已经推出去了(孤儿 tag)。manual / bugfix 两条发布通道则完全没有校验,会静默放行漂移。
  • 实测 mcp-server.mjs:字节级透传、cwd 无关、SIGTERM 转发到子进程、缺入口时 stderr 列出全部尝试路径并 exit 1——PR 声称的行为都成立。
  • 修复后在 PR head 上跑新门禁:四份清单与 package.json 一致,通过。新增 8 个 hermetic 测试本地全绿,typecheck 干净,全量套件交给 CI。

结构化八问

  1. 是什么问题:给仓库补 Codex 生态的插件清单 + MCP 外壳(功能 PR)。审核发现的实质问题是:新加的「发布前版本一致性校验」按文档化流程永远通不过,会把后续所有发布卡死;外加安装脚本会损坏 Windows 用户的 config.toml 等非 ASCII 内容等几处缺陷。
  2. 什么原因导致的:门禁步骤被放在打 tag 之后、且假设发布分支上清单已经同步——但既有发布流程(AGENTS.md §5 / reference/release.md)只要求 bump package.json,没有任何一步产出同步后的清单;作者自己的脚本注释也承认仓库里已经漂了 16 个版本(0.1.188 vs 0.1.204),说明这个前置条件从来没被满足过。其余是逐点缺陷:文件头注释把探测优先级写反、两条永远不会命中的全局 npm 探测路径、PS 5.1 默认 ANSI/GBK 读写编码、spawn 无 error 处理。
  3. 影响范围与严重程度:不修的话——从下一次发布开始所有发布通道红灯(release 流水线不可用,属 p1 级);已装用户侧——仅 Windows 上跑 install.ps1 且 config.toml 含非 ASCII 的用户会被写回乱码(数据损坏类,低频但严重);MCP 探测死路径零行为影响。src/、kernel/、wire 均未触碰,现有客户端车道不受影响。
  4. 怎么修复的:把门禁移到任何 dispatch/tag/publish 之前、简化为纯 --check(原来的「写入+diff」尾巴是死逻辑);让「清单同步 commit」成为发布分支的正式步骤(AGENTS.md §5 + reference/release.md 新增 step 3.5,幂等、空提交可跳过);manual 通道在 CI 内 bump 时顺带同步并放宽 diff 白名单到 6 个文件;bugfix 通道对冻结 head 提前校验。安装脚本改用 .NET File API 恒定 UTF-8 无 BOM 读写;shell 修注释、删死路径、补 spawn error 处理;补 XDG_*/TMPDIR 环境变量透传;新增两个测试文件把门禁双向行为(漂移必红/对齐必绿/收敛不改坏其他字段)和 shell 四个行为钉死。
  5. 是否有回归问题:逐项审过——① release.yml 既有步骤(分支判定/CI dispatch/tag/publish)顺序与语义未动,只在最前面插了一步;② manual 通道 "Verify bump diff" 从「恰好 2 个文件」放宽为「⊆ 6 个文件的白名单」(有意变更,见下 feat: release CI (npm auto-publish on release branch) #8 披露,保留了对意外文件的拦截和空变更检查);③ shell 删除的两条探测路径经代码走查确认永不命中(npm prefix -g 的输出被拼成 <prefix>/billion-context/... 不是真实安装位置;npm-cache/_npx/<name> 不符合 npx 真实的 _npx/<hash>/node_modules 布局)→ 零行为变化;④ stdin EOF 传播、信号转发、透传字节一致均实测保持;⑤ npm tarball 内容不变(files 字段未动)。高危模式(fail-fast 变吞错、阈值/时序漂移、输出格式变化)逐项排查无命中。
  6. 是否破坏缓存:不涉及——未触碰缓存/重试/游标/去重策略。本 PR 保护的插件缓存版本检测逻辑反而因门禁而更可靠。
  7. 是否改了设计方向:无架构转向。Codex 车道沿用既有 .claude-plugin 模式,Git marketplace 是四种源类型中唯一有版本推进语义的,选型成立。唯一的方向性补充是发布流程多了一个强制步骤(见下)。
  8. 是否引入了新的配置:审核方未引入任何新 env/config/CLI。PR 自带的 BILI_MCP_ENTRY(显式入口逃生舱)合理且已在 README 说明。

行为变更披露(旧值 → 新值,均有原因)

# 变更 旧 → 新 原因
1 .claude-plugin 两份清单版本(作者提交) 0.1.188 → 0.1.205 修复历史漂移;后果:Claude Code 用户会收到一次插件更新通知(一次性)
2 发布流程(我的修复) release 分支无需同步清单 → 必须带一个 chore: sync plugin manifests to vX commit 否则新门禁红灯;已写入 AGENTS.md §5 与 reference/release.md step 3.5
3 三条发布工作流 无清单校验 → tag/publish 前 --check,漂移 = 红发布 防止版本号漂移再次进入发布产物(本 PR 的直接动机)
4 install.ps1 对 config.toml 的读写 Get/Set-Content(PS 5.1 下 ANSI 解码 + UTF8 带 BOM)→ .NET API 恒定 UTF-8 无 BOM 消除乱码写回与双 BOM 边界
5 Codex 插件页显示版本 可能停在过期值 → 随上游推进 Git marketplace + 同步门禁的共同效果(本 PR 目标)

遗留(不在本 PR 范围,供参考)

  • Codex MCP App 不能自我声明为默认侧栏入口(visibleByDefault 仅对内置 code-review 开放)——作者已知限制,README 已说明需手动 pin。
  • 仅装插件未跑代理时工具报 proxy unreachable——预期行为,README 排障节已覆盖。

判定:可合并(人类操作)。等 af8e5dc80 上的 CI 全绿即可 merge:#4449

标签:pr / codex / scope-wiring / p3(功能类非缺陷;p3 = 新增车道,无存量用户受影响,核心风险在发布流程已由门禁兜住)。

@Chrockution

Copy link
Copy Markdown
Author

感谢审阅和直接重构,4 个修复 commit 已确认(af8e5dc8)。本地已同步验证:

  • node scripts/sync-codex-plugin-version.mjs --check → exit 0,四份清单一致(0.1.205)
  • 新增两个测试文件 7 passed / 1 skipped(SIGTERM 仅 POSIX)/ 0 failed

10 个 workflow 目前都是 action_required(fork PR 首次运行需维护者批准),麻烦帮忙 Approve and run。CI 绿后请直接合并,我不再改动分支。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

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

收到,你本地那组数字(7 passed / 1 skipped)和预期完全吻合——SIGTERM 转发那条测试按设计只在 POSIX runner 上跑(Windows 的 kill() 是模拟信号,无法验证真转发),ubuntu shard 上会是 8/8。

两件事都帮不上,说明一下原因:

  1. Approve and run:GitHub 对 fork PR 首次运行的待批准 workflow 没有开放 API,「Approve and run」只能在 Actions 页面由维护者手动点。请 owner 到 https://github.com/ranxianglei/billion-context/actions 把 af8e5dc8 上的 10 个 pending 运行逐个批准。
  2. 合并:仓库规则(AGENTS.md §4)规定 PR 合并是 human-only,agent 一律不合并——这条对外部贡献者的请求同样适用,所以「CI 绿后直接合并」需要 owner 自己操作:[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449

CI 结果出来我这边会自动跟进:任何 lane 红了我会直接定位并修;全绿就等 owner 点合并。分支保持不动即可。

@ranxianglei
ranxianglei merged commit 751c354 into ranxianglei:master Oct 24, 2026
31 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.789-master.751c354 (rolling master tag).

npm install -g billion-context@0.0.789-master.751c354  # 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.

ranxianglei pushed a commit to abworks-dev/billion-context that referenced this pull request Oct 24, 2026
ranxianglei#4449 added tests/codex-mcp-shell.test.ts and
tests/codex-plugin-version-sync.test.ts; both match the SPAWN_RE
tripwire but were never registered in scripts/live-files.mjs, so every
CI test shard dies at startup before running a single test (red master
since 751c354, inherited by all open PRs).

Concurrency review required by the tripwire:
- codex-mcp-shell.test.ts spawns node MCP-server children over stdio
  only — no port binding, temp dirs only;
- codex-plugin-version-sync.test.ts execFileSyncs
  sync-codex-plugin-version.mjs against mkdtemp fixtures — no ports.
Both are safe under --test-concurrency 4; their zone bands stay unused.

Appended per the append-only slot rule in live-files.mjs. Verified by
replicating run-ci-tests.mjs's full-set tripwire scan locally.

No bili behavior change.
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
…_FILES

Both files landed on master via af8e5dc (#4449) without LIVE_FILES
registration, so the run-ci-tests process-spawn tripwire fails every
shard of every PR branch (inherited red master, unrelated to this PR's
change). Neither binds a port: codex-mcp-shell coordinates its spawned
shell child via ENTRY_REPORT_FILE, codex-plugin-version-sync runs
execFileSync synchronously. Appended at list end (slot = index).
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
ranxianglei added a commit that referenced this pull request Oct 24, 2026
…_FILES (#4449 follow-up)

#4449 landed two process-spawning suites without registering them, so
every test shard now aborts at startup ('process-spawning test files
missing from LIVE_FILES') on master and all open PRs. Same disease as
#4333/#4334 — register them.
ranxianglei pushed a commit that referenced this pull request Oct 24, 2026
The previous head's merge ref predates 5ac5428 (LIVE_FILES registration for the two #4449 suites), so both the original run and rerun-failed-jobs fail the #1248 tripwire on a stale tree. Empty commit to force a fresh pull_request run on the current base; no content change.
@Chrockution

Copy link
Copy Markdown
Author

Thanks for reviewing and merging this PR! 🎉

A short note on how this is being used downstream, in case it is useful for future
changes to plugins/codex:

What landed

  • plugins/codex/ — the Codex Desktop plugin: .codex-plugin/plugin.json,
    .mcp.json, mcp-server.mjs, README.md and scripts/install.ps1.
  • scripts/sync-codex-plugin-version.mjs — keeps the Codex/Claude manifests in
    sync with package.json, so the marketplace manifest, the plugin manifest and
    the npm version never drift apart.
  • tests/codex-mcp-shell.test.ts and tests/codex-plugin-version-sync.test.ts —
    cover the MCP shell behaviour and the version gate.

Verified locally

  • node scripts/sync-codex-plugin-version.mjs --check — clean (all four manifests
    report the same version as package.json).
  • node --import tsx --test tests/codex-mcp-shell.test.ts tests/codex-plugin-version-sync.test.ts
    — all green (the SIGTERM case is POSIX-only, so it is skipped on Windows).

Observed in the Codex desktop app

  • The plugin installs from a Git marketplace and registers the bili MCP server
    (compress / decompress / search_context / acp_status / acp_cache).
  • Routing the model traffic through the local proxy
    (http://127.0.0.1:8787/bili/http://127.0.0.1:<upstream>/v1) enables the
    proxy-mode compression path: the effective context window is aligned to the
    model window, and healthy sessions keep a ~95–97% prefix-cache hit rate.
  • codexCompact handling in the proxy works as documented.

One thing worth confirming

plugins/codex/.codex-plugin/plugin.json and .agents/plugins/marketplace.json
are currently at 0.1.205 while package.json is at 0.1.206. I assume the
release workflow runs scripts/sync-codex-plugin-version.mjs before publishing,
so the Codex marketplace advertises the version that actually contains the
plugin. If that is not the case for the next release, the plugin version would
need a manual bump.

Thanks again — happy to pick up any follow-up issues on the Codex side.

ranxianglei added a commit that referenced this pull request Oct 24, 2026
…ane-guard

[PR] fix(release): train mode survives pre-#4449 patch lanes
yanhuojiyusheng pushed a commit to yanhuojiyusheng/billion-context that referenced this pull request Oct 24, 2026
…guard the manifest-sync script call and the manifest git-add (both fatal on lanes cut from tags older than b87732e)
ranxianglei pushed a commit that referenced this pull request Oct 25, 2026
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 pushed a commit that referenced this pull request Oct 26, 2026
…lane, missing-manifest gate, autoFold docs

Three unfixed items from the #4725 review ledger (#4757 landed separately via
the ci-fixes sweep):

- release-bugfix.yml lost the #4449 manifest --check when the v3 lane rewrite
  landed (v0.1.208 ran it before Publish guard; master's rewrite dropped it).
  Ported back with the #4576 pre-#4449 lane existence guard, gated on the
  resolve step's actual proceed output (this variant has no path output).
- scripts/sync-codex-plugin-version.mjs silently SKIPPED a missing manifest
  file — in --check mode a missing file greened the gate, neutering the
  release guard. A missing target is now a hard error naming the file; the
  four manifests are a fixed contract. Regression test added (RED on the old
  skip).
- CONFIGURATION.md en+zh: document the autoFold benefit gate (#3444: growth
  folds arm only on ≥4096 tokens over the effective target; sub-4096 saving
  arms the backoff; image-dominant exempt) and the measured floor (irreducible
  baseline raises an unreachable target, never above the window). Both
  languages in sync.

Sync tests 5/5, typecheck clean.
ranxianglei added a commit that referenced this pull request Oct 27, 2026
The 0.1.208 carve-out lane shipped off the v0.1.207 tag (storage v8
emergency, #4677) without landing a version bump on master, so master's
package.json (0.1.207) no longer equals npm latest (0.1.208) and the
one-click release drift guard aborts (run 40520077248, step 'Drift
guard'). Version-string sync ONLY: master already carries the 0.1.208
content under its own commits (#4708 for #4677, #4666). Plugin manifests
synced via scripts/sync-codex-plugin-version.mjs (#4449) so the publish
workflows' --check gate stays green. No code change; branch deliberately
does NOT match *_release-v* so merging publishes nothing.
@github-actions github-actions Bot mentioned this pull request Oct 27, 2026
abebatista pushed a commit to abebatista/ranxianglei-billion-context that referenced this pull request Nov 1, 2026
…anxianglei#5430) on top of the reverted flow, with four regressions fixed

ranxianglei#5446 ('恢复老的ci release manal') restored the classic pre-flight npm ci +
typecheck + build and dropped today's emergency buttons. Owner decision
(2026-11-01, incident): keep BOTH — the old full-CI normal path AND the
emergency channel. This restores release-manual.yml from 1115455 (the last
state that had the channel, i.e. ranxianglei#5430-era workflow) and adds back the single
line ranxianglei#5446 kept: npm ci inside the Pre-flight gate. Net effect vs master:

A. skip_ci_gate + raw_publish inputs, Raw emergency publish step and all the
   if-conditions that wire them — back. Emergency = deps download + build +
   publish, zero CI, no master push, tag + GitHub Release + version-sync PR.
B. Full CI dispatch again carries CI_FULL_DISPATCH=1 — direct releases
   dispatch the COMPLETE lane set at the publish sha, not ci.yml's CORE
   default (the ranxianglei#3539 windows/node24 gap ranxianglei#5446 reopened).
C. Bump version syncs the plugin manifests via scripts/sync-codex-plugin-version.mjs
   and Verify bump diff accepts them again (ranxianglei#4449).
D. job timeout-minutes: 90 is back — a wedged release run can no longer pin
   the one-click-release concurrency group for hours.
E. Drift guard keeps its pending-bump state (ranxianglei#5376) instead of hard-failing
   whenever master leads npm by one patch.

Plus the ranxianglei#5445 fix folded in: on the raw_publish path a master/npm version
skew (the state right after emergency publish ranxianglei#1, before its version-sync PR
merges) logs a loud audit warning instead of exit 1 — back-to-back emergency
publishes work. The duplicate-publish guard (npm version already exists) stays.

Verified: YAML parses; inline scripts of Drift guard / Raw emergency publish /
Bump version pass bash -n.
ranxianglei pushed a commit that referenced this pull request Nov 13, 2026
The previous head's merge ref predates 5ac5428 (LIVE_FILES registration for the two #4449 suites), so both the original run and rerun-failed-jobs fail the #1248 tripwire on a stale tree. Empty commit to force a fresh pull_request run on the current base; no content change.
ranxianglei pushed a commit that referenced this pull request Nov 14, 2026
The previous head's merge ref predates 5ac5428 (LIVE_FILES registration for the two #4449 suites), so both the original run and rerun-failed-jobs fail the #1248 tripwire on a stale tree. Empty commit to force a fresh pull_request run on the current base; no content change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants