Avoid FlowDrop UI becoming a themed variant of BPMN.io

With the current model abstraction relying on BPMN structures, there is a risk that FlowDrop UI will offer only surface-level value, i.e. a styled fork of the BPMN.io modeler with limited integration benefits.

This undermines our goal of building a deeply integrated Drupal-native workflow editor.

Discussion Points:

• How can FlowDrop assert more control over the model and runtime behaviors?
• What custom UI affordances can differentiate FlowDrop from generic BPMN editors?