Give the AI subsystem one profile table and one collection, read everywhere

Plugin/unraid/Tools/ai_chat_worker.php

@@ -404,6 +404,11 @@ if ($can('conf_lookup')) {
 // Varaverk question as chat produces a confident invention about the user's system, which is
 // precisely what retrieval exists to prevent. The user always knows which contract is in force,
 // and the strict profile is the default.
+//
+// These stay here rather than in include/ai_profiles.php with the rest of what a profile is.
+// That file exists to kill duplication, and these prompts have exactly one reader — moving them
+// would relocate the most delicate text in the subsystem without removing a single copy of
+// anything. The registry owns the ids; the ids branch here. The trailing else is varaverk.
 if ($profile === 'chat') {
     // A polite instruction is not a guard. Asked "what does mover_stop.sh do in my setup", the
     // model invented an answer and dressed it in real memory facts so it read as authoritative.
@@ -652,7 +657,7 @@ $messages[] = ['role' => 'user', 'content' => $question];
 // them, which is why the report prints here: it describes the request that is about to be made,
 // not a reconstruction of one.
 if ($explain) {
-    $caps = array_keys(array_filter(VV_AI_CAPS, fn($ps) => in_array($profile, $ps, true)));
+    $caps = vv_ai_profile_caps($profile);
     $sysChars = strlen($system);
 
     echo "QUESTION   ", $question, "\n";