Distillation

Date: Sep 16, 2026

• 🟡 (14:17) In packages/gateway/src/pipeline.ts:11636-11673, principal transport failures are retried only when the error is an SSEStreamTransportError, principal reading has not finished, continuation has not been attempted, error.kind === "read", no principal or ordinary-tool event has been emitted, the signal is not aborted, opts.retryPrincipal exists, and principalTransportRetries < maxPrincipalTransportRetries; failures are reported with outcomes "retry", "continue", "retry_exhausted", or "failed".
• 🟡 (14:17) Assistant defined a fail-first matrix covering three reviewed security/correctness issues: 1. raw non-JSON diagnostics carrying private recall data on both producer paths, 2. malformed continuation terminal timestamps in object/array/string/negative/null/non-finite forms, and 3. a high-cardinality real stream that counts numeric projection sorts rather than timing execution.
• 🟡 (14:18) Candidate ozrmvotwxzuykyvutstpwpzukpptktxv at head 583020fad43e1481470aac2588251b8636d16251, based on main@origin commit 2cbf40060c67df229731cf1b9e34d5bf22ec2145 through ab979df5cddfec3952680e423e39564664e881fe, passed integrity validation. Clean child working copy: 9285e4185a10a4e4734964fed7e342ada4fda044; unrelated conflicted bookmark: fix/responses-private-references.
• 🟡 (14:18) Candidate changed exactly 2 files—packages/gateway/src/pipeline.ts and packages/gateway/test/openai-responses-recall-aware-stream.test.ts—with 654 insertions and 62 deletions. Plain diff SHA-256 remained 83d7c15b3b0c7dd4b58df93af5f20b0e18de6ad99e939d02aa75c0d5e7dea30d; packages/gateway/dist/index.cjs SHA-256 remained 37e33a5aeb66b81d1c8b307ed9f511aa20b56d095f8e31cf8f037eb993bd20a5.
• 🟡 (14:18) Full candidate gate command CI=1 NO_COLOR=1 SENTRY_AUTH_TOKEN= SENTRY_ENABLED=0 pnpm test -- --printConsoleTrace exited 0 after 1416s: 469 test files passed, 17 skipped, 0 failed (486 total); 10,303 tests passed, 230 skipped, 0 failed (10,533 total). Vitest duration was 1406.11s with transform 32.37s, setup 64.15s, import 970.11s, tests 2979.19s, and environment 120ms; aggregate success made the four shards unnecessary.
• 🟡 (14:18) Full-gate isolation checks found the production database was never accessed, /tmp/lore-test-* paths remaining were 0, workspace test workers before and after were both 0, all 10 publish-listed bundle artifacts existed, and the candidate stack/filesystem remained clean.
• 🟡 (14:18) Assistant determined that although candidate 583020fa retained valid full-gate evidence with 10,303 passing tests and unchanged patch/bundle hashes, the new security findings still blocked merge; implementation edits were deferred until all 9 newly added tests failed against unchanged production code for the expected three reasons.
• 🟡 (14:18) Initial fail-first test invocation produced ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL because command "vitest" was not found; assistant classified this as missing workspace dependency links, not test evidence.
• 🟡 (14:19) Existing frozen pnpm lockfile was materialized offline without source or lockfile changes: 977 packages added using pnpm v10.28.0. Gateway postinstall ran pnpm --filter @loreai/gateway run build, invoking tsx script/build.ts and creating development shims for index.bun.js, embedding-worker.js, and vector-worker.js.
• 🔴 (14:20) User established the security invariant: “never exposes non-semantic principal frames after recall interception”; the fail-first test for this invariant failed in 72ms.
• 🔴 (14:20) User established the security invariant: “never exposes non-semantic continuation frames after recall interception”; the fail-first test for this invariant failed in 7ms.
• 🟡 (14:20) Fail-first Vitest run for packages/gateway/test/openai-responses-recall-aware-stream.test.ts executed 222 tests in 194ms: exactly 9 failed and 213 were skipped.
• 🟡 (14:20) Both non-semantic-frame tests failed because client-visible output still contained event: diagnostic after recall interception, demonstrating leakage on both the principal and continuation producer paths. The emitted stream also contained public recall marker and safe-answer events, including <!-- lore-recall:private-recall-query -->.
• 🟡 (14:20) Six malformed continuation created_at validation tests failed for exact forms: 1. object, 2. array, 3. string, 4. negative, 5. null, and 6. non-finite. Instead of emitting PUBLIC_RECALL_ERROR ("Lore could not continue the response …") and suppressing response.completed, the implementation rebuilt and exposed a successful terminal response.
• 🟡 (14:20) The non-finite created_at case was serialized into a terminal response.completed with "created_at":null, exposing the safe answer and terminal response rather than rejecting before terminal reconstruction.
• 🟡 (14:20) The high-cardinality regression test "updates the principal projection without sorting once per indexed event" failed in 57ms, showing that principal projection still performs numeric sorting once per indexed event rather than maintaining the projection incrementally.