docs(reliability): record live agent.wait fix verification

memory/2026-03-13.md

@@ -73,6 +73,20 @@
 - Net status at end of this pass:
   - subagent persistence/announcement fix: live-verified
   - raw `agent.wait` follow-up fix: tests passed, but live source-gateway repro still failed; do not mark this closed
+- Final focused live-fix pass on 2026-03-13 closed the remaining raw `agent.wait` bug.
+  - root cause: the live direct gateway path could receive `agent_end` carrying a terminal assistant error without a preceding `message_end`, leaving stale/empty assistant state and still emitting lifecycle `phase:"end"`
+  - final upstream fix taught embedded subscribe lifecycle handling to recover the terminal assistant from `agent_end.messages` / session transcript and emit lifecycle `phase:"error"`, and taught the gateway `agent` RPC handler to derive terminal status from observed lifecycle + final result metadata instead of blindly caching `ok`
+  - final targeted validation passed:
+    - `pnpm -C /home/openclaw/.openclaw/workspace/external/openclaw-upstream test -- --run src/agents/pi-embedded-subscribe.handlers.lifecycle.test.ts src/agents/pi-embedded-subscribe.subscribe-embedded-pi-session.subscribeembeddedpisession.test.ts src/commands/agent.test.ts src/gateway/server-methods/agent-wait-dedupe.test.ts src/gateway/server-methods/server-methods.test.ts`
+    - result: `108 tests` passed across `5` files
+  - decisive live source-gateway repro after the final fix:
+    - gateway: source-run on port `18903`
+    - run id: `gwc-live-agent-wait-gpt53-source-fixed2-1773429512008`
+    - final `agent` response returned `finalStatus:"error"`
+    - matching `agent.wait` returned `status:"error"` with the same context-window error text
+- Net status now:
+  - subagent persistence/announcement fix: live-verified ✅
+  - raw `agent.wait` semantics fix: live-verified ✅
 - Side note: unrelated dirty `/subagents log` UX changes in `external/openclaw-upstream` regression-passed `src/auto-reply/reply/commands.test.ts` (44 tests) but were intentionally left out-of-scope for this focused reliability pass.
 - Will also explicitly requested that zap keep a light eye on active subagents and check whether they look stuck instead of assuming they are fine until completion.
 - Will explicitly reinforced on 2026-03-13 that once planning is done, zap should use subagents ASAP and start implementation in a fresh session rather than continuing to implement inside the long-lived main chat.