/** Phase name for content retrieval */
    String PHASE_FETCH = "fetch";

    /** Phase name for answer generation */
    String PHASE_ANSWER = "answer";

    /**
     * Called when a processing phase starts.
     *
     * @param phase the phase name (e.g., "intent", "search", "evaluate", "fetch", "answer")
     * @param message a human-readable message describing what's happening
     */

            LlmStreamCallback callback);

    /**
     * Generates an FAQ answer using document content (streaming).
     * Uses a prompt optimized for direct, concise FAQ-style answers.
     *
     * @param userMessage the user's message
     * @param documents the documents with content
     * @param history the conversation history

In GitHub, the template will guide you to write the right question so that you can more easily get a good answer, or even solve the problem yourself even before asking. And in GitHub I can make sure I always answer everything, even if it takes some time. I can't personally do that with the chat systems. 😅

    }

    /** Sets the system prompt for FAQ answer generation.
     * @param faqAnswerSystemPrompt the FAQ answer system prompt */
    public void setFaqAnswerSystemPrompt(final String faqAnswerSystemPrompt) {
        this.faqAnswerSystemPrompt = faqAnswerSystemPrompt;
    }

    /** Sets the system prompt for direct answer generation.
     * @param directAnswerSystemPrompt the direct answer system prompt */

#### The time to answer helps the attackers { #the-time-to-answer-helps-the-attackers }

        }
        return getAvailableClient().evaluateResults(userMessage, query, searchResults);
    }

    /**
     * Generates an answer using document content (synchronous).
     *
     * @param userMessage the user's message
     * @param documents the documents with content
     * @param history the conversation history
     * @return the chat response

        assertEquals("search", ChatPhaseCallback.PHASE_SEARCH);
        assertEquals("evaluate", ChatPhaseCallback.PHASE_EVALUATE);
        assertEquals("fetch", ChatPhaseCallback.PHASE_FETCH);
        assertEquals("answer", ChatPhaseCallback.PHASE_ANSWER);
    }

    @Test
    public void test_phaseConstants_notNull() {
        assertNotNull(ChatPhaseCallback.PHASE_INTENT);
        assertNotNull(ChatPhaseCallback.PHASE_SEARCH);

									<span class="step-label"><la:message key="labels.chat_step_fetch" /></span>
								</div>
								<div class="progress-step" data-phase="answer">
									<div class="step-icon"><i class="fa fa-pencil" aria-hidden="true"></i></div>
									<span class="step-label"><la:message key="labels.chat_step_answer" /></span>
								</div>
							</div>

    return Ints.saturatedCast(sum);
  }

  /*
   * We override the toArray methods for two reasons:
   *
   * 1. Both superclass toArray methods assume that size() gives a correct answer, while our size()
   * might not (and the answer might change while we're building the array).
   *
   * TODO: cpovirk - Is this an issue anywhere anymore? It looks to have been fixed for Java 8

									<span class="step-label"><la:message key="labels.chat_step_fetch" /></span>
								</div>
								<div class="progress-step" data-phase="answer">
									<div class="step-icon"><i class="fa fa-pencil" aria-hidden="true"></i></div>
									<span class="step-label"><la:message key="labels.chat_step_answer" /></span>
								</div>
							</div>