flowdrop 2.7.0-alpha4

It bundles @flowdrop/flowdrop 2.13.0, so Test mode and the Playground stop polling a finished session, and it fixes what testing alpha3 turned up. Try it on a test site, not in production.

Before you upgrade

• From 2.7.0-alpha3: there are no database updates. Clear caches after updating.
• From 2.6.0, 2.7.0-alpha1 or 2.7.0-alpha2: read the 2.7.0 sections of UPGRADE.md first. They have database updates, and alpha2 changed how a workflow's chat is set up.

What changed since alpha3

• Load library defaults loads the current defaults. The button on the UI settings form loaded the 1.10 defaults (dark, Default theme). It now loads Graphite, the light colour scheme and the newer layout keys, read from the bundled library itself (#3592481). Settings a site has already saved are not touched.
• The Interface tab can expose a node's dynamic port, such as a Prompt Template's named inputs (#3592466). It used to offer the port and then refuse to save. This works on node types that allow dynamic ports: Prompt Template, Merge, Data Mapper and Assemble Messages ship that way.
• Drift detection ignores key order (#3592469). A workflow is no longer reported as drifted because the keys of a schema fragment, or its required list, came in another order.
• The loop Doctor warns less. LOOP_PORT_BEHIND_GATEWAY now shows only where a run still fails, not where the consumer is simply skipped (#3592479). Expect some Doctor findings to disappear.
• Entity presave and Form validate say what they do (#3592476). They observe the event; a run cannot change the entity or reject the form. Behaviour is unchanged.
• The Playground stops polling a finished session, in the
  standalone page and in Test mode (fdnpm#46). Polling starts again on the next turn.

For developers

The full list is in CHANGELOG.md. The bundled library @flowdrop/flowdrop is 2.13.0, which adds a playground mount option for the docked Playground. A site that builds the library itself should rebuild from 2.13.0.

An exposed dynamic port has a lane (its data type) but no JSON Schema type in the workflow's schema snapshot, so values passed to it from a parent workflow are not type-checked.