Distillation

Date: Sep 16, 2026

• 🔴 (22:50) User/project continuation logic creates synthetic message IDs with const syntheticId = `msg_${state.id || "lore"}_${recall.outputIndex}`;.
• 🔴 (22:50) User/project continuation logic throws new RecallContinuationFailure("recall_execution") when recall execution fails.
• 🔴 (22:50) User/project continuation processing tracks transactionalEvents, heldContinuationEvents, contRecallInputs, contUnresolvedToolIndices, lastContinuationSourceSequenceNumber, continuationRecallBytes, contOtherTool, and contState.
• 🔴 (22:50) User/project continuation stream parsing uses JSON.parse(cd) as Record<string, unknown> and applies an SSE frame limit through maxFrames: maxSSEFrames.
• 🔴 (22:50) User/project continuation events can be marked transactional via held.transactional = true; non-transactional held events are treated separately.
• 🔴 (22:50) User/project code cancels and releases a follow-up reader with cancelAndReleaseReader(follow.reader, signal.reason).
• 🔴 (22:51) User/project continuation logic detects collisions against existing item identities and iterates continuation raw items with for (const [idx, item] of contState.rawItems).
• 🔴 (22:51) User/project continuation logic throws new RecallContinuationFailure("follow_up_failed") when a follow-up fails.
• 🔴 (22:51) User/project continuation execution supports transactional commit and rollback callbacks and invokes the commit path when nextExecuted.commit is present.
• 🔴 (22:51) User/project code uses failure categories including "principal_unexpected" and continuationFailureCategory ?? "unexpected".
• 🔴 (22:51) User/project failure synthesis can emit "response.incomplete" with usage: null.
• 🔴 (22:51) User/project cancellation cleanup calls cancelAndReleaseReader(activeReader, signal.reason) when activeReader exists.
• 🔴 (22:51) User/project configuration declares MAX_FOREGROUND_ERROR_BYTES = 64 * 1024.