"kadar", "karşın", "katrilyon", "kendi", "kendilerine", "kendini", "kendisi", "kendisine", "kendisini", "kez", "ki", "kim", "kimden", "kime", "kimi", "kimse", "kırk", "milyar", "milyon", "mu", "mü", "mı", "nasıl", "ne", "neden", "nedenle", "nerde", "nerede", "nereye", "niye", "niçin", "o", "olan", "olarak", "oldu", "olduğu", "olduğunu", "olduklarını", "olmadı", "olmadığı", "olmak", "olması", "olmayan", "olmaz", "olsa", "olsun", "olup", "olur", "olursa", "oluyor", "on", "ona", "ondan", "onlar", "onlardan",...

"kadar", "karşın", "katrilyon", "kendi", "kendilerine", "kendini", "kendisi", "kendisine", "kendisini", "kez", "ki", "kim", "kimden", "kime", "kimi", "kimse", "kırk", "milyar", "milyon", "mu", "mü", "mı", "nasıl", "ne", "neden", "nedenle", "nerde", "nerede", "nereye", "niye", "niçin", "o", "olan", "olarak", "oldu", "olduğu", "olduğunu", "olduklarını", "olmadı", "olmadığı", "olmak", "olması", "olmayan", "olmaz", "olsa", "olsun", "olup", "olur", "olursa", "oluyor", "on", "ona", "ondan", "onlar", "onlardan",...

However, if there are no changes for more than a week, it's safe to assume that the issue is up for grabs.
There is no need to ask for an assignment or for permission to work on those issues, just comment and start working on it.

## Setting up your development environment

In order to make changes to Gradle, you'll need:

* It is ok for Serializer to be used as a replacement for Java serialization as a migration step.

However, this does not fully remove the prerequisite, as the Wrapper itself would still need an installed Java runtime to execute.

Gradle needs a solution that covers the use-case of starting the Wrapper itself as well given its importance.

### Running Gradle on multiple Java versions

        // The process method needs actual ThumbnailQueueBhv and other components
        assertTrue(true);
    }

    // Test process with unavailable generator
    @Test
    public void test_process_unavailableGenerator() {
        // Skip this test as it requires container components
        // The process method needs actual ThumbnailQueueBhv and other components
        assertTrue(true);

## Consequences

* We are incurring debt that will need to be paid later via deprecations or breaking changes to existing classes. The implementation for some Gradle types will be more complicated than an equivalent clean-sheet implementation.
* During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.

        session.addAssistantMessage("Assistant 2");
        session.addUserMessage("User 3");
        session.addAssistantMessage("Assistant 3");

        // Trimming to 4 starts at index 2 which is user - no skip needed
        session.trimHistory(4);

        final List<ChatMessage> messages = session.getMessages();
        assertEquals(4, messages.size());
        assertEquals(ChatMessage.ROLE_USER, messages.get(0).getRole());

Doing this provides the following specific benefits:
- **Reduce the API surface** - We no longer need to maintain two methods.
- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

                logger.debug("Cannot add message, session not found. sessionId={}", sessionId);
            }
            return false;
        }
        session.addMessage(message);

        // Trim history if needed
        final int maxMessages = getMaxHistoryMessages();
        session.trimHistory(maxMessages);

        if (logger.isDebugEnabled()) {