Some programs put the terminal into a mode of their own choosing while moor is still running. Known culprits are cmd.exe on Windows, and Node.js on all platforms when piping its output into moor. Before this release, that could make moor miss arrow keys and sometimes print garbage to the console. With this release, moor sets the terminal mode it needs as it goes, so navigation keys keep working regardless. This also covers coming back from an editor launched with "v", which on Windows could ignore navigation keys for many seconds afterwards. On Windows this also fixes moor sometimes leaving the terminal in a broken state after exiting. Also in this release:

• Support for the Unicode 17.0.0 tables in the upcoming Go 1.27, through an updated charlievieth/strcase dependency