Distillation

Date: Sep 16, 2026

• 🔴 (15:55) User stated that recall-only streaming “never converts a failed continuation into completed,” reflected by the test at /home/byk/Code/opencode-lore-provider-error/packages/gateway/test/openai-responses-recall-aware-stream.test.ts:8864.
• 🔴 (15:55) User stated that recall-continuation diagnostics “never alter the fixed public failure,” reflected by the test at /home/byk/Code/opencode-lore-provider-error/packages/gateway/test/openai-responses-recall-aware-stream.test.ts:9172; the test also requires private result content to remain absent from client output.
• 🔴 (15:55) User stated that the recall-aware stream “never executes recall from an incomplete principal,” reflected by the test at /home/byk/Code/opencode-lore-provider-error/packages/gateway/test/openai-responses-recall-aware-stream.test.ts:9320.
• 🔴 (15:55) User stated that the recall-aware stream “never executes a chained recall from an incomplete continuation,” reflected by the test at /home/byk/Code/opencode-lore-provider-error/packages/gateway/test/openai-responses-recall-aware-stream.test.ts:9346.
• 🟡 (15:55) The shown recall-aware stream regressions require failed/incomplete recall paths to emit no response.completed event and keep private recall query/result text out of serialized completion state and client output.