assertEquals(ChatIntent.UNCLEAR, ChatIntent.fromValue("unclear"));
        assertEquals(ChatIntent.UNCLEAR, ChatIntent.fromValue("UNCLEAR"));
        assertEquals(ChatIntent.UNCLEAR, ChatIntent.fromValue("Unclear"));
    }

    @Test
    public void test_fromValue_null() {
        // Defaults to UNCLEAR when value is null
        assertEquals(ChatIntent.UNCLEAR, ChatIntent.fromValue(null));
    }

    @Test

    /** 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;
    }

    /**
     * Returns the string value of this intent.
     *

    }

    /**
     * Creates an unclear intent result when intent cannot be determined.
     *
     * @param reasoning the detection reasoning
     * @return the unclear intent result
     */
    public static IntentDetectionResult unclear(final String reasoning) {
        return new IntentDetectionResult(ChatIntent.UNCLEAR, null, null, reasoning);
    }

    /**

    @Test
    public void test_unclear() {
        final IntentDetectionResult result = IntentDetectionResult.unclear("unclear intent");

        assertEquals(ChatIntent.UNCLEAR, result.getIntent());
        assertNull(result.getQuery());
        assertNull(result.getDocumentUrl());
        assertEquals("unclear intent", result.getReasoning());
    }

    @Test
    public void test_unclear_withNullReasoning() {

## Status

- ACCEPTED on 2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

        }
        return intentDetectionPrompt;
    }

    /**
     * Gets the system prompt for unclear intent responses.
     *
     * @return the unclear intent system prompt
     */
    protected String getUnclearIntentSystemPrompt() {
        if (unclearIntentSystemPrompt == null) {

            LlmStreamCallback callback);

    /**
     * Generates a response asking user for clarification when intent is unclear.
     *
     * @param userMessage the user's message
     * @param history the conversation history
     * @param callback the streaming callback
     */

                logger.debug("[RAG] Intent detected. intent={}, query={}", intentResult.getIntent(), intentResult.getQuery());
            }

            if (intentResult.getIntent() == ChatIntent.UNCLEAR) {
                // Unclear intent - generate answer with empty documents to ask for clarification
                final LlmChatResponse llmResponse = llmClientManager.generateAnswer(userMessage, Collections.emptyList(), history);

 *     "Unexpected bill status: %s", bill.status());
 * }
 *
 * <h3>Comparison to alternatives</h3>
 *
 * <p><b>Note:</b> In some cases the differences explained below can be subtle. When it's unclear
 * which approach to use, <b>don't worry</b> too much about it; just pick something that seems
 * reasonable and it will be fine.
 *
 * <ul>

repeats of these filename(s) with different casing:
EOF
    find . | tr '[A-Z]' '[a-z]' | sort | uniq -d | tee $BATS_FILE_TMPDIR/repeats
    [[ ! -s $BATS_FILE_TMPDIR/repeats ]]
}

# It's unclear why, but running this on //tensorflow/... is faster than running
# only on affected targets, usually. There are targets in //tensorflow/lite that
# don't pass --nobuild, so they're on their own.
#