fix(reme): align ReMe client with 0.4.x job APIs

[guslegend0510]

Background

Fixes #2005.

agentscope-extensions-reme was still modeled around the legacy ReMe personal-memory endpoints:

• POST /summary_personal_memory
• POST /retrieve_personal_memory

ReMe 0.4.x has switched to job-based APIs and no longer exposes those endpoints, which causes 404s against current self-hosted deployments.

What Changed

• migrate ReMeClient from legacy personal-memory endpoints to:
  • POST /auto_memory
  • POST /search
• update ReMe request/response DTOs to match the ReMe 0.4.x payload and response schema
• update ReMeLongTermMemory to:
  • send filtered messages directly instead of building legacy trajectories
  • support sessionId(String) for ReMe 0.4.x
  • keep userId(String) as a backward-compatible alias that falls back to session_id
  • read retrieval fallback content from metadata.results[].text
• rewrite module tests around the new protocol
• update ReMe docs in v1/v2 EN/ZH to reflect the new session_id-based behavior and remove stale example references

Notes

ReMe 0.4.x no longer provides the old workspace_id-scoped personal-memory API.
For compatibility, this patch keeps the builder surface stable where possible, but userId now behaves as a fallback alias for session_id.

Testing

• mvn -pl agentscope-extensions/agentscope-extensions-mem/agentscope-extensions-reme test

[codecov]

Codecov Report

❌ Patch coverage is 74.54545% with 28 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...agentscope/core/memory/reme/ReMeSearchRequest.java	65.51%	10 Missing ⚠️
...io/agentscope/core/memory/reme/ReMeAddRequest.java	70.37%	8 Missing ⚠️
...gentscope/core/memory/reme/ReMeSearchResponse.java	76.92%	5 Missing and 1 partial ⚠️
...o/agentscope/core/memory/reme/ReMeAddResponse.java	84.61%	2 Missing ⚠️
...gentscope/core/memory/reme/ReMeLongTermMemory.java	84.61%	0 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!