<script type="text/javascript" src="${fe:url('/js/jquery-3.7.1.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/clipboard.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/popper.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/bootstrap.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/suggestor.js')}"></script>

	<script type="text/javascript" src="${fe:url('/js/jquery-3.7.1.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/clipboard.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/popper.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/bootstrap.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/suggestor.js')}"></script>

* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown
# ADR-000X - Title

## Status

name: 'Close stale PRs'
on:
  schedule:
    # Execute every hour at xx:05 to avoid conflicts with other workflows
    - cron: '5 * * * *'

permissions: {}

jobs:
  stale:
    permissions:
      pull-requests: write

    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@v10
        with:
          operations-per-run: 50
          ascending: true
          exempt-all-milestones: true

    protected long currentEndRecordNumber;

    /** List of page numbers for pagination navigation. */
    protected List<String> pageNumberList;

    /** Flag indicating whether the results are partial due to timeout or other issues. */
    protected boolean partialResults;

    /** The actual search query executed against the search engine. */
    protected String searchQuery;

    /** Time taken to execute the search query in milliseconds. */

    }

    // ========== Thread Safety Tests ==========

    /**
     * Test that the volatile alive field is visible across threads.
     * One thread sets alive to false, other threads should see the change immediately.
     */
    @Test
    public void test_aliveField_volatileVisibility() throws Exception {
        // Ensure alive starts as true
        assertTrue(dataStore.alive);

		</div>
	</div>
	<input type="hidden" id="contextPath" value="${contextPath}" />
	<script type="text/javascript" src="${fe:url('/js/admin/jquery-3.7.1.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/admin/popper.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/admin/bootstrap.min.js')}"></script>
	<script type="text/javascript" src="${fe:url('/js/login.js')}"></script>
</body>

	</component>
	<component name="queryStringBuilder" class="org.codelibs.fess.util.QueryStringBuilder" instance="prototype">
	</component>
	<component name="queryParser" class="org.codelibs.fess.query.parser.QueryParser">
	</component>

        final IllegalArgumentException rootCause = new IllegalArgumentException("Invalid character in query");
        final IllegalStateException middleCause = new IllegalStateException("Query parser state error", rootCause);
        final String message = "Query processing failed";
        final VaMessenger<FessMessages> messageCode = messages -> messages.addErrorsInvalidQueryUnknown(UserMessages.GLOBAL_PROPERTY_KEY);

 *
 * This exception is used to indicate various SSO authentication failures
 * including configuration errors, authentication token validation failures,
 * communication issues with SSO providers, and other SSO-related problems.
 */
public class SsoLoginException extends FessSystemException {

    /** Serial version UID for serialization compatibility. */
    private static final long serialVersionUID = 1L;

    /**