chore: bump acp-kernel to 0.0.34 - #191
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps acp-kernel 0.0.32 → 0.0.34 (two releases: 0.0.33 responses item.id fix + 0.0.34 inline
<think>normalization).What the proxy gains
openaiToCorenow splits<think>\n…\n</think>/<thinking>…</thinking>/ ```thinking fences at offset 0 of assistant content into a separatereasoningcore message when no `reasoning_content` field is present. Providers that demote thinking inline (glm / qwen3 / deepseek / kimi via openai-completions) previously folded those turns as one opaque text blob:reasoning_contentform, so omp restart replay (issue release v0.1.25 #64 demoted variant) survives without any mirror retry — omp PR feat(mitm): auto-discover model domains from client configs (no hardcoding) #125 drops its omp-side retry accordingly.Protocol/serialization decisions keep consolidating in the kernel; the proxy stays a thin mitm + adapter shell (this PR is dependency-only).
Tests
npm test512/512 passnpm run typecheckclean