Repository navigation
[PR] fix(ci): unblock master static gates - drop orphaned export and stale duplicate doc rows - #3871
Conversation
… by a bad merge resolution The generated param-ref block in CONFIGURATION.md / CONFIGURATION.zh-CN.md carried two duplicated rows (storage.unified, storage.sqliteAutoDownload): the pre-#3818 spellings alongside the regenerated ones. Re-running tools/gen-config-docs.mjs generate removes exactly those four stale lines; every key stays documented once with current text. Fixes the docs-sync gate red on master since 2026-10-19.
a4f2730 (#3811) introduced maskUrlForPublish with an export, but nothing outside src/log-mask.ts imports it (only maskUrlsForPublish below calls it), so scripts/check-unused-exports.mjs fails with: INTERNAL_ONLY src/log-mask.ts: maskUrlForPublish Dropping the export keyword makes the gate pass again; no behavior change. Same treatment as #2315 applied to maskUrlsInText.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4577-pr.3871.ceda8dcThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3871.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
(ai: vllm-qwen/qwen3.8-27b) Supplementing evidence from the #3876 work (these two red lanes are pre-existing on master and unrelated to any in-flight PR):
|
Commit 66219d4 added externalSummary to COMPRESS_SETTING_FIELDS on this branch; the config-surface guard then fails HERE (leaf compress.externalSummary lacks a seed entry) until #3880's seed lands on master - i.e. merge order mattered: merging this PR first would have put a NEW red on master's own config-surface-guard. This mirrors #3880's exact seed entry (byte-identical, so either PR may merge first and the duplicate is a clean no-op) plus the generator output for it (5 added lines, 0 removed), making this branch self-contained green for both config-surface-guard and docs-sync once the pre-existing master static-gate red (#3870/#3871) clears.
Commit 66219d4 added externalSummary to COMPRESS_SETTING_FIELDS on this branch; the config-surface guard then fails HERE (leaf compress.externalSummary lacks a seed entry) until #3880's seed lands on master - i.e. merge order mattered: merging this PR first would have put a NEW red on master's own config-surface-guard. This mirrors #3880's exact seed entry (byte-identical, so either PR may merge first and the duplicate is a clean no-op) plus the generator output for it (5 added lines, 0 removed), making this branch self-contained green for both config-surface-guard and docs-sync once the pre-existing master static-gate red (#3870/#3871) clears.
(ai: vllm-qwen/qwen3.8-27b) 收到转发的两条评论:#3876 的补充证据是之前 agent 会话(我)发的,无新增信息需要回应;github-actions 的构建通知是纯信息性的,无需动作。借这次唤醒对 PR 现状做了一轮终态确认(全部在推送的 head bdad5b0 上验证,不是本地工作树): 复核结果
现状与待办:PR open、checks 全绿; 合并后的效果:关闭 #3870,master CI 转绿,其余所有在途 PR(如 #3880)的全量套件 CI 自动恢复运行。 查重:不重复——同方向的两条修复尝试 #3877/#3882 已在 #3876 工作中按先来后到关闭为本 PR 的重复项。 判定:可合,无遗留动作。 |
The five ContextView* shapes and ModelSwitchStats are consumed structurally (buildContextView's return value / cache-ledger internals); nothing outside their own files names them, so the #1440 P6 gate flags them as INTERNAL_ONLY. Drop the leading export keyword only - no behavior change. The remaining local gate hit (src/log-mask.ts maskUrlForPublish) is pre-existing master drift tracked by #3870 with fixes in flight (#3871/#3887); deliberately not bundled here.
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.629-master.3d2b0b5 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #3870
Two labeled commits, one per gate, both verified green locally on master @ 39fb841:
docs:regenerate CONFIGURATION.md / CONFIGURATION.zh-CN.md - the generated param-ref block carried two stale duplicate rows (storage.unifiedpre-Storage wrap-up: 6 fixes + switch default mode to full (single PR) | 存储收尾六修 + 缺省模式翻 full(一个 PR 统一处理) #3818unset (shadow)text,storage.sqliteAutoDownload) left inside the marker block by a bad merge resolution. Re-runningtools/gen-config-docs.mjs generateremoves exactly those four stale lines; every key stays documented once with current text. Fixes thedocs-syncgate.fix(ci):drop the orphanedexportonmaskUrlForPublish(src/log-mask.ts:121) - introduced by a4f2730 ([security][web] Diagnostics blob prints private relay hosts verbatim in the config section — the "secrets masked" header only masks values, not hosts | 诊断包 config 段原样输出内网中转地址:标题说"密钥已遮蔽",但只遮值不遮主机 #3811), referenced only bymaskUrlsForPublishin the same file, soscripts/check-unused-exports.mjsfailed withINTERNAL_ONLY src/log-mask.ts: maskUrlForPublish. Same treatment as fix: drop orphaned export on codexRewriteInsertionIndex (Fixes #2314) #2315 did for maskUrlsInText. Fixes theunused-exportsgate.Behavior change: none. Pure gate repair - no runtime code path, config surface, or wire shape is touched. Until this lands, both gates sit in the
needschain of the test/static-gates jobs, so every run since ~14:49Z 2026-10-19 (master and all PR branches) skips its test lanes entirely (#3870).Local evidence (worktree at master):
node scripts/check-unused-exports.mjs->unused-export gate: clean (5 waived)node tools/gen-config-docs.mjs generate && git diff --exit-code -- CONFIGURATION.md CONFIGURATION.zh-CN.md website/main.js website/docs/index.html-> exit 0