}

    /**
     * Creates a FAQ intent result with a Fess query.
     *
     * @param query the Fess query string
     * @param reasoning the detection reasoning
     * @return the FAQ intent result
     */
    public static IntentDetectionResult faq(final String query, final String reasoning) {
        return new IntentDetectionResult(ChatIntent.FAQ, query, null, reasoning);
    }

    /**

    }

    @Test
    public void test_fromValue_faq() {
        assertEquals(ChatIntent.FAQ, ChatIntent.fromValue("faq"));
        assertEquals(ChatIntent.FAQ, ChatIntent.fromValue("FAQ"));
        assertEquals(ChatIntent.FAQ, ChatIntent.fromValue("Faq"));
    }

    @Test
    public void test_fromValue_unclear() {
        assertEquals(ChatIntent.UNCLEAR, ChatIntent.fromValue("unclear"));

    /** User wants to search for documents in Fess */
    SEARCH("search"),

    /** User wants a summary of a specific document */
    SUMMARY("summary"),

    /** User is asking a FAQ-type question */
    FAQ("faq"),

    /** Intent is unclear - need to ask user for clarification */
    UNCLEAR("unclear");

    private final String value;

    ChatIntent(final String value) {
        this.value = value;

            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

            throw new LlmException("summarySystemPrompt is not configured for " + getName());
        }
        return summarySystemPrompt;
    }

    /**
     * Gets the system prompt for FAQ answer generation.
     *
     * @return the FAQ answer system prompt
     */
    protected String getFaqAnswerSystemPrompt() {
        if (faqAnswerSystemPrompt == null) {

This can be quite noticeable when using `docker compose`. See this Docker Compose FAQ section for more technical details: [Why do my services take 10 seconds to recreate or stop?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop).

#### Directory Structure { #directory-structure }

You should now have a directory structure like:

이는 `docker compose`를 사용할 때 꽤 눈에 띌 수 있습니다. 좀 더 기술적인 상세 내용은 Docker Compose FAQ 섹션을 참고하세요: [Why do my services take 10 seconds to recreate or stop?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop).

#### 디렉터리 구조 { #directory-structure }

이제 다음과 같은 디렉터리 구조가 되어야 합니다:

```
.
├── app

詳しくは、[shell形式とexec形式に関するDockerドキュメント](https://docs.docker.com/reference/dockerfile/#shell-and-exec-form)をご覧ください。

これは `docker compose` を使用する場合にかなり目立つことがあります。より技術的な詳細は、このDocker ComposeのFAQセクションをご覧ください：[Why do my services take 10 seconds to recreate or stop?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop)。

#### ディレクトリ構造 { #directory-structure }

これで、次のようなディレクトリ構造になるはずです：

```
.
├── app

你可以在 [Docker 關於 shell 與 exec 形式的文件](https://docs.docker.com/reference/dockerfile/#shell-and-exec-form) 閱讀更多。

使用 `docker compose` 時這會特別明顯。技術細節請見這段 Docker Compose 常見問題：[為什麼我的服務要花 10 秒才重新建立或停止？](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop)

#### 目錄結構 { #directory-structure }

你現在應該會有如下的目錄結構：

```
.
├── app
│   ├── __init__.py
│   └── main.py
├── Dockerfile

Cela peut être très visible lors de l'utilisation de `docker compose`. Voir cette section de la FAQ Docker Compose pour plus de détails techniques : [Pourquoi mes services mettent-ils 10 secondes à se recréer ou à s'arrêter ?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop).

#### Structure du répertoire { #directory-structure }