Gronk v0.1.3

Update from any earlier build. Every release before this one has at least one
feature that does not work.

Added

Search every session by title or message text, from the sidebar. It spans
Chat and Build together — you remember what was said, not which surface you said
it on — and each result says where it matched and which one it came from. Agent
reasoning is searched as well, since it often names the file the visible answer
only alludes to.

Fixed — the preview pane

Its security was hardened in 0.1.2. Its actual operation had never been
exercised. Six defects, each measured rather than reasoned about:

• It could fail to find your dev server at all. The URL scan ran on a
  redacted copy of the output, so a server printing its own address with a query
  string had that address mangled before it was matched. The capture also stopped
  only at whitespace, so App running at http://localhost:3000.,
  (http://localhost:3000) and markdown links all produced something unparseable
  — after which the pane waited forever with no error.
• Stopping it could leave your dev server running. A process-tree kill breaks
  when an intermediate exits, which is exactly what npm run dev does when it
  hands the server to a detached grandchild; the port stayed bound. A port sweep
  now follows, and on macOS and Linux it escalates to SIGKILL.
• A failed kill could crash the app. The guard could not catch the error it
  guarded, which arrives asynchronously and became an unhandled exception.
• A stopped pane could come back, and a failed start left it reporting
  "running" forever with nothing behind it.

Fixed — plugins

• The trust dialog said "Pinned commit" when nothing was pinned. The install
  never received that commit and never verified it afterwards. It now says what
  the value actually is and that the install is not pinned to it.
• A plugin source could specify any scheme. The https-only check covered
  catalog entries read from disk but not ones arriving from the CLI, so a
  marketplace listing could name a local file or an ssh target and have it
  installed. The check now sits at the install itself.
• A successful install could empty the Installed list when the follow-up read
  could not be parsed, making a working install look destructive.

Which file do I want?

Platform	File
Windows	Gronk-0.1.3-windows-x64-setup.exe (installer) or -portable.exe
macOS	Gronk-0.1.3-macos-universal.dmg — Apple Silicon and Intel
Linux	Gronk-0.1.3-linux-x86_64.AppImage or -amd64.deb

Node.js is not required. You do need the Grok CLI and your own
Grok account.

These installers are unsigned

macOS will say the app is damaged. It is not. Right-click and choose Open,
then confirm — double-clicking will not work until you have done that once.
Windows SmartScreen: More info → Run anyway.

SHA256SUMS.txt verifies the download arrived intact. That checks integrity, not
authorship — only signing does that.

Known limitations

• Developed and tested on Windows. The macOS and Linux builds come from CI and
  have not been run by the author.
• No automatic updates.
• Conversations are stored on your machine as readable text. Do not paste secrets
  into a chat.

Full detail in CHANGELOG.md.