Everything a workflow is, in one version history

A workflow's definition used to live in four places that could each move without the others noticing. The steps were the version. The written procedure had its own counter. Your uploaded files had none. Replace the price list a step reads and that step was wrong about the world, with no version, no history and nothing to roll back to.

A workflow is now one versioned directory: the procedure, the steps and your reference files together, one counter, one history. Change any of them and a version mints carrying all three. Change nothing and nothing mints, because a version that says nothing new is noise in a history.

A run pins the version it started on and works out of that directory, at start and again when it resumes. Swap a file while a run is in flight and that run keeps the file it began with.

Which is why a change landing on a workflow that already has code asks you instead of guessing. A sharpened sentence and a changed procedure look identical from outside. Reset applies the change now, drops the code, and hands the work back to an agent. Adapt opens a revision interview against your change, and the version mints when you confirm it, carrying the new file, the new procedure and the adapted code at once. Between the question and your confirm, nothing running has moved.

You can open a revision from your own words too, with no file or procedure edit involved. "Nothing needed to change" is a real answer, and the confirm still mints, because the procedure and the files are part of what the workflow is.