Do we have a high-confidence way to reproduce the issue?

Yes. The release-base helper visibly omits toolcall_end between the promoted delta and done, while the declared protocol and current main include that terminal event.

Is this the best way to solve the issue?

Yes. Completing the lifecycle in the existing shared release helper is narrower and safer than backporting current main’s larger stream-normalization refactor.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against fc0fd1bddaa3.

Label changes:

• add P1: The release-branch defect can leave repaired tool calls unfinished for LM Studio, xAI, and Ollama streaming workflows.
• add rating: 🦀 challenger crab: Overall readiness is 🦀 challenger crab; proof is 🌊 off-meta tidepool and patch quality is 🦀 challenger crab.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply because live repository permission reports the author has admin access; focused Testbox and CI results remain useful supplemental evidence.

Label justifications:

• P1: The release-branch defect can leave repaired tool calls unfinished for LM Studio, xAI, and Ollama streaming workflows.
• rating: 🦀 challenger crab: Overall readiness is 🦀 challenger crab; proof is 🌊 off-meta tidepool and patch quality is 🦀 challenger crab.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor proof gate does not apply because live repository permission reports the author has admin access; focused Testbox and CI results remain useful supplemental evidence.

PR surface:

Source +1, Tests +19, Docs +1. Total +21 across 4 files.

What I checked:

• Release-base defect: Before this patch, the release helper emitted toolcall_start and toolcall_delta for a promoted call but proceeded to done without the terminal event. (src/plugin-sdk/provider-stream-shared.ts:112, 726a27e96a39)
• Protocol contract: The assistant stream protocol defines toolcall_end with the content index, completed tool call, and partial assistant message. (packages/llm-core/src/types.ts:404, fc0fd1bddaa3)
• Correct backport shape: The patch adds the required terminal event immediately after the promoted delta and supplies the complete record and partial message, matching the protocol. (src/plugin-sdk/provider-stream-shared.ts:113, 117db716cba5)
• Current-main provenance: Current main centralizes the same start, delta, and end lifecycle in the tool-call-repair package; commit 05ebaf4 introduced the current normalization implementation. (packages/tool-call-repair/src/promote.ts:50, 05ebaf41f6ee)
• Shared provider scope: LM Studio, xAI, and Ollama all consume the shared compatibility wrapper, and this PR adds direct Ollama lifecycle assertions. (extensions/ollama/src/stream.test.ts:374, 117db716cba5)
• Validation status: The cited focused Testbox run was still in progress during review; the exact PR head had 66 passing checks, no failed checks, and remaining pending checks. (117db716cba5)

Likely related people:

• steipete: Authored the current-main bounded stream-normalization implementation and has the strongest recent history across the shared provider-stream surface. (role: feature owner and recent area contributor; confidence: high; commits: 05ebaf41f6ee, 062f88e3e3af; files: packages/tool-call-repair/src/promote.ts, src/plugin-sdk/provider-stream-shared.ts, extensions/lmstudio/src/stream.ts)
• fuller-stack-dev: Introduced the earlier promotion of serialized tool calls through the shared repair package, which is the behavior this release backport completes. (role: introduced related behavior; confidence: medium; commits: 3ea911558c45; files: src/plugin-sdk/provider-stream-shared.ts, packages/tool-call-repair/src/promote.ts)
• vincentkoc: Recently refactored shared provider payload-normalization helpers in the same public provider-stream SDK module. (role: recent adjacent contributor; confidence: medium; commits: 35bafea757fa, 2ba9d6eabef9; files: src/plugin-sdk/provider-stream-shared.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.