Exact

Exact Union RegExp

Alessandro 505c0b4dc6 Clear scheduler errors after successful chat continuation ... Failed scheduler tasks stayed in Error when their chats resumed outside the scheduler runner, even after successful replies and a persistence reload. Persist the owning task UUID in chat context data and reconcile successful main-agent monologues with the associated errored task. Save Idle, the recovered result and its completion timestamp through a checked update. Preserve planned launch progression, normal retry callbacks and unrelated, disabled, removed or reassigned tasks. Legacy dedicated chats resolve by context ID; legacy shared chats still require an explicit scheduler retry. Add regression coverage for failure, restoration, two successful chat steps, all task types, JSON/YAML persistence, cancellation and ownership guards. Update the scheduler and extension contracts. Validation: 31 scheduler tests passed in the localhost:32081 container's framework runtime. Broader lifecycle checks: 65 passed, with one unrelated nudge fixture failure reproduced with reconciliation disabled. No live provider/model-switch test or service restart.		2026-10-21 14:19:51 +02:00
..
_20_update_scheduler_task.py	Clear scheduler errors after successful chat continuation	2026-10-21 14:19:51 +02:00