Refactor history messages merging logic

[huangdijia]

Simplified the logic for merging system and regular messages in ToolUseAgent and MemoryManager by using unified methods. This improves code readability and reduces redundancy.

#11

[Copilot]

Pull Request Overview

This PR refactors the merging of system and regular messages by centralizing the logic into a single method.

• Simplify merging in MemoryManager::getProcessedMessages() using array_merge
• Update ToolUseAgent::call() to use the new getProcessedMessages() method

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Memory/MemoryManager.php	Replaced conditional merge of last system message with direct array_merge
src/Agent/Tool/ToolUseAgent.php	Swapped manual merge of messages for a call to getProcessedMessages()

Comments suppressed due to low confidence (2)

src/Memory/MemoryManager.php:113

• [nitpick] Consider adding unit tests for getProcessedMessages to verify correct behavior when there are no system messages, a single system message, and multiple system messages to catch any unintended regressions.

$allMessages = array_merge($this->getSystemMessages(), $this->getMessages());

src/Memory/MemoryManager.php:113

• This replaces the previous behavior of merging only the last system message; now all system messages are included. Confirm whether you intended to include the full history or keep only the most recent system message, and adjust the logic if needed.

$allMessages = array_merge($this->getSystemMessages(), $this->getMessages());