neutralize upstream service branding

This commit is contained in:
2026-06-12 16:31:08 +08:00
parent 126ae4eafa
commit 42de7f9da0
18 changed files with 340 additions and 256 deletions

View File

@ -1,6 +1,6 @@
# Memory Gateway multimodal API test
This file records a real end-to-end test through **Memory Gateway**, not direct EverOS calls.
This file records a real end-to-end test through **Memory Gateway**, not direct upstream memory service calls.
Gateway URL used by curl:
@ -8,7 +8,7 @@ Gateway URL used by curl:
http://127.0.0.1:8010
```
Gateway upstream EverOS:
Gateway upstream memory service:
```text
http://10.6.80.123:1995
@ -35,7 +35,7 @@ Command:
```bash
cd /home/tom/memory-gateway
EVEROS_BASE_URL=http://10.6.80.123:1995 \
MEMORY_GATEWAY_BACKEND_BASE_URL=http://10.6.80.123:1995 \
MEMORY_GATEWAY_DB_PATH=/tmp/memory_gateway_curl.sqlite3 \
MEMORY_GATEWAY_STORAGE_DIR=/tmp/memory_gateway_curl_storage \
MEMORY_GATEWAY_HOST=127.0.0.1 \
@ -136,7 +136,7 @@ Response:
```json
{
"session_id": "chat:gateway-multimodal-20260611180257",
"everos": {
"backend": {
"request_id": "c9e24b8d27ee4ad08a8df70273336637",
"data": {
"message_count": 1,
@ -174,7 +174,7 @@ Response:
```json
{
"session_id": "chat:gateway-multimodal-20260611180257",
"everos": {
"backend": {
"request_id": "8eb7d5db2d3b43f4999f445aabb813b1",
"data": {
"status": "extracted"
@ -192,7 +192,7 @@ TOTAL_TIME:2.135721
## 4. Search through Gateway
EverOS indexing can lag briefly after `flush`, so this test waited about 2 seconds before searching.
upstream memory service indexing can lag briefly after `flush`, so this test waited about 2 seconds before searching.
Request:
@ -279,7 +279,7 @@ Response:
{
"status": "ok",
"api": {"status": "ok"},
"everos": {
"backend": {
"status": "ok",
"base_url": "http://10.6.80.123:1995",
"data": {"status": "ok"}