fix: `log_working_memory_replacement` reports incorrect memory_len (delta instead of total)

[nuthalapativarun]

Problem

In src/memos/mem_scheduler/general_modules/scheduler_logger.py, log_working_memory_replacement has a # TODO: Log output count is incorrect comment at line 167.

The method passes memory_len=len(memcube_content) to create_event_log, where memcube_content only contains the newly added memories (delta). This means the scheduler UI shows the count of changes, not the actual size of the output working memory.

Example:

• Original working memory: [A, B, C] (3 items)
• New working memory: [A, B, D] (3 items)
• memcube_content = [D] → memory_len = 1
• Correct value: memory_len = 3 (total memories in output)

Expected Behavior

memory_len should reflect the total number of memories in the working memory after replacement (len(new_memory)), consistent with how other log entries represent the output size.

Steps to Reproduce

Trigger a working memory replacement operation via the scheduler and observe the memory_len field in the scheduler log output.

Proposed Fix

Change line 227:

# Before
memory_len=len(memcube_content),
# After
memory_len=len(new_memory),

Files

• src/memos/mem_scheduler/general_modules/scheduler_logger.py line 167, 227

[MaiHHConnect]

💬 我也在做记忆系统相关的工作：CausaMem，可以来看看，说不定有能借鉴的地方 🙂

[MaiHHConnect]

💬 我也在做记忆系统相关的工作：CausaMem，可以来看看，说不定有能借鉴的地方 🙂

[Memtensor-AI]

⏸️ AutoDev task a1ebc4ccf6299d5d needs manual clarification.

Reason: 已修复 #1790：log_working_memory_replacement 现在用 len(new_memory) 上报输出工作记忆总大小，移除了 # TODO 注释，并在 tests/mem_scheduler/test_scheduler.py 新增回归测试。Commit ca61c9a 已推送到分支 autodev/MemOS-1790。是否创建 PR？