Repository navigation
[PR] docs: document the pi-claude-bridge compression-state limitation (#3429) - #3553
ranxianglei wants to merge 5 commits into
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6199-pr.3553.8450982This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr3553.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复。本条是 #3429 triage 选项 B 的文档 PR;扫描了所有提及 pi-claude-bridge 的在途 PR(#3001 async 压缩功能、#3221 /compact summarizer 路由)——目标不同,与本文档缺口无重叠,无并行同类工作。 审核方式(独立复核,未照抄 issue 结论): 拉取分支 Diff 与落位 ✅
事实断言逐条核对(代码级)✅
CI 状态
八问:
小注:PR 正文用「For #3429」而非 Closes——有意为之,#3429 应留开到桥侧修复(option A)落地;标题已带链接,不影响可追溯性。 判定:可合。 windows 重跑转绿即可直接合;若再红一次,上述证据链仍支持环境噪声,届时你定强合还是再等。option A(桥侧根治)继续等你按跨仓政策明确同意后我再列投递计划。 |
(ai: vllm-qwen/qwen3.8-27b) 重跑结果更新(run 39025590078,attempt 2):
判定不变:可合。 当前红是 #3530 flake 窗口的误红,不是本 PR 的问题。可按上述证据链直接合并;若想要全绿截图,再等一轮重跑也行,但不必因此阻塞。 |
pi-claude-bridge spawns a fresh Claude Code subprocess per pi session start whose own x-claude-code-session-id never carries pi's stable conversation id — so after reopen/resume/fork bili's verbatim session keying maps the new CC id onto an empty conversation (folded history + compression accounting lost, launcher/native compress 404s on the pi id). One root mechanism, not a bili defect: content is never lost or corrupted, only the compression state resets. Documented in the Pi section of CLIENTS.md / CLIENTS.zh-CN.md with the bridge-side fix direction (stable CC id derivation); option B of the #3429 triage.
181ca17 to
6b1e2ce
Compare
(ai: vllm-qwen/qwen3.8-27b) 查重:同 #3530 家族(Windows runner flake,victim 轮转、master 自身也红过),该 issue 已被 owner 于 10-18 关闭(completed);不另立项——期间 #3665 已把对应恢复机制合入 master(见下)。 处置:已把分支 rebase 到当前 master 并 push——新 head 为什么这样修(独立取证,非复述前评论):
结构化八问:
收工判定:分支已与 master 对齐、mergeable,等新 head 的 CI 跑完即可合并;若该 flake 再次触发,#3665 会自动重试吸收,若仍红则是确定性挂起、需要人工介入(届时我会再报)。 |
…help-merge sweep)
…help-merge sweep)
master window commits 293ae65/de5e03659 bumped kernel/package.json to 0.0.165 without regenerating the lockfiles; lock-sync re-resolution then rewrites the stale recorded versions (root 0.0.163, kernel 0.0.164) and fails. Pure recorded-version sync via npm install --package-lock-only; no dependency or semantic change.
|
(ai: sglang-gpu0/qwen3.8-27b) |
For #3429 — option B of the triage conclusion (the limitation is a bridge-side identity gap, not a bili defect; documenting it until the bridge ships a fix).
What
One paragraph in the Pi section of CLIENTS.md (+ zh-CN mirror), placed right after "How routing works" because the limitation is a direct consequence of verbatim session keying:
x-claude-code-session-idrides every model request while pi's stable conversation id never does;compressaddressed to the pi id returns 404 (unknown plugin conversation) — one root mechanism, not two bugs;Why this PR exists on its own
#3429's triage concluded bili needs no code change (a content-affinity fallback on the proxy side was explicitly rejected — mis-attributing sessions across re-minted ids is the most expensive failure class in this project, see MESSAGE-IDENTITY.md). The actionable bili-side remainder was exactly this documentation gap: users of the combination currently discover the behavior as "compression is entirely decorative" with no explanation anywhere in the docs.
No code changes; no tests required. Option A (the actual bridge-side fix) is cross-repo work and awaits owner sign-off per the cross-repo submission policy.
Fixes #3429
(孤儿认领:标题本已指向 #3429,补上关闭关键字 —— 第三批清理)