redrafter 0.1.16

If 0.1.15 told you the Default preset was edited, it wasn't

Upgrading to 0.1.15 left a lot of installs with the new Default preset
showing an "edited" badge, over a direction nobody had written.

0.1.14's Behavior screen prefilled its text box with "Fix grammar, spelling and
clarity - keep my voice, tone and length." and saved on blur whether or not you
had changed anything, so clicking into that box once was enough to store it.
0.1.15's upgrade step read that back as your own wording, carried it onto the
Default preset, and marked the preset overridden. The visible part was the
badge; the part you could not see is that it also replaced the fuller shipped
instruction - the one that says preserve length, do not summarize, reply with
only the corrected text - with that single sentence.

This release ignores wording that came from us rather than from you, and repairs
installs that already took the bad upgrade: if your Default preset carries one
of those two shipped strings, the override is dropped and the preset goes back
to reading as the built-in it always was. A direction you actually wrote is left
exactly where it is.

Update checks happen on their own now

The updater only ever ran when you opened the menu-bar menu and clicked Check
for updates…, so a release could sit there indefinitely with nobody told. A
check now runs shortly after launch and once a day after that, and the menu item
names what is waiting: Update to 0.1.17… rather than Check for updates….

Nothing is downloaded or installed without you asking. General has a switch
to turn the automatic checking off.

And it tells you what it found

Clicking Check for updates… used to write its answer to the menu-bar
tooltip and nowhere else, so it looked like a dead menu item unless you thought
to hover the icon afterwards - and a check that failed outright looked exactly
like a check that found nothing. The answer now appears on screen: the version
that is waiting, that you are up to date, or why the check could not run.

Downloads

Platform	File
macOS (Apple Silicon)	redrafter_0.1.16_aarch64.dmg — signed and notarized
Linux	redrafter_0.1.16_amd64.AppImage, .deb, .rpm
Windows	redrafter_0.1.16_x64-setup.exe

redrafter 0.1.15

Writing rules: the things you never want the model to do

If you had put "never use em dashes" into the Default direction on the
Behavior screen, it worked right up until you used a preset. /formal or
/rd make it shorter replaced that direction wholesale, em dashes and all -
so the rule applied to exactly the refines you had not customized, which is
the opposite of a rule.

The Behavior screen now has Writing rules instead, and they are sent with
every refine no matter what else is in play. They ship with a starter set
(no litotes, no em dashes, no "here is what people miss", no mic-drop
endings), you can edit them freely, and a switch turns the whole block off
without losing what you wrote. Where an instruction contradicts a rule -
/bullets against a rule about lists - the instruction wins on that point
and the rest of the rules still hold.

Reset to defaults restores the rules this build ships. Leave them
untouched and a future release can improve them; edit them and yours are kept
as they are.

The baseline instruction moved to Presets

What used to be the Default direction is now a preset called Default,
pinned at the top of the Presets list. It is what runs when your selection
names no preset, and it is edited the same way as /formal - including
Reset to default if you want the shipped wording back. It has no /slash
trigger, because typing one would only ask for the direction that was already
going to be used.

If you had edited the old default direction, that wording moves onto the
Default preset the first time you launch this version. Nothing to do.

Re-running an entry from History now obeys your Default preset and your
writing rules too; it used to ignore both.

Downloads

Platform	File
macOS (Apple Silicon)	redrafter_0.1.15_aarch64.dmg — signed and notarized
Linux	redrafter_0.1.15_amd64.AppImage, .deb, .rpm
Windows	redrafter_0.1.15_x64-setup.exe

redrafter 0.1.14

The Presets editor uses the whole window now

Editing a preset happened in a box roughly 420px wide, whatever size you made
the settings window. It was tight enough to clip the Model override menu
mid-word — it read Inherit (active mo — and to squeeze every pair of fields
next to it. Making the window bigger didn't help: the box stayed put and the
empty margins either side got wider.

The Presets screen was inheriting a width limit meant for the single-column
forms (General, Behavior), which never needed the room. It now grows with the
window, so the editor gets the space instead of the margins:

• Field pairs sit side by side while both fit and drop to one per line when
  they don't, so a menu is never narrower than the value it has to show.
• Below about 720px the preset list moves above the editor rather than
  competing with it for width.
• Long values — a model id, a base URL — wrap instead of pushing the panel
  past the edge of the window.

At a typical settings-window size the editor is now roughly twice as wide as
it was.

Downloads

Platform	File
macOS (Apple Silicon)	redrafter_0.1.14_aarch64.dmg — signed and notarized
Linux	redrafter_0.1.14_amd64.AppImage, .deb, .rpm
Windows	redrafter_0.1.14_x64-setup.exe