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/include/ai_profiles.php

@@ -2,7 +2,8 @@
 // ═══════════════════════════════════════════════════════════════════════════════════════════════
 // PURPOSE
 //   The one definition of what an AI profile is. Every consumer — the endpoint, the worker, the
-//   shared chat include, the Scheduler dock — reads it from here instead of restating it.
+//   shared chat include and every page that renders it — reads it from here instead of
+//   restating it.
 //
 // WHY THIS EXISTS
 //   A profile used to be defined in five places: history depth in api/ai.php, capabilities in
@@ -187,9 +188,9 @@ function vv_ai_profiles_client(): array {
 // surfaces ask for it. Emitted as its own tag so any script block that consumes it stays pure
 // JavaScript and remains syntax-checkable outside PHP.
 //
-// Both the shared chat include and the Scheduler dock call this. Before it existed the dock had
-// its own literal `{ code: 'Code', troubleshoot: 'Troubleshoot' }` map, which is how a fourth
-// copy of the profile list came to exist in the first place.
+// The shared chat include calls this, as does any page emitting the registry ahead of it. Before
+// it existed the Scheduler had its own literal `{ code: 'Code', troubleshoot: 'Troubleshoot' }`
+// map, which is how a fourth copy of the profile list came to exist in the first place.
 function vv_ai_profiles_script(): void {
     static $done = false;
     if ($done) return;