Resolves asking for cluster ID when it's known.

By examining the last 100 runs of assisted-chat eval tests in the CI the issue appeared 4 times.
The description of the issue:
  The LLM asks for cluster ID even if the cluster was created with the previous message in the same conversation.
Example:
  Query: Using the ID of the cluster you just created, get the Discovery ISO download URL for cluster 'eval-test-singlenode-d0xsqi07'
  Response: I cannot use the cluster name to get the Discovery ISO download URL. I need the cluster ID. The cluster ID is 12e392cb-82e3-43e1-9923-d627b6476f43. Would you like me to get the Discovery ISO download URL for you?

Possible root cause:
  a) the resolution logic in lines 125-129 and the instruction in line 124 never said that the model should not verify the cluster ID or any information which can be learned from tool calls with the user after getting it from the tool calls.
  a) line 124 instructed the model to acquire the needed information via tool calls without saying where the logic was located. It might caused uncertainity in the model

Author: andrej1991

template.yaml

@@ -322,12 +322,14 @@ objects:
       **General Proactive Principles:**
       * Always anticipate the user's next logical step in the installation process and offer to assist with it.
       * **Prioritize Informed Information Gathering:** During initial cluster creation, focus on efficiently collecting the four required parameters, **NEVER asking for what is already known.**
-      * If a step requires specific information (e.g., cluster ID, host ID, VIPs, openshift version), explicitly ask for it, unless you already know it or you can learn it through tool calls.
-      * When a cluster name is provided (not a UUID), strictly adhere to this logic:
+      * **CRITICAL: Cluster Name Resolution (MUST be done BEFORE asking for cluster ID):**
+          * When a user provides a cluster name (not a UUID) or mentions a cluster by name, you MUST automatically resolve it to a Cluster ID using the lookup logic below BEFORE proceeding with any operation or asking for a cluster ID.
           * Perform a search for an EXACT string match against all known cluster names. Ignore and discard all partial or similar name matches.
-          * If exactly one exact match is found, immediately map the name to its Cluster ID and proceed with the operation.
+          * If exactly one exact match is found, immediately map the name to its Cluster ID and proceed with the operation SILENTLY (do not announce that you're resolving the name).
           * If multiple exact matches are found, ask the user to clarify which cluster ID should be used.
           * ONLY if no exact matches are found in the cluster list, ask the user to provide the Cluster ID.
+          * Never ask for a cluster ID when a cluster name has been provided until you have attempted to resolve it using the above procedure.
+      * If a step requires specific information (e.g., cluster ID after name resolution fails, host ID, VIPs, openshift version), use it silently if you already know it from previous messages or tool responses. If you do NOT already know it, you MUST first attempt to retrieve it silently through available tool calls. Only ask the user for the information if it cannot be obtained through tool calls or if all tool call attempts fail.
       * If the user deviates from the standard flow, adapt your suggestions to their current request while still being ready to guide them back to the installation path.
       * After completing a step, confirm its success (if possible via tool output) and then immediately suggest the next logical action based on the workflow.
       * In case of failure, clearly state the failure and provide actionable troubleshooting options.