0.4.0

Two days of quality-of-life work — and a handful of things that could quietly eat your
text.

Changed on purpose: Enter in the quick menu

A one-off instruction typed into the quick menu used to rewrite the selected text on
Enter and answer in the chat on Ctrl+Enter. They are the other way round now: Enter
answers in the chat, Ctrl+Enter rewrites the text. "Summarise this chapter", typed in a
hurry, used to replace the chapter with its summary — and Enter is a key people press
without looking. The destructive one should cost an extra finger.

Working without selecting anything

• The section under the cursor joins the whole note and the paragraph as an answer to
  "what if nothing is selected". It runs from the heading above the cursor down to the next
  one of the same level, subsections included — exactly what folds when you collapse that
  heading. The heading goes to the model together with the text, so it knows what the text
  is about; the blank lines and the --- before the next section stay behind.
• The quick menu shows what it took: a row of paragraph / section / note with the size
  of each, the one from your settings picked, and the piece itself highlighted in the note.
  The arrow keys change it for that one run, and your setting stays as it was. An empty
  line no longer means "select something first" either — the menu opens with the section.
• A question before sending a lot. Past a threshold you set — 20 000 characters by
  default — a long piece goes to the model only after you say yes. 0 never asks.

Right-click on the selection

The editor's context menu now offers the quick menu and a question to the chat — and the
actions from your keys, each on its own line, if you switch that on in the quick-menu
settings. On a phone it is the same menu, held down. With nothing selected the plugin adds
nothing to it: a stray click should not rewrite a whole note.

The conversation is yours to edit

• "Ask again" under an answer drops it along with the question and sends the question
  again, exactly as it was — down to the system prompt, if it came from an action.
• The pencil under your own question puts the text back into the field, with the
  fragment it was about, and takes the rest of the conversation off.
• The bin removes a message; a question leaves together with the answers to it.
  Anything removed comes back from the notice, the same way a cleared chat does.
• The input field remembers. An unfinished question survives closing the panel and
  restarting Obsidian, and the up arrow walks through your previous questions.
• Every answer is signed with the model that wrote it. Models are switched from the
  panel header, and afterwards there was no telling who said what.
• A saved conversation is named after its first question, not by the date alone.

Run it again

The journal of edits got a second button. "Run it again" brings the text back and runs the
same action over it once more: the old card becomes "undone", the new edit lands below. An
answer from a model is a roll of the dice, and rerolling it used to mean Ctrl+Z by hand
plus finding the action again.

Things that were happening to your note

• An action that answers in the panel no longer gets the editing tools. "Show it in the
  panel" already says "leave the note alone" — but the model had the tools anyway, and
  "summarise this chapter" could end with the summary lying where the chapter was.
• …and it no longer drags the open note along. "Send the current note as context" is
  about a conversation in the panel; an action over a selection has already said what to
  work on. The model was seeing the same text twice and taking one of the copies for a
  duplicate.
• An action no longer picks up the fragment attached in the panel. A paragraph went as
  the question, and a whole chapter went with it — attached earlier, and paid for again.
• "Apply" on an edit card no longer takes the keyboard focus. The card appears by
  itself, in the middle of an answer, and Enter at that moment — the Enter just pressed to
  send the question — meant "yes, rewrite my note".
• A cut-off answer never goes into the note. When the model runs out of room and stops
  mid-sentence, the reply is not written over your text: it stays in the card, and the chat
  says what happened. The provider says so in finish_reason, which the plugin had never
  read.

Gone

• Thinking mode. The switch asked for reasoning but could not forbid it: a model that
  reasons by default kept reasoning with the switch off. A setting that does not do what
  its name says is worse than no setting at all.
• Translation language. It fed {lang} to prompts, and the action that used it was
  removed two versions ago.