yetuge 11e0195fe9

refactor(gateway): route memory mutations through the shared drained-write helper (#6164) ...

Memory router kept its own bare drain wrapper (_run_memory_mutation,
five call sites) after #6151 hoisted the superset into
app.gateway.persistent_writes.run_drained_write - this is the remaining
per-router fork called out in that review.

Each call site passes the domain errors its handler already maps
(NotImplementedError 501s, ValueError/KeyError 400/404/409 mappings,
MemoryConflictError/MemoryCorruptionError, OSError 500s), so the helper
stays silent on them exactly as the removed wrapper did; unexpected
failures gain the type-only lost-failure log line per the AGENTS.md
rule. Behavior is otherwise unchanged: same off-thread execution and
cancel-drain semantics.

The router test's drain stub moves to the shared name and pins the
clear-memory error tuple.

Signed-off-by: yetuge <2219677952@qq.com>

2026-10-02 21:41:50 +08:00

..

channels

feat(scheduler): push scheduled task results to IM channels via a notification outbox (#6135)

2026-10-01 17:59:30 +08:00

gateway

refactor(gateway): route memory mutations through the shared drained-write helper (#6164)

2026-10-02 21:41:50 +08:00

mcp_tasks

fix(mcp): reserve notification launches atomically (#5965)

2026-09-30 09:12:11 +08:00

scheduler

feat(scheduler): push scheduled task results to IM channels via a notification outbox (#6135)

2026-10-01 17:59:30 +08:00

subagent_batches

feat(subagents): add unified capacity and durable batch execution (#4998)

2026-08-25 07:49:38 +08:00

__init__.py

refactor: split backend into harness (deerflow.*) and app (app.*) (#1131)

2026-03-14 22:55:52 +08:00