v0.3.55 — References follow their step; runs keep their definition

Upgrading from 0.3.54:

• Rebuild and recreate the app container (docker compose up -d --build alexclaw-prod). Two migrations run on start: workflow_runs gains a nullable definition column, and step positions become unique within a workflow.
• Data exports made before the upgrade still restore. A file from an older schema is accepted when the database has only added nullable columns since; those columns come back empty. A file from a newer schema is refused, and so is one that lacks a column the database requires or has one it no longer has, naming the table and column.
• Removing a step that another step routes to or takes its input from is refused, naming those steps. Reroute them first.
• Reordering or removing steps rewrites every route (goto) and input_from, so each still points at the same step. Removing a step also numbers the remaining steps 1, 2, 3… again, closing gaps left by earlier removals.
• Two steps of one workflow can no longer share a position: adding a step at a taken position, or importing a file with two steps at one position, is refused.
• Workflows that had two steps at one position are renumbered on upgrade (order kept) and disabled, listed in the log. Before enabling one, check its routes: a step that shared a position never ran before, and would run now.
• Runs record the workflow as it was when they started (each step's position, name, skill, config, routes and input from). Secret config values are stored as "<secret>", never the value. Runs from before the upgrade have no recorded definition.

Changes

• A run's history no longer depends on the workflow as it is now: renaming, reordering or deleting steps later leaves an old run's recorded definition as it was.
• The admin UI names the steps that still point to a step it was asked to remove.