ACP integration: Session history is not replayed or available to clients (e.g., Zed, JetBrains, ...)

Problem

When using kimi-cli as an ACP agent (e.g. with Zed or JetBrains IDEs), loading or switching a session does not replay or provide past conversation history to the client. This means all ACP-based integrations always start at a blank context, even if older session history exists.

• The ACP spec expects that, when loading a session, the complete conversation history is provided to the client via notifications. This matches typical user expectations in IDEs (history/chat review buttons, navigation, etc.).
• In the Web UI and CLI, history replay is already implemented and works as expected, using context.jsonl and wire.jsonl files for persistence.
• With ACP, history seems to be totally absent; e.g., in Zed, every session starts with 0 messages. This makes context continuity and long-running chat impossible.
• There is a closed issue ([#824](https://github.com/MoonshotAI/kimi-cli/issues/

What does it mean for Zed Users?

When inspecting History, nothing shows up

And after user clicks History -> View All

However, when using /session in the Kimi CLI directly, it correctly shows the Sessions History

Start at the ACP load_session implementation and compare it with the existing Web UI and CLI replay paths using context.jsonl and wire.jsonl. Check the ACP specification's load_session expectations and reproduce the missing history through a client such as Zed. Done means an existing session's complete conversation is available after loading or switching.