[xandreeddev]

What

• A run's memory maintenance can no longer cost its reply. It now runs after the turn's completed or partial reply is recorded, drained and sealed (TurnMemory.afterReply, TurnWriter.seal), still inside the turn, billed by its call recorder and triggered on the run's reported input. An ordinary maintenance failure is logged and skipped (writer, fence and close failures stay hard). A cancel, a time limit or a shutdown during it stops the maintenance only, and the turn ends completed with its reply.
• A process death during that work leaves the turn sealed in the session's head state (stored format 17, HeldTurn.sealed: the ending and the reply's closing drafts). A reap or takeover ends it completed and stores that reply with its text, and the turn is not resumable, so the model is not asked again. Only what the holder held after the seal (the summary it was writing) is lost; the next run's start maintains it. A begin that is refused while such a turn's holder is gone (a resume of it, which is finished) reaps it in a commit of its own, so the inbox drainer never retries resuming a sealed turn and moves on to queued work.
• Each run's start (turn-start) is still the safety net. It is now calibrated by the last stored selected response (TurnMemory.acceptedBefore: the last step.usage with its step's context.built), so calibration carries across runs and reopened sessions.
• The summary strategy keeps summarizeAt: "turn-end" as its default. Manual stepRequestOf → StepLoop.run compositions get the same lifecycle with nothing to call after the loop, so the unreleased prepareRun is removed.
• turnBilledUsageOf and telemetry bill each loop step's selected usage when no Loop call names that step. Before, any recorded call hid every selected response. The call recorder reads only its own turn's rows, and a step's ceiling is lowered to a catalogued model window less its output cap.
• Migration: custom TurnMemory implementations add deferAfterReply, afterReply and acceptedBefore. TurnWriter.seal is optional, and a writer that has it reruns sessionsConformance (new sealed check, with a careless self-test). The changelog names the event kinds reserved since 0.14.0 (memory.tool-presentation, tool.intercepted, inbox.taken, model.called, request.part, memory.snapshot): 0.14.0 let a host event take those names.

Checks

• bun run typecheck: pass
• bun packages/foundry/src/main.ts check --config packages/foundry/foundry.config.ts: pass
• bun test: 3806 pass, 0 fail
• bun run foundry demo, build:packages, verify:packages, docs:generate (no diff), bun run --cwd packages/website check, the models plugin proxy tests (on Bun 1.3.0, not 1.3.6): pass