Method loadSession

packages/acp-adapter/src/server.ts:357–372

* Handle ACP `session/load`. Mirrors newSession's auth gate * and connection guard, but resumes an existing on-disk session * via the shared setupSessionFromExisting helper instead of * creating a new one. After the AcpSession is wired up, replays the * persisted history

(params: LoadSessionRequest)

   * deliberately skips it (per ACP spec G4 / plan gap-4.3).
   */
  async loadSession(params: LoadSessionRequest): Promise<LoadSessionResponse> {
    const { session, acpSession, configOptions } = await this.setupSessionFromExisting({
      cwd: params.cwd,
      sessionId: params.sessionId,
      mcpServers: params.mcpServers,
      mode: 'load',
    });
    // Synchronously replay history — the response must not settle
    // until every historical `session/update` has been pushed,
    // otherwise the client would race the load completion against
    // its own UI bootstrap. This is the ONE difference vs.
    // `resumeSession`, which intentionally omits this step.
    await acpSession.replayHistory();
    this.scheduleAvailableCommandsUpdate(session.id);
    return { configOptions };
  }

  /**
   * Handle ACP `session/resume`. Per ACP spec, `session/resume` is the