memmy-agent 第二条消息固定报错 session not found

[Memtensor-AI]

现象

memmy-agent 启动后首次对话正常，但发送第二条消息时会固定报 session not found；新建会话后仍可稳定复现。

复现情况

• 首次对话正常
• 第二条消息必现报错
• 新建会话后仍可复现

备注

OpenClaw 知识库未匹配到解决方案。

[Memtensor-AI]

🤖 AutoDev has picked up this issue and started working on it.

Task ID: 1d452ba963e2f9cb
Working branch: bugfix/autodev-2327-20260902070028337
Target branch: latest dev* branch
Workflow: opsp (analysis → coding → testing → PR)

I will post the PR link here once done. If I need more information, I will ask in the comments.

[Memtensor-AI]

✅ AutoDev task 1d452ba963e2f9cb completed.

Summary: Fixed #2327: memmy-agent second-message "session not found" error.

Root cause: apps/memos-local-plugin/core/pipeline/memory-core.ts::closeSession threw MemosError("session_not_found") when the session was no longer in the orchestrator's in-memory live map. After the first message, the adapter's on_session_end hook calls session.close which evicts the session from the live map. Any subsequent duplicate close (lifecycle race, adapter retry, memmy-agent bridge re-firing) hit the null branch and threw, surfacing to the user on the second message.

Fix: Made closeSession idempotent — unknown session ids are a silent no-op with a debug log, matching the existing semantics of closeEpisode/discardEmptyEpisode. Added 4 regression tests in tests/unit/pipeline/regression-2327-second-message.test.ts. All 176 session + pipeline unit tests pass.

Changed files: core/pipeline/memory-core.ts (fix), core/pipeline/README.md + ALGORITHMS.md (doc update), tests/unit/pipeline/regression-2327-second-message.test.ts (new regression tests).

Base branch: main
Branch: bugfix/autodev-2327-20260902070028337
Commit: 3cb77e5
PR: #2328
Assigned to: @whipser030
Reviewers: @whipser030, @hijzy