v0.79.7
August 7, 2026
Four targeted closures. Activity sequences now resume reliably from every channel — including AI agents via MCP —, completed items no longer accept changes even under concurrency, the scheduler no longer produces false conflicts, and the activities' technical configuration stays on the server. No migrations: a simple upgrade.
-
Improvement
Sequences guaranteed from every channel
The intent to continue a sequence is now recorded in the same transaction as the completion, on every channel: UI, API, extension and MCP agents. A crash at any point can no longer leave the sequence stalled; recovery is automatic.
-
Improvement
Completed items truly closed, scheduler without false conflicts
Saving data on a completed item is rejected even when the closure lands an instant before the save — no data or revisions touched. And the scheduler's anti-race guard now fires only during the real activation window: conflicts reported where no concurrency existed are gone.
-
Security
Activity configuration stays on the server
Runtime activity responses no longer carry URLs, headers, payloads, prompts or scripts: only the fields the UI actually uses travel, with an explicit allow-list that is the same for every role. The designer, where configuration is edited, is unchanged.