Repository navigation
fix: pin acp-kernel 0.0.89 — Claude-lane hotfix (top-level anyOf removed from compress schema) - #1302
Conversation
…hema (Anthropic 400, #1299)
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-1302Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr1302.tgz
npm install -g packageInstall instructions are refreshed on each push. |
PR 已核验完毕(人工已于 05:37Z 合并,merge commit Diff 与回归面
行为变更披露(旧→新)
Gates(本地在合并头复跑)
关联观察:#1301(#1299 会话提的并行热修 PR)在本 PR 之后 3 分钟也被合并( 下一步:npm latest 仍是 0.1.148,Claude 用户仍在 400——我正按 §5 流程切 一句话总结:pin 0.0.89 热修已核实无误(kernel diff 仅含 schema 修复、pin 门测试双向复现有效、本地全套 gates 绿),合并无问题;正在提 0.1.149 发布 PR。 |
发布闭环完成,热修已上线:
一句话总结:0.1.149 热修发布全链路闭环(one-click 工作流 PR #1303 已合并、npm 已发布、官方产物复审无顶层组合子),Claude lane 事故解除。 |
…enai SSE lane Review of #1305 (mutation-verified) found the consolidation dropped the old #1302 assertion for the OpenAI chat and Responses tool shapes: top-level combinators were only checked on anthropic (WC-001) and google (WC-006), so an anyOf on COMPRESS_TOOL_OPENAI.parameters passed every rule test and only the golden byte-diffs caught it. Restores the ban as part of WC-004/WC-005 with provenance; re-running the mutation now fails 6 rule tests (was 0). Also: stream:true on the openai-chat smoke lane (activates the fake's SSE branch and exercises the real src/stream-openai.ts parse path — previously dead code), sse() no longer emits an empty event: line for OpenAI chunks, and AGENTS.md now points WIRE_RULES at tests/wire-contract-fakes.ts (where it is defined).
…nified ledger (ranxianglei#1304) Consolidates the ranxianglei#1301 served-surface gate and the ranxianglei#1302 kernel-export gate into one wire-contract suite and extends it per owner decision on ranxianglei#1304 (items 1+2+3, plus the 4-protocol scripted-client matrix phase): - tests/wire-contract-fakes.ts: WIRE_RULES ledger (WC-001..WC-006, each with production/doc provenance) + strictest-known validation for all four wires (anthropic /v1/messages, openai chat, responses, google v1beta) + four validation-parity fake upstreams on listen(0) with canned per-wire replies. - tests/wire-contract.test.ts: four layers — ledger self-check (every rule id has a live enforcement clause), A kernel exports, B bili-built surfaces, C plugin manifest (default + opt-in), D live proxy-mode forward of one client-shaped turn per protocol through the matching fake (asserts the forwarded tool set is exactly bili's intended surface and the fake's strictest validation accepts it). The anthropic lane reproduces ranxianglei#1299 end-to-end. Supersedes tests/kernel-pin-wire-schema.test.ts and tests/issue1299-anthropic-top-level.test.ts (all their assertions kept). - tests/wire-contract-golden.test.ts + tests/golden/wire-contract/*.json: byte-equal golden snapshots of every advertised tool schema at both layers (kernel exports, bili surfaces, plugin manifest default+opt-in); manifest version normalized to <VERSION> so release commits don't churn it. - scripts/update-wire-contract-goldens.ts: explicit regeneration path. - AGENTS.md §7.3: institutional rule — every upstream rejection/validation constraint becomes a permanent wire-contract rule inside the fixing PR; the ledger only grows.
Fixes #1299 (user-facing outage) · kernel side: acp-kernel #404 + #405 (merged), released as 0.0.89.
What happened
Kernel 0.0.87–0.0.88 gave
COMPRESS_PARAMETERSa top-levelanyOf(the #374 schema relaxation). Anthropic hard-rejects toolinput_schemawith top-leveloneOf/allOf/anyOf→ 0.1.148 (pin 0.0.88) 400s every request carrying the injected compress tool on the Claude lane (tools.91.custom.input_schema), and the auto-updater pushed it fleet-wide. 0.1.147 (0.0.86) unaffected.This PR
{type, properties}, content-vs-flat alternation stays in descriptions + parser).tests/kernel-pin-wire-schema.test.ts— the pin gate: imports the pinned kernel and walks every tool × every wire shape (anthropic / openai / responses / google, absorb / image_full / acp_retrieve included, plus the manifest path) asserting no top-level combinators. Verified it trips on 0.0.88 (red) and passes on 0.0.89 (green) — a future pin bump to a wire-illegal kernel now fails CI at the pin PR instead of production.Gates
After merge
Needs hotfix release 0.1.149 — Claude proxy users are still 400-ing on 0.1.148. Also note: #1298 (fingerprint/refold) depends on kernel APIs not yet released (#398/#400) — its CI will stay red against this pin until the kernel ships them; that PR is blocked upstream by design.