219cb714a1
On the stateless api_server platform, a background delegate_task completion was delivered by self-POSTing /v1/chat/completions with role=user after the parent turn had already completed (event.complete, finish_reason=stop). That starts an unauthorized new agent turn the client never sent, persists the completion as an ordinary role=user row (display_kind NULL), and can blow through a pending human-confirmation gate — the exact skip-ahead reported in #85957. Fix: async_delegation completions targeting a non-push api_server session are now written into the session transcript as a durable DELIVERY row (role=user + display_kind=async_delegation_complete + display metadata — the same bookkeeping shape the TUI/desktop delivery path persists). No agent turn runs; clients polling GET /api/sessions/{id}/messages see the result immediately, and the next real client turn carries it as context. Persist failures return False so the durable claim is released and the completion retried. Watch-pattern notifications keep the existing self-post wake behavior; push-capable adapters are untouched. Fixes #85957