├── 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)

            }
        }
        return prs
            .filter { it.milestone?.title?.startsWith(milestone.get()) == true }
            // Filter out the ghost user that replaces deleted users
            .filter { it.user.login != "ghost" }
            .map { it.user.login }
            .toSet()
            .map { getUserInfo(it) }
            .toSet()
    }

    private

- [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective.
- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
- [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
- [ ] Ensure that tests pass sanity check: `./gradlew sanityCheck`.

import org.codelibs.fess.exception.CommandExecutionException;
import org.codelibs.fess.opensearch.user.exentity.User;

/**
 * Authentication chain implementation that executes external commands for user operations.
 * Provides user management through command-line tool execution for password changes and user deletion.
 */
public class CommandChain implements AuthenticationChain {

        TestRefreshableFessUser user = new TestRefreshableFessUser("testuser", true);
        assertTrue(user.refresh());
        assertEquals(1, user.getRefreshCount());

        // Test multiple refreshes
        user.refresh();
        user.refresh();
        assertEquals(3, user.getRefreshCount());

        // Test custom implementation that returns false
        user = new TestRefreshableFessUser("testuser", false);

import jakarta.validation.constraints.Size;

/**
 * Form class for editing user roles in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing role entries,
 * including tracking information for optimistic locking and audit trails.
 * Roles define permissions and access levels for users within the system.
 *
 */
public class EditForm extends CreateForm {

    /**

        return OptionalEntity.empty();
    }

    /**
     * Returns the user entity based on the provided form data, applying any necessary transformations.
     *
     * @param form the form containing user data for retrieval and update
     * @return optional user entity populated from the form
     */
    public static OptionalEntity<User> getUser(final CreateForm form) {
        return getEntity(form).map(entity -> {

        assertEquals("file:/home/user", wizardAction.convertCrawlingPath("/home/user"));
        assertEquals("file:/var/log/app.log", wizardAction.convertCrawlingPath("/var/log/app.log"));
    }

    @Test
    public void test_convertCrawlingPath_windows_path() {
        assertEquals("file:/C:/Users/test", wizardAction.convertCrawlingPath("C:\\Users\\test"));

					</p>
				</a>
				<ul class="nav nav-treeview">
					<c:if test="${fe:permission('admin-user-view')}">
					<li class="nav-item">
						<a href="${fe:url('/admin/user/')}" class="nav-link <c:if test="${param.menuType=='user'}">active</c:if>" <c:if test="${param.menuType=='user'}">aria-current="page"</c:if>>
							<i class='fa fa-user nav-icon' aria-hidden="true"></i>
							<p><la:message key="labels.menu_user" /></p>

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