v0.84.0
August 21, 2026
Events delivered all the way through and clear answers even in edge cases. The event engine always executes every action of an event, in the right order and without duplicate effects; an overly wide calendar range is rejected with an explicit message, deleting an initiative from the Plan never leaves orphaned elements, and integrations see more while revealing less.
-
Improvement
Every event action reaches its target
When an event triggers multiple automations on the same element — say, a data update and a phase change — they now all run, in the right order: data and notifications first, then the transition. Duplicate actions produce a single real effect, and an already-processed event can no longer be mistakenly reclassified as "no recipients".
-
Improvement
Calendars without silent narrowing
If an integration asks the calendar for a range wider than the allowed maximum (366 days), it receives a clear, actionable error instead of partial results over a silently reduced window: widening the requested period can no longer return fewer results than before. Normal calendar use is unchanged.
-
Improvement
Always-consistent deletions from the Plan
Deleting an initiative from the Plan always closes its linked governance element; if closing fails, the deletion stops and can be retried, instead of leaving an open element with no lifecycle. No more orphans to clean up by hand.
-
Integration
Agents also see process events
AI assistants connected via MCP that read a process now also receive each phase's event subscriptions — which event, which action, and toward which target — in the same shape as the Designer API: the full event-driven behavior in a single read.
-
Security
More discreet authorization errors
The integration authorization endpoints answer a malformed request with a standard error and a stable message: no internal technical details end up in public responses anymore.