fix: align agentId resolution to prevent scope mismatch (#231)

[AliceLJY]

Summary

• Root cause: memory_update, memory_forget, memory_stats, and memory_list used resolveRuntimeAgentId(runtimeContext.agentId, runtimeCtx) in their execute functions, which re-resolves agentId from the execute-time runtimeCtx. When the execute-time context provides a different agentId than the definition-time runtimeContext.agentId, this causes "Memory is outside accessible scopes" errors because the scope filter is built from a different agentId than what memory_store used.
• Fix: Replace resolveRuntimeAgentId(runtimeContext.agentId, runtimeCtx) with runtimeContext.agentId in all 4 tools, aligning them with memory_store's pattern of using the stable definition-time agentId.
• PR fix: use resolveToolContext in memory_forget and memory_update #270 partially addressed agentId resolution but the runtimeCtx override path remained in these 4 tools.

Fixes #231

Test plan

• All existing tests pass (npm test — 0 failures)
• Verify that memory_store + memory_update/forget/stats/list use consistent agentId when execute-time context differs from definition-time context

🤖 Generated with Claude Code