Bring the docs up to the chat window we actually built

The readmes still described a single expand glyph and a chevron for saved chats, and neither knew about the banner, the two expanded sizes or the shortcuts list.
2026-08-09 13:45:30 -04:00
parent 66f9d6f435
commit 4b6c5fe1cc
3 changed files with 30 additions and 7 deletions
@@ -128,8 +128,20 @@ composed from a prefix so instances can coexist, and each tears down the previou
 prefix, because Unraid swaps tab content by AJAX without unloading the old page's JavaScript.

 A placement chooses how much room it gets and which extra controls it needs. It does not choose
-the shape: the control row is fixed everywhere — profile chip hard left, `⤢` `▾` `New` `Ask` hard
-right — because a chat that rearranges itself per tab is three components wearing one name.
+the shape, because a chat that rearranges itself per tab is three components wearing one name.
+The layout is fixed everywhere:
+
+- **Banner** — title, then `Medium`/`Large` and `Shortcuts` at the right.
+- **Transcript**.
+- **Composer**, then one row grouped by what each control acts on: the profile chip at the left
+  for what is *answering*, `New` `Saved` `Ask` centred for what you do to the *conversation*, `⤢`
+  at the right for what you do to the *window*.
+
+`⤢` and `Medium`/`Large` are deliberately separate: whether the conversation is expanded is an
+action taken constantly, how much expanded is worth is a preference set once. The shortcuts list
+is subtracted from the transcript rather than added above it, so opening it never changes the
+window's total height — which matters on the Scheduler, where that height is a fixed share of a
+panel that clips.

 The Scheduler panel was exactly that until it was folded in, and it proved the cost: a thread
 there died on reload while the other two were saved, and its bar had drifted into a different