A run in history can become a preset, or happen again

[thousandflowers]

History recorded what had been done and could do nothing about it. The missing piece was in the entry: it kept which preset had run, not what that preset did, so a preset edited or deleted since left a row describing a conversion nothing could reproduce. The chain is now written down beside it, optional so older history still decodes.

With the chain there, a row offers three things in order of how useful they are:

1. Save as a preset — the same mapping in the other direction, saved through the ordinary path, indistinguishable from one made by hand.
2. Run on other files — files chosen now, so nothing can be stale.
3. Run again on the same file — the delicate one. An original that has moved is named rather than skipped in silence, and a run recorded with no destination folder replaced its original, so repeating it goes through the existing replace confirmation rather than around it.

Revealing outputs in Finder was already there and stays.

Test plan

• swift test — green
• 7 tests: chain round-trips into a preset, an old entry says why it cannot be repeated, a missing source is named and the rest carries on, in-place re-run still classifies as block
• Real History.json from a CLI conversion now carries presetName and actions

🤖 Generated with Claude Code

https://claude.ai/code/session_018H9CZxWumc3ryumgEHd578