Distillation

Date: Sep 16, 2026

• 🟡 (14:44) Validation after restoring the projection-work guard succeeded: @loreai/gateway@0.40.0 typecheck completed with tsc --noEmit, and all 9 selected tests passed with 213 skipped out of 222 in packages/gateway/test/openai-responses-recall-aware-stream.test.ts; duration was 5.70s.
• 🟡 (14:44) Assistant identified that the first sort-count implementation still shifted a full map for every newly visible item and proposed a bounded incremental projection ledger: append-only fast path for normal monotonic streams, binary lookup for repeated sparse items, fail-closed behavior when a late lower visible item would retroactively change an emitted coordinate, and rare hidden-recall removal under the one-recall invariant.
• 🟡 (14:45) packages/gateway/src/pipeline.ts was updated to implement the bounded incremental projection-ledger approach.
• 🟡 (14:46) Typecheck still completed cleanly after the bounded-ledger change, but focused testing produced 1 failure, 12 passes, and 209 skipped out of 222; duration was 5.99s.
• 🟡 (14:46) The failing test was fails closed when a lower-index recall follows visible output at packages/gateway/test/openai-responses-recall-aware-stream.test.ts:5882-5919. Its stream places visible textItem(1, "already visible", "msg_dense_visible") before lower-index recallCall(0, { query: "private query" }, "fc_dense_late_recall"); expected behavior includes the public PUBLIC_GATEWAY_ERROR, no private query/result, zero recall executions, exactly one response.failed, no response.completed, and failed terminal output [].
• 🟡 (14:46) The lower-index-recall test failed specifically at line 5906 because output did not contain PUBLIC_GATEWAY_ERROR (Gateway request failed). Instead, it retained the already-emitted visible message and emitted one sanitized response.failed whose error message was Lore could not continue the response after recall; logs classified the failure as follow_up_setup at packages/gateway/src/pipeline.ts:11572, 11712, and 11841.
• 🟡 (14:46) The failure output did not expose private query or private result, but its failed response still contained the completed visible item msg_dense_visible in response.output, conflicting with the test’s expected output: [].
• 🟡 (14:46) packages/gateway/src/pipeline.ts was updated again after inspecting the failing lower-index-recall test; no subsequent validation result was shown.