Workflow bootup events now emit audit trails

Previously, workflow state changes that occurred during application bootup were not captured in any audit trail, leaving operators without visibility into what happened to workflows during startup sequences. When a system restarted or leadership changed hands, workflows would activate or deactivate silently.

Now, whenever workflows transition between active and inactive states during bootup, audit events fire with the relevant metadata — workflow ID, name, version, and the reason for any deactivation. The event types n8n.audit.workflow.activated and n8n.audit.workflow.deactivated carry this information through the message event bus, creating a searchable record of system behavior during critical startup moments.

In the CLI package's active workflow manager, two new audit event emissions bracket workflow state changes. Activation always triggers an event, while deactivation events are scoped to init and leadershipChange activation modes — deliberate boundaries that prevent excessive noise during normal operation while capturing meaningful state transitions. This gives operations teams the audit trail they need to reconstruct what happened during any boot sequence.