name = stage.stageName.stageName + " (Trigger)" + (os?.asName()?.toCapitalized()?.let { "($it)" } ?: "")
        type = Type.COMPOSITE

        applyDefaultSettings()

        features {
            publishBuildStatusToGithub(model)
        }

        if (generateTriggers) {
            val enableTriggers = model.branch.isMainBranch || model.branch.isLegacyRelease

        }

        writeFuturePluginVersions {
            property(plugin.id, version)
        }

        compatibility {
            features {
                configurationCache = true
            }
        }
    }
}

// For local consumption by tests - this should be unified with publish-public-libraries if possible

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".
An architecture module is responsible for providing a coherent set of features and:

- Provides a set of APIs and services for use from outside the module.
- Has a private implementation.
- Is owned by a single team. A team may own multiple architecture modules.

    }
}

fun BaseGradleBuildType.tcParallelTests(numberOfBatches: Int) {
    if (numberOfBatches > 1) {
        params {
            param("env.TEAMCITY_PARALLEL_TESTS_ENABLED", "1")
        }
        features {
            parallelTests {
                this.numberOfBatches = numberOfBatches
            }
        }
    }
}

fun BuildFeatures.publishBuildStatusToGithub() {

 * saml.default.groups=user
 * saml.default.roles=user
 * </pre>
 *
 * <h2>Security Settings (Production)</h2>
 * <p>For production environments, consider enabling these security features:</p>
 * <pre>
 * saml.security.authnrequest_signed=true
 * saml.security.want_messages_signed=true
 * saml.security.want_assertions_signed=true
 * </pre>
 *

     * This method searches for 'fess_ds++.xml' configuration files within JAR files
     * in the data store plugin directory and extracts component class names.
     *
     * <p>The method uses secure XML parsing features to prevent XXE attacks and
     * other XML-based vulnerabilities. Component class names are extracted from
     * the 'class' attribute of 'component' elements in the XML files.</p>
     *

## GitHub docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
##
## CODEOWNERS style rules:
## 1. Prefer team ownership over individual user ownership.
## 2. GBT-related team should be listed first.
## 3. Try to keep paths alphabetically sorted within visual groups.
## 4. List individual owners last.
##

# Build infrastructure

        client.setChatResponse("{\"intent\":\"faq\",\"query\":\"Fess features\",\"reasoning\":\"FAQ question\"}");

        // Call the original single-arg method
        final IntentDetectionResult result = client.detectIntent("What are Fess features?");

        assertEquals(ChatIntent.FAQ, result.getIntent());
        assertEquals("Fess features", result.getQuery());

 * crawling and indexing documents, including incremental crawling capabilities, content
 * modification checking, and integration with the Fess search engine backend.
 *
 * <p>Key features include:</p>
 * <ul>
 * <li>Incremental crawling support with last-modified timestamp checking</li>
 * <li>Document expiration handling</li>
 * <li>Child URL extraction and queueing</li>

 * types of crawlers (web, file, data). It manages the crawler process lifecycle,
 * handles timeout scenarios, and ensures proper cleanup of resources.</p>
 *
 * <p>Key features:</p>
 * <ul>
 *   <li>Concurrent crawler process management with configurable limits</li>
 *   <li>Selective crawling based on configuration IDs</li>
 *   <li>Document expiration handling</li>