Distillation

Date: Sep 16, 2026

• 🔴 (16:18) Repository search found 58 matches across gateway tests. Relevant OpenAI Responses coverage in packages/gateway/test/openai-responses-recall-aware-stream.test.ts includes created metadata, provider failures, response-identity changes, ordinary-tool continuation without replaying side effects, terminal identity/output validation, ciphertext chains, mid-delivery abort/follow-up behavior, reference identity, and valid incomplete recall/principal responses.
• 🔴 (16:19) In packages/gateway/test/openai-responses-recall-aware-stream.test.ts:2070-2090, aborting with new DOMException("foreground expired", "TimeoutError") during retryPrincipal() must make client.text() reject with name: "TimeoutError" and cancel the retry response body (retryBodyCancelled === true).
• 🔴 (16:19) In packages/gateway/test/openai-responses-recall-aware-stream.test.ts:2093-2119, a principal Response(null) is classified as unexpected: output contains exactly one response.failed event and PUBLIC_GATEWAY_ERROR, excludes PUBLIC_RECALL_ERROR and "Upstream response has no body", emits no RecallContinuationFailureCategory, and logs exactly "openai-responses recall-aware stream failed category=principal_unexpected".
• 🔴 (16:19) In packages/gateway/test/openai-responses-recall-aware-stream.test.ts:2122-2140, a stream created as response ID "resp_identity_a" but changed by response.in_progress to "resp_identity_b" must produce response.failed.
• 🔴 (16:19) In packages/gateway/test/openai-responses-recall-aware-stream.test.ts:2142-2169, malformed named continuation event event: response.completed\ndata: {not-json}\n\n must yield PUBLIC_RECALL_ERROR, must not expose {not-json}, and must report exactly ["follow_up_protocol"].
• 🔴 (16:19) packages/gateway/test/openai-responses-recall-aware-stream.test.ts:2171-2197 begins a regression for retrying a dropped recall continuation before exposing output: the first follow-up emits created ID "resp_dropped_followup" and message ID "msg_retry_identity" before a "socket reset"; recovery uses response ID "resp_recovered_followup", the same message ID, text "recovered answer", and a completed terminal event.
• 🔴 (16:21) Search for throwing log/telemetry sinks found two targeted tests: packages/core/test/temporal-prune-race.test.ts:14, whose comment notes withDbSpan wraps every executed statement so a sink can throw, and packages/gateway/test/sentry-principal-transport-failure.test.ts:91, test "contains hostile telemetry objects with throwing getters".
• 🔴 (16:25) packages/core/src/log.ts hardens persistent logs with LOG_MAX_BYTES = 5 * 1024 * 1024, ROTATION_CHECK_INTERVAL = 1000, directory mode 0o700, file mode 0o600, and O_NOFOLLOW except on Windows. It verifies current ownership and stable device/inode identity, rejects symlinks and non-regular files/directories, uses O_NONBLOCK to avoid blocking on a raced-in FIFO, tightens permissions with fchmodSync(), and validates the data directory again after opening the log.
• 🔴 (16:25) resolveLogPath() in packages/core/src/log.ts:376-395 returns undefined under NODE_ENV === "test" or on setup failure; otherwise it creates and validates dataDir(), resolves lore.log, and immediately tightens both lore.log and lore.log.1 so a legacy 0644 backup cannot remain readable. logFilePath() memoizes this resolution.
• 🔴 (16:25) Log rotation in packages/core/src/log.ts opens and tightens the active file before checking its size, rotates only when stat.size > LOG_MAX_BYTES, and safely validates/removes the existing ${logPath}.1 backup before replacement.
• 🔴 (16:27) Focused Vitest v4.1.8 run in /home/byk/Code/opencode-lore-provider-error passed: 1 test file passed; 26 tests passed and 217 skipped out of 243; started at 16:25:31; duration 7.17s with transform 3.89s, setup 722ms, import 6.03s, tests 197ms, and environment 0ms.
• 🔴 (16:28) Attempt to repeat the Vitest run with --repeat failed before tests ran because Vitest v4.1.8 does not recognize that option: CACError: Unknown option \--repeat`. Runtime was Node.js v24.16.0`.