Back to the changelog

v0.79.8

August 7, 2026

Real governance on published flows. A published flow is now immutable — you change it by creating a new Draft version — and each item's history records the exact design version behind every event. Misconfigured rules are stopped at publish time, AI agents follow the same policies as the UI, and Process Maps gain full link management.

  • Feature

    Immutable published flows, faithful history

    Any change to a published flow's definition is rejected: you work on a new Draft version, and the audit stays reproducible. History freezes the version and phase names at the moment of each event — older rows openly declare when the snapshot is unavailable, instead of showing current names as if they were historical.

  • Improvement

    Configurations stopped before they become problems

    A phase with a timeout but no resolvable destination now blocks publishing with an error that says what to fix — before, it silently failed at runtime, every minute. Scheduled dates get a maximum horizon (10 years) on every channel, and new flows start with the event trigger disabled: you enable it deliberately, with the event dictionary one click away.

  • Improvement

    Agents and UI, same rules

    Manual transitions decided by MCP agents now follow the same policy as the UI (roles, allowed transitions, completed items), AI flow generation saves every policy through the canonical writer — no more silently dropped fields — and every Flow Agent operation is signed with the key's real identity, no longer a generic "system".

  • Design

    Process Maps: links under control

    Map links can now be selected with a click and removed via the contextual trash button or the keyboard, with confirmation. The change only affects the map drawing: flow configuration is untouched.