Repository navigation
test: record Copilot Gemini schema constraints - #1415
ranxianglei merged 2 commits into
Conversation
[bot] 🏷 Review: mergeable. Test-only, additive, green everywhere. Details below. ① Direction (original issue)Correct half of a two-part fix, correctly scoped. #1414 explicitly assigns to Bili "a wire-contract regression to record this provider constraint"; the schema producer lives in acp-kernel ( ② Regression inventory (existing behaviors touched)
③ CodeThe encoding matches the real producer bug exactly. Inspected the pinned kernel 0.0.93 ④ Test teeth
⑤ Diff & verification3 files, +51/-0, every line on-purpose; no whitespace/lockfile/unrelated churn. Local: targeted One forward-looking note (non-blocking, for the follow-up pin-bump PR): Layers A/B synthetic bodies carry no 中文摘要:审核了「记录 Copilot Gemini schema 约束」的纯测试 PR(账本 WC-008 + 假上游校验 + 回归测试),方向与 #1414 分工一致、对既有校验零行为漂移、编码与当前内核 0.0.93 的真实缺陷逐条吻合,本地 18/18 + typecheck + CI 12/12 全绿,可以合并。 |
|
#1417 批次深审 + 修复交付 判定:✅ 可合(修后)干什么/动机:wire-contract 账本新增 WC-008——GitHub Copilot 的 Gemini 端点要求 schema 四轴:压缩行为/推荐列表/cache 命中/压缩质量全部零触碰。 审查发现与修复(新 head
|
[bot] 🏷 Fixed-head verified — correct and green locally — but PR #1415's head ref does not contain the fix; do not merge as-is. What I verified (lineage
|
Record the Copilot Gemini compress-schema rejection in the wire-contract ledger and fake upstream validator. Synthetic regression tests independently reject array-valued types and untyped alternatives, accept explicit typed alternatives, and preserve validation for other model families.
This is the Bili regression half of the fix. The schema producer is acp-kernel; its source correction must be released before a follow-up updates Bili's exact dependency pin. This PR alone does not change the installed kernel or fix production requests.
Validation: Bili typecheck, targeted Copilot and wire-contract tests, and build pass. No production configuration, prompts, or diagnostic logs are included.
Tracks #1414 (kept open until the fixed kernel is released and consumed). Kernel issue: ranxianglei/acp-kernel#447.