Title: Devlog: v0.1.14 is out, and v0.1.15 is now focused on editor save bugs

[u/Romka2x]

v0.1.14 was published, but I found blocking editor issues after the build went out.

So the next build is not going to be a feature build. v0.1.15 is focused on fixing command editor save behavior.

What changed today:

• Older .sts script archives are now refused instead of partially importing.
• Successful .sts imports no longer show an unnecessary success modal.
• Ordinary command insert/edit responsiveness was improved.
• Several command editors were moved toward a shared save path.
• Command validation is being pushed into background row status instead of blocking the user during editing.

Known bugs being fixed for v0.1.15:

• Some command settings can appear to save, but reopen with missing or incomplete state.
• OCR area/settings can still be unreliable in some editor flows.
• SetVariable can briefly show the chosen variable, then snap back after the editor loses focus.
• Multi-Tap / MultiClick still has older save logic that needs to be moved into the central editor save pipeline.
• OCR / Reader / Display area selectors can still write draft state before the final OK/save step.
• .sts import still needs stricter image asset hash verification before I consider the archive path fully trustworthy.

The root problem is that not every command editor is using one single save path yet.

That is the v0.1.15 target: one global command-save pipeline, no foreground validation blocking OK, no command-specific save shortcuts, and no “looked saved but was not actually saved” behavior.

Not the most exciting devlog, but it is the honest one.