Gronk 0.4.1

A correction and a fix. If you are on 0.4.0, take this one — 0.4.0 gives wrong advice
when a turn fails.

Fixed

A failed turn no longer suggests the wrong cause. 0.4.0 said that a bare "Internal
error" from the agent probably meant a spent plan quota, and told you to check your usage
limits. That is wrong. The Grok CLI reports rate limits on their own error code with their
own message about upgrading, and treats "Internal error" as a server fault specifically
not a rate limit — so a real quota block arrives clearly labelled, and the advice pointed
at the one thing the CLI would already have told you about. The message now says what the
code actually means: a well-formed request that failed inside the agent, worth retrying. It
guesses at nothing.

History from one conversation can no longer be painted into another. Opening a session
can return a different session than the one you clicked, so the app had to accept restored
history for a conversation it had not heard of yet. That left a window, while a session was
opening, where an unrelated session finishing its own startup could repaint what you were
reading — and the save that follows would store it under the name of the conversation you
thought you were in. Each open is now named, and restored history is only accepted from the
open it answers.

Upgrading

Straight over 0.4.0, nothing to migrate. The 0.4.0 note about not going back to 0.3.0 or
earlier still applies: conversations live in one file each now, and older versions read them
out of the store, so they would show every session as empty.

---

Verify a download against SHA256SUMS.txt before running it.