fix(demo): treat HTTP 202 Accepted as background-store success

[Fearvox]

fix(demo): treat HTTP 202 Accepted as background-store success

Closes #93.

Problem

SimpleMemoryManager.store() (the demo client in
methods/EverCore/demo/utils/simple_memory_manager.py) called
response.json() on every non-error POST. When the EverCore memory API
runs extraction in the background it answers POST /api/v1/memories with
202 Accepted and an empty body. response.raise_for_status() passes the
202 through (2xx), then response.json() either raises or yields no status,
so store() drops into the failure branch and prints
❌ Storage failed: ... — even though the write was accepted. This is exactly
the symptom reported in #93: "Storage failed: Request accepted, processing in
background."

Fix

Add a 202 branch right after raise_for_status() and before response.json().
On 202 the demo prints a ⏳ Accepted … (Processing in background) notice and
returns True. No other behavior changes — non-202 success and error paths are
untouched.

response.raise_for_status()

# Background mode returns 202 Accepted (memory extraction
# continues asynchronously). Treat it as success instead of
# falling through to result.json() and reporting a failure.
if response.status_code == 202:
    print(
        f"  ⏳ Accepted: {content[:40]}... (Processing in background)"
    )
    return True

result = response.json()

Test

Adds methods/EverCore/tests/test_simple_memory_manager.py, an offline
regression that monkeypatches httpx.AsyncClient to return a 202 response and
asserts store() returns True. No live EverCore stack, database, or network
is required.

Run it:

cd methods/EverCore
PYTHONPATH=src:. uv run pytest tests/test_simple_memory_manager.py -q
# 1 passed

Verified locally on this branch:

• With the fix: 1 passed (exit 0).
• Without the fix (negative control): 1 failed (exit 1) —
  '_AcceptedResponse' object has no attribute 'json' and the demo prints
  ❌ Storage failed, reproducing Storage failed: Request accepted, processing in background #93. This confirms the test exercises the
  fix rather than passing vacuously.

Scope

Two files, surgical:

• methods/EverCore/demo/utils/simple_memory_manager.py (+10, the 202 branch only)
• methods/EverCore/tests/test_simple_memory_manager.py (new, offline regression)

No production memory-layer code is touched; this is demo-client robustness plus
its regression test.

Credit

The 202-handling approach matches upstream PR
#211
("fix: handle 202 Accepted response in demo store method") by @haifengqiu (梓宏),
credited on the commit via Co-authored-by.

---

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.