v0.1.0-alpha.5

What's new for people using Fiji
Windows: runs work again. In alpha.4, Fiji on Windows refused every run before it started ("could not be asked whether they can write run records … NameError: name 'version' is not defined"). Fixed. (#55, found in test round alpha.4, LabConstrictor-Tools#141)

Run a tool again without the menu. When a run ends, the same tool's form opens again with the values you just used. Change what you need and press OK for the next run (a new guess in Guess the Condition, another parameter, the next image). Press Cancel when you are done. (#61, fixes #58)

An image's "(or file)" field starts empty again, so the next run uses the open image.
A field the tool marks "clear after run" (a guess, for example) goes back to its default after a run that worked.
Lists that come from another tool are asked again.
Each run has its own run record, Log lines and macro line.
A call from a macro still runs once.
The choosers remember. The next time you open the menu, the app and tool choosers start on the ones you picked last. (#61)

A Back button. [< Back] [OK] [Cancel]: from a tool's form back to the list of tools, and from the list of tools back to the list of apps. If you pick the same tool again, its form shows what you had typed. A list with only one entry is skipped. (#64)

Help on the inputs. An input that has a description shows ⓘ after its label. Hover over the label or the field to read it. (#63, LabConstrictor-Tools#147)

How to stop a run is now on screen. While a tool runs, the status bar says "(press Esc to cancel)". (#60, fixes #56)

The run record is finished before the message. When a run is refused or fails, its record is complete before the error dialog shows, not only after you close it. (#59, fixes #57)

Results and Cancel are more reliable. (#54, fixes #32 and #33)

Fiji waits until a tool's outputs have arrived before it shows them.
Cancel also stops the processes the tool started, not only the tool itself.
For developers
UI audit driver: a test that opens each tool's dialog in real Fiji, presses every control, and checks the windows, overlays and results. It is not part of the default CI. (#53)
The user guide no longer says that no release exists. (#62)
Full Changelog: v0.1.0-alpha.4...v0.1.0-alpha.5

Before publishing (checklist, not part of the notes)
Guillaume's OK on the tag v0.1.0-alpha.5. QuPath is already on alpha.5; hosts tagged together share one version, so maybe napari alpha.5 at the same time.
Pre-release (like alpha.1 to alpha.4) or Latest (as QuPath alpha.5 was published)?
Optional: a dry run first (Actions > release > Run workflow, tag v0.1.0-alpha.5-dry). It builds and smokes the jar and creates no tag or release.
Nobody has tried #61, #63 or #64 by hand on Windows or macOS yet; CI is Linux.