Dashboard › opencode-lore › Distillation
d6926f38-f3cd-4fd1-bd61-9ff2a8f7867e["lore_tm_v1_q9opXR8fviyubBlxopHO8yq5k_4twooUtmRWV4Lyfj8","lore_tm_v1_SPZ_cyqMDP5-7hk2r3c_VGK8gTCLpfpLHTlH71RzGx4","lore_tm_v1_ii6BZITvaNAz8ltYShTDsVlw0Z3wKmALr2Bu_PCJonI","lore_tm_v1_rqD5zSw9xG4cjyhtD9Tri6d6gYrv76IZ_Wnv-1K3yzw","lore_tm_v1_UTocymLkHxn5nlk2k6_18dwKH7TkRBlYLJyWu5gxXOo"]
Date: Sep 16, 2026
/home/byk/Code/opencode-lore-responses-accumulation using Vitest v4.1.8 passed completely: 1 test file passed, 255 tests passed, started at 15:18:36, duration 16.20s (transform 4.67s, setup 981ms, import 6.58s, tests 8.43s, environment 0ms).packages/gateway/test/openai-responses-recall-aware-stream.test.ts found 6 lifecycle-helper references: LIFECYCLE_ONLY_EVENTS at line 194, LifecycleOnlyEvent at line 205, sparseCoordinateScenario() at line 209, lifecycleLimitScenario() at line 256, and parameterized uses of LIFECYCLE_ONLY_EVENTS at lines 1069 and 7334.packages/gateway/test/openai-responses-recall-aware-stream.test.ts:194-203 defines 8 LIFECYCLE_ONLY_EVENTS, ordered: 1. response.reasoning_summary_text.delta, 2. response.reasoning_summary_text.done, 3. response.reasoning_summary_part.added, 4. response.reasoning_summary_part.done, 5. response.reasoning_text.delta, 6. response.reasoning_text.done, 7. response.content_part.added, 8. response.content_part.done; LifecycleOnlyEvent is derived from this tuple at line 205.SparseCoordinateKind is "output" | "content" | "summary". sparseCoordinateScenario(kind, coordinate, suffix, value = "private sparse coordinate value") creates item ID item_sparse_coordinate_${kind}_${suffix}: output scenarios emit response.output_item.added directly at the supplied output_index with a message containing one output_text; content and summary scenarios first add an item at output index 0, then trigger response.output_text.delta with content_index: coordinate or response.reasoning_summary_text.delta with summary_index: coordinate.lifecycleLimitScenario(event, suffix) uses item ID item_lifecycle_${suffix}, private marker private-lifecycle-${event}-${suffix}, and partIndex = 2. It creates reasoning items with summary: [] for event names containing "reasoning" and assistant message items otherwise; .done scenarios prepend the corresponding .delta or .added event, while trigger payloads embed private markers to verify they do not leak.lifecycleLimitScenario() maps reasoning-summary events to field summary and expected part { type: "summary_text", text: "summary value" }; reasoning-text events map to field content and { type: "reasoning_text", text: "reasoning value" }; content-part events map to field content and { type: "output_text", text: "content value" }.textItem(outputIndex, text, itemId = \msg_${outputIndex}`)builds a complete four-event text lifecycle in order: 1.response.output_item.added, 2. response.output_text.delta, 3. response.output_text.done, 4. response.output_item.done; the terminal item has status: "completed"and content[{ type: "output_text", text }]`.