fix(eve): pass the settled history to turn.completed so memory capture runs

[gugu91]

Summary

Fixes #3223 (p0). Since 0.51.0 no memory provider's capture["turn.completed"] has run. This restores the one argument that was lost and adds a regression test.

The problem

turn.completed skips memory capture because it arrives without the turn's messages. handleEvent(event, messages) in execution/workflow-steps.ts forwards both arguments to dispatchMemoryLifecycleEvent, which only captures when messages are present:

} else if (input.event.type === "turn.completed" && input.messages !== undefined) {
  try { await dispatchMemoryTurnCompleted({ ... }); } catch (error) { log.error(...); }
}

#2690 (aae26311, "graduate background subagents to workflow tools") removed the messages parameter from emitTurnEpilogue in harness/emission.ts and the session.history arguments at its call sites in tool-loop.ts. Since then messages is always undefined, the guard returns before the try, and nothing is logged. Recall kept working because turn.started has no such guard, and compaction-time capture kept working because compaction.requested still passes messages, so the regression stayed hidden.

How we hit it

We integrated @supermemory/eve on 0.52.4 and the agent could only recall facts it had saved with the remember tool. A recorder provider in our fixture stack logged every turn.started and no turn.completed across many turns, and the live Supermemory container held only source_type: "memory" documents, none of type "conversation". Reading the shipped dist led to the guard above and then to #2690. #3223 already reports the same diagnosis with reproductions on 0.51.0, 0.52.x, 0.54.3 and 0.55.0. The maintainer-bot draft #3224 has only the failing test and has been idle since 2026-09-10, so this PR carries that test forward with the fix.

Why this fixes it

emitTurnEpilogue takes an optional messages again and passes it as the second argument of the emit, as it did before #2690. The four places that settle a turn pass session.history:

• finishConversationTurn and finishTaskTurn, plain path
• finishConversationTurn and finishTaskTurn, structured path, through emitStructuredResult, which gains the same parameter

Each site reads the history after persistStructuredAssistantTurn and clearTurnClientContextState, so the provider receives the settled history including the assistant response. The five other callers of emitTurnEpilogue end a turn without a model response (session limits, input requests, authorization parking, proxied subagent input and authorization events). They keep omitting messages on purpose, so a turn with no answer captures nothing. The public event stream does not change: messages is the side-channel argument of HarnessEmitFn, not part of the event.

Testing

Unit, this repo

• New test in harness/tool-loop.test.ts: a conversation turn through createToolLoopHarness with a mock model, asserting the turn.completed emit receives the same array as result.session.history. On main it fails with expected undefined to deeply equal [ { content: 'Hi', … }, … ]; with the fix it passes.
• pnpm test:unit: 8756 passed, 1 skipped, 4 failed. The 4 failures (execution/session-callback-request.test.ts ×3, self-modification/registry-add.test.ts ×1) fail the same way on a clean main checkout in this environment and do not touch memory or the harness.
• pnpm test:integration: 871 passed across 112 files.
• pnpm lint: 0 errors, only pre-existing warnings in apps/templates. pnpm typecheck: 47/47 tasks. oxfmt --check clean on the touched files.

Live, our app against Supermemory with a real model

• Before: after about 10 turns the member's container held 2 documents, both source_type: "memory" from the remember tool, and none of type "conversation".
• After: one chat with a passing remark (my dog is called kestrel-…) and no tool calls in the stream. About 20 seconds later the container had a new source_type: "conversation" document with status: "done". A new chat asking "what's my dog called?" answered kestrel-… with no tool calls, so the provider's turn-start search found the captured turn.

Checklist

• This change was requested or approved by a maintainer. It was not: Memory capture silently stops running after upgrading to 0.51.0 #3223 is p0 and draft fix(eve): restore memory capture after completed turns #3224 has stalled, so I am offering the fix. Happy to close it if you would rather land your own.
• I ran the relevant checks from CONTRIBUTING.md
• I added tests and documentation where relevant
• I added a changeset if this touches the published eve package
• DCO sign-off passes for every commit (git commit --signoff)

[vercel]

@gugu91 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.