/api/v1/responses streaming (SSE) omits required output_index/content_index fields, breaking OpenAI-Responses-compatible clients #3607

Platform

Linux/Ubuntu

Lemonade Version

11.9.0

GPU / APU Model

Radeon AI PRO R9700

Component

llama.cpp

Bug Description

Summary

When calling POST /api/v1/responses with "stream": true, the returned SSE events do not include the output_index field (on response.output_item.* and response.reasoning_text.* events) or the content_index field (on response.content_part.* / response.output_text.* events) that the OpenAI Responses API specifies. Clients that rely on these indices to place streamed deltas into the correct output item/content part (instead of relying purely on event ordering) cannot unambiguously associate deltas with items, and reject the stream as containing "overlapping" or "unindexed" output items.

Non-streaming /api/v1/responses ("stream": false) is unaffected — the final response payload is well-formed.

Environment

• Lemonade server, OpenAI Responses-compatible endpoint: http://<host>:<port>/api/v1/responses
• Model: Qwen3.8-27B-GGUF (llama.cpp-backed GGUF model)
• Client: OpenClaw, api: "openai-responses" provider adapter

Steps to Reproduce

curl -sN -X POST http://:/api/v1/responses
-H "Authorization: Bearer ***"
-H 'Content-Type: application/json'
-d '{
"model": "Qwen3.8-27B-GGUF",
"input": "Reply with exactly the word: ok",
"stream": true,
"max_output_tokens": 64
}'

Expected vs Actual Behavior

No response

Log Output

Additional Context

No response