0.3.1

An audit of the whole plugin, and the fixes it turned up. Nothing new to learn — the
things below either did not work or were not true.

Fixes

• The note button in the panel header saves what you press. It wrote to the chat
  history file instead of the settings, so "send the current note as context" was back to
  off by the next start.
• Alt+1 is no longer promised out of the box. It has not been claimed automatically
  since 0.1.3 — a plugin should not take a key on someone else's keyboard — but the README
  and the quick-menu description still said it would. The switch that gives the menu its
  key is right there in the quick-menu settings.
• An empty address is a refusal, not DeepSeek. Picking "Custom" and pressing "Test
  connection" before typing anything used to send your key to a provider you did not
  choose.
• A full URL pasted from the documentation works. A trailing /chat/completions is
  dropped before the method is appended, so the model list no longer asks the provider for
  .../chat/completions/models.
• An answer cut short by a new question stays on screen but out of the conversation.
  Filed at the end, it used to sit after the question that interrupted it — in the feed
  and in the context of the next request, in that order.
• A word-level diff costs a third of the memory it did, and a pair of very long texts
  is counted rather than drawn.
• Smaller: the chat history is never written to the vault root; a tool name that a
  provider repeats in full in every chunk is not glued to itself; an edit is undone in the
  note itself rather than in a tab that only looks like one; a failed request without
  streaming no longer surfaces as an error in the console.

Said out loud

A model allowed to edit notes can read the open note by itself, whether or not "Send the
current note as context" is on. Every call it makes is shown in the panel as a card — and
now the setting and the README say so too, instead of leaving two switches that look like
one promise.