@leanandmean/coding-agent 0.74.1-scramjet.19 → 0.74.1-scramjet.21

package/dist/core/agent-session.d.ts

@@ -165,6 +165,8 @@ export declare class AgentSession {
     private _unsubscribeAgent?;
     private _eventListeners;
     private _agentEventQueue;
+    private _disposed;
+    private readonly _harnessPersistenceAcks;
     /** Tracks pending steering messages for UI display. Removed when delivered. */
     private _steeringMessages;
     /** Tracks pending follow-up messages for UI display. Removed when delivered. */
@@ -227,6 +229,8 @@ export declare class AgentSession {
     private _handleAgentEvent;
     private _createRetryPromiseForAgentEnd;
     private _findLastAssistantInMessages;
+    private _processAgentEventTracked;
+    private _harnessAckIdForEvent;
     private _processAgentEvent;
     /** Resolve the pending retry promise */
     private _resolveRetry;
@@ -298,8 +302,26 @@ export declare class AgentSession {
      * run/turn framing. The idle-vs-mid-run branch lives in `runHarnessTool` (keyed on the agent's
      * active run, which tracks `isStreaming`): idle calls execute immediately, mid-run calls queue
      * and drain before the next intra-run LLM call.
+     *
+     * **Persisted settlement (#341).** This is a strictly stronger boundary than
+     * {@link Agent.runHarnessTool}: the returned promise resolves only after (1) the Agent-core
+     * pipeline fulfills *and* (2) `_processAgentEvent` has persisted the matching tool-result
+     * `message_end` via `SessionManager.appendMessage`. Because the event queue preserves order,
+     * that also proves the preceding synthetic assistant tool-call message was persisted first. It
+     * rejects on Agent-core failure, on failure to process/persist a matching event, on disposal
+     * before settlement, on a post-disposal call, on an unknown tool, or on a duplicate explicit
+     * tool-call id that is already pending. **Rejection means the promised pipeline did not complete —
+     * it does not prove artifact absence** (Agent state and persistence may have partially or fully
+     * completed before a late failure), so callers must not blindly retry. A tool's own `execute()`
+     * error is *not* a rejection: it becomes a normal `isError: true` result and the promise resolves
+     * after that error-result pipeline is persisted.
+     *
+     * **Reentrancy.** As with `runHarnessTool`, do not `await` this from work whose return is required
+     * for the Agent to reach the drain point or for the event queue to persist the matching result.
      */
     invokeHarnessTool(name: string, args: unknown, options?: InvokeHarnessToolOptions): Promise<void>;
+    private _allocateHarnessToolCallId;
+    private _registerHarnessPersistenceAck;
     /** Whether compaction or branch summarization is currently running */
     get isCompacting(): boolean;
     /** All messages including custom types like BashExecutionMessage */