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
@@ -176,8 +176,10 @@ on disk is never touched until you press Save.
 | **+ Folder** | Custom Scripts | A collapsible subfolder you can drag scripts into |
 | **why? / recap** | Recent Activity | Opens that run's log and asks the assistant about it in one click |
 | **Profile chip** | Assistant | What is answering, and what it is pointed at. Click to change the profile |
-| **⤢** | Assistant | Trades more of the panel for the conversation, and back |
-| **▾** | Assistant | Saved conversations, shared with the AI tab and the Monitor dashboard |
+| **⤢** | Assistant | Expands the conversation into the panel, and collapses it again |
+| **Medium / Large** | Assistant banner | How much of the panel expanding is worth — 20% or 40% |
+| **Shortcuts** | Assistant banner | The keyboard list. Taken out of the transcript, so the panel keeps its height |
+| **Saved** | Assistant | Saved conversations, shared with the AI tab and the Monitor dashboard |
 | **New** | Assistant | Starts a fresh conversation; the old one stays in the store |

 ## Reference — orchestrator and step behaviour
@@ -197,11 +199,18 @@ on disk is never touched until you press Save.
 The right-hand panel is the default view and everything returns to it. **← Scheduler Info** comes
 back here from any log, editor, conf form or script view.

- **Notification board** — how many jobs are scheduled out of the total, and what is running now.
+- **Notification board** — how many orchestrators are scheduled, how many scripts carry a cron of
+  their own, and what is running now. Pinned, so it stays visible while you read the rest.
 - **Next Runs** — what fires next, and when.
 - **Recent Activity** / **Recent Errors** — described above.
 - **Cron Calculator** — described above.

+The board counts **orchestrators**, not scripts. A schedule here is normally one cron on an
+orchestrator that then calls its steps in order, so the steps are deliberately cronless — counting
+them made a fully-scheduled system read as `10 / 82 scheduled`, which is alarming and wrong. Steps
+that *do* carry their own cron are counted separately as standalone, because that is the exception
+and the number of exceptions is the figure worth knowing. It shows only when there are any.
+
 ## Reference — Advanced mode

 The **Advanced** button at the top right turns blue when active. It is a display and editing