User user1 = createTestUser("user1", "User One");
        User user2 = createTestUser("user2", "User Two");
        User user3 = createTestUser("user3", "User Three");

        chain.update(user1);
        chain.update(user2);
        chain.update(user3);

        assertEquals(3, chain.updateCalls.size());
        assertEquals(user1, chain.updateCalls.get(0));

        assertFalse(exception1.getMessage().equals(exception2.getMessage()));
        assertEquals("User is not found: user1", exception1.getMessage());
        assertEquals("User is not found: user2", exception2.getMessage());
    }

        assertEquals("user1", resultList.get(0).get("name"));
    }

    @Test
    public void test_register_collectionPerformanceOptimization() {
        RenderData data = new RenderData();

        BsUser entity1 = new BsUser();
        entity1.setName("user1");
        BsUser entity2 = new BsUser();
        entity2.setName("user2");

        // Test with different names
        LdapUser user2 = new LdapUser(testEnv, "anotheruser");
        assertEquals("anotheruser", user2.getName());

        // Test with empty name
        LdapUser user3 = new LdapUser(testEnv, "");
        assertEquals("", user3.getName());

        // Test with null name
        LdapUser user4 = new LdapUser(testEnv, null);
        assertNull(user4.getName());
    }

    @Test

     * When enabled, user search queries are logged for analysis.
     */
    @Size(max = 10)
    public String searchLog;

    /**
     * Enable or disable user information tracking.
     * When enabled, user information is stored and tracked.
     */
    @Size(max = 10)
    public String userInfo;

    /**
     * Enable or disable user favorite functionality.

Although properties offer the benefit of precise user-side control and support gradual evolution practices, the high number of properties also presents challenges.

The main challenge on the user side is comprehensibility.
With that many properties, and considering the tendency for properties to accrete in user builds over time, it is important for users to understand the contracts tied to the features.

├── opensearch/                # DBFlute integration for OpenSearch
│   ├── config/                # Config index (crawl configs, schedules)
│   ├── log/                   # Log index (search logs, click logs)
│   └── user/                  # User index (users, groups, roles)
├── helper/                    # Cross-cutting utilities (~40+ helpers)
├── crawler/                   # Crawling engine (processor, transformer, service)

Inconsistency in spelling conventions can lead to several issues:

* **Confusion for users and contributors**: Mixed spellings (e.g., "color" and "colour", "initialize" and "initialise") in the codebase create confusion about which variant to use

     * to avoid login delays when users have many nested group memberships.
     * @param user The Entra ID user to update.
     */
    public void updateMemberOf(final EntraIdUser user) {
        if (logger.isDebugEnabled()) {
            logger.debug("[updateMemberOf] Starting for user: {}", user.getName());
        }

        final List<String> groupList = new ArrayList<>();

        if (cleanupTask != null && !cleanupTask.isCanceled()) {
            cleanupTask.cancel();
        }
    }

    /**
     * Creates a new chat session.
     *
     * @param userId the user ID (can be null for anonymous users)
     * @return the created session
     */
    public ChatSession createSession(final String userId) {
        final ChatSession session = new ChatSession(userId);