Say there is one chat component, in the places that claimed otherwise

Several headers argued the Scheduler dock was deliberately separate, and the Scheduler's help
never mentioned the assistant at all — including the fix flow that just changed shape.

Plugin/unraid/pages/readme/scheduler-readme.md

@@ -80,6 +80,42 @@ Two blocks on the Scheduler Info panel get you there faster:
 The status dot in the Orch tree is green, orange or red for the last run's outcome, dim if the
 script has never run. Hover for detail.
 
+## Asking the assistant about what is on screen
+
+The panel below the right-hand views is the same chat component the AI tab and the Monitor
+dashboard use, at this panel's size. What is particular to this tab is that its subject follows
+you: open a log, a conf or a script and the chip states both the profile answering and the thing
+it is pointed at. Nothing is inferred silently — if what the chip says is wrong, that costs a
+glance rather than a confidently wrong answer.
+
+Every row in **Recent Activity** carries a **why?** (failed) or **recap** (clean) button. It opens
+that script's log first and then asks, because the question is only worth asking with the log
+attached — the profile that reads it is the one that gets the log tail. The question is posted as
+visible text, so what was asked on your behalf is never a mystery.
+
+Moving to a different subject keeps the transcript on screen but stops sending the earlier turns
+to the model, and starts a new stored conversation. A troubleshooting thread carrying log excerpts
+must not bleed into a question about a conf key; hiding that the earlier exchange happened would
+be worse than carrying it visibly.
+
+Reasoning is enabled only for Troubleshoot. Working out what a log means is worth waiting for; a
+lookup like "what does this setting do" is not, and an inline answer that stalls reads as broken.
+
+## Recording what actually fixed something
+
+When a diagnosis is followed by that same script running clean, the assistant offers to record it:
+*"`<script>` just ran clean. Want me to record what fixed it?"* Answer **Yes** and the next thing
+you type is stored as the fix rather than asked as a question.
+
+The trigger is the run record, not the conversation. It fires once, at the moment the trouble is
+demonstrably over, rather than after every answer — an offer that appears constantly is one you
+learn to skip past.
+
+What gets stored is the symptom you asked about and the fix you describe. The model's diagnosis is
+deliberately not stored: it is a reading of evidence, and writing a hypothesis into institutional
+memory as settled fact is how a wrong answer outlives the incident it came from. What is
+remembered is what actually worked, and it is shown the next time the same thing is diagnosed.
+
 ## Stopping a script that is stuck
 
 **Stop** sends SIGTERM, waits 3 seconds, then SIGKILL, and clears any lock files the script left
@@ -138,6 +174,11 @@ on disk is never touched until you press Save.
 | **Auto Scroll** | Toolbar | Follows the newest line; pauses if you scroll up |
 | **Cancel** | Toolbar, editing | Discards changes and returns here. The file is untouched until 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 |
+| **New** | Assistant | Starts a fresh conversation; the old one stays in the store |
 
 ## Reference — orchestrator and step behaviour