flowdrop 2.7.0-alpha2

The second alpha of 2.7.0. The editor gains Test mode: the Playground docked into the canvas you are editing, behind an Edit | Test switch in the navbar, with a list of the workflow's runs and a Problems indicator that diagnoses the unsaved draft and fixes it as one undoable edit. A workflow's chat is now set up in its own Playground settings rather than guessed from node names, and a workflow has no chat until somebody sets one up. The editor's look is new too: redrawn node cards, zoom levels that simplify the canvas as you zoom out, and Graphite as the default theme.

Why an alpha: the bundled editor is a development build of the next @flowdrop/flowdrop release, not yet published on npm, and the chat binding changed shape between alpha1 and alpha2. The full test suite is green. Try it on a development site first.

What is new

• Test mode in the editor. Open /admin/flowdrop/workflows/{id}/editor?mode=test, or use the Edit | Test switch, to run the workflow you are editing next to its canvas. The editor's Test mode task and the Open in Playground links on sessions go there. A new switch,
  Offer Test mode, on the UI settings form turns it off. The standalone Playground page still works but is deprecated (#3592465).
• Runs list and in-editor Doctor. In Test mode a Runs list shows the workflow's recent runs, with rerun and cancel. The Problems indicator diagnoses the draft as you edit it and applies a
  remedy as a single edit you can undo. Two new endpoints serve them: POST /api/flowdrop/workflow/{id}/diagnose and …/remedy, plus
  POST /api/flowdrop/pipeline/{id}/rerun.
• A workflow's chat is its Playground settings. Which input receives the person's message, which gets the history, and which
  node outputs print as replies are saved with the workflow, so they are versioned, exported and imported with it. The Playground shows a chat box only when a message input is bound. The upgrade writes these
  settings for every workflow that chats today, so no working chat is lost. A workflow built only from text_input / text_output nodes gets no chat until you set one up; the
  workflow doctor lists it (#3592465).
• The AI Assistant can read a run. Two new assistant tools, site_get_run and site_get_node_run, answer what a run did, which node failed and why, and which nodes were
  edited since. Run data goes to your model provider, so the chat settings have a Run tools switch (on by default).
• A trigger that did not fire skips itself. In a workflow with several triggers, only the one that fired runs its branch; the others skip with everything only they feed. Under the hood this is a new, general option: a required parameter may say that a missing value skips its node instead of failing it (when_missing).
  Trigger payloads are plain data with a declared shape per event family, and a pipeline now records who or what started it (#3592477).
• Default theme and white-label branding. Under Appearance at /admin/flowdrop/config/ui-settings you can pick the editor's default theme and replace the FlowDrop wordmark with your own logo, name and link. The editor follows Drupal's light or dark mode by default (Match Drupal, from Gin's setting).
• The editor's look. Node cards on a fixed grid with their ports in rows, zoom tiers (full card, outline, map), a terminal-style Command Console that opens as a bottom drawer, workflow settings in a resizable sheet behind a navbar Workflow button, and Graphite as the default theme. Branching nodes always draw as gateways; the per-node-type visual type setting is no longer used.

What is fixed

• A session waiting for a person's answer can be stopped. Stop used to be refused, and the paused run kept waiting.
• A workflow that takes no message and declares no inputs can be run from Test mode; the turn endpoint no longer demands a message for it.

Upgrading

1. Update the module as usual. Drupal ^11.3, PHP 8.3 or later.
2. Run drush updatedb. Updates and post-updates in six modules add a settings field to sessions and a started_by
   field to pipelines, write each chatting workflow's Playground settings, mark the sessions the Playground created, and give every trigger node type its reserved event input and payload ports.
3. If the update says some sessions were not checked, run drush flowdrop:playground:mark-sessions.
4. Run drush cr, then export configuration if you track it. Several of the updates write config.
5. Coming from alpha1: the interface turn
   annotations alpha1's upgrade wrote are moved into the Playground settings and removed from the interface. turn is deprecated.
6. Sub-workflows in a shared session post their replies to the parent's conversation only when the parent's Playground settings ask for it (sub_workflow_replies). A child whose chat_output used to print there is no longer printed.
7. No permission changes.

For developers

• New @api: TurnBindingResolverInterface (flowdrop_session), ConditionalServerToolInterface (flowdrop_chat), EventPayloadSchemaInterface (flowdrop_trigger), and the SetThirdPartySetting mutation primitive.
• New endpoints: GET /api/flowdrop/sessions/{uuid}/runs, the Doctor's diagnose and remedy, pipeline rerun, and paging (?limit, ?offset) on GET /api/flowdrop/workflow/{id}/pipelines.
  Workflow payloads carry playground.
• Deprecated for 3.0: turn on the workflow interface, the standalone Playground page, LegacyChatInputLocator and LegacyReplyMatcher. alpha1's turn-port post-update and its doctor diagnostic are removed.
• An event type plugin's extractTriggerData() returns plain data only. Validator rule R16 refuses an edge into a trigger's event input.
• The bundled @flowdrop/flowdrop is a development build, 2.11.0-dev-9ecc00d6 (from 2.10.1). Sites that mount the library themselves should wait for the next npm release.
• css/design-tokens.css is gone: the design tokens come from the library build. Overrides of that file must target the two new files.

• CHANGELOG.md
  — everything that changed in 2.7.0-alpha2.
• UPGRADE.md — the 2.7.0-alpha1 to 2.7.0-alpha2 section (and, from 2.6.0, the section before it).

This is a pre-release: try it on a development site first. Questions andbug reports are welcome in theissue queue.