}
        });
    }

    private void importBulk(final String fileName, final File tempFile) {
        if (logger.isDebugEnabled()) {
            logger.debug("Bulk data import started: fileName={}", fileName);
        }

        final ObjectMapper mapper = new ObjectMapper();
        final AtomicBoolean resetJobs = new AtomicBoolean(false);

        searchRequestParamsRewriters[searchRequestParamsRewriters.length - 1] = rewriter;
    }

    /**
     * Stores current search parameters in a browser cookie for later retrieval.
     *
     * This method serializes the current request parameters, compresses them using GZIP,
     * encodes them with Base64, and stores them in a secure HTTP cookie.
     */
    public void storeSearchParameters() {

    /**
     * Called when a processing phase starts.
     *
     * @param phase the phase name (e.g., "intent", "search", "evaluate", "fetch", "answer")
     * @param message a human-readable message describing what's happening
     */
    void onPhaseStart(String phase, String message);

    /**
     * Called when a processing phase starts with additional context data.
     *

# 
# Example:
# map:{
#     ; PURCHASE     = SEQ_PURCHASE
#     ; MEMBER       = SEQ_MEMBER
#     ; MEMBER_LOGIN = SEQ_MEMBER_LOGIN
#     ; PRODUCT      = SEQ_PRODUCT
# }
#
# *The line that starts with '#' means comment-out.
#
map:{
    #; PURCHASE     = SEQ_PURCHASE
    #; MEMBER       = SEQ_MEMBER
    #; MEMBER_LOGIN = SEQ_MEMBER_LOGIN
    #; PRODUCT      = SEQ_PRODUCT
}

These properties CAN be supplemented with command-line options and they SHOULD follow the shared naming scheme described above.

Examples of properties in this category:

* `org.gradle.caching`
* `org.gradle.configuration-cache`

## Consequences

* Internal properties must start with `org.gradle.internal.`
* Properties of pre-incubation features must start with `org.gradle.experimental.`

- Tooling API client. This a library that is embedded into applications, such as IDEs or CI agents, that allows them to act as a Gradle client.
- Worker processes. Long-running daemon processes that the Gradle daemon starts to run specific kinds of work, such as compilation or test execution.

The diagram below shows the relationships between the different processes:

```mermaid
    graph LR
        
        gradle["Gradle CLI client"]

name: Cleanup stale performance test data

on:
  schedule:
    - cron: '0 4 * * 1'  # Run every Monday at 4:00 AM UTC
  workflow_dispatch:

permissions:
  contents: read
  id-token: write

jobs:
  cleanup-stale-performance-data:
    runs-on: ubuntu-latest

    if: github.repository == 'gradle/gradle'

    steps:
      - name: Checkout repository
        uses: actions/checkout@v6
      

# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

version: 2
updates:
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

description = "Provides a set of plugins that are shared between the Gradle and build-logic builds"

tasks.register("check") {
    dependsOn(subprojects.map { "${it.name}:check" })

        val result = mutableMapOf<TestCoverage, List<SmallSubprojectBucket>>()
        for (stage in model.stages) {
            for (testCoverage in stage.functionalTests) {
                if (testCoverage.testType !in
                    listOf(TestType.ALL_VERSIONS_CROSS_VERSION, TestType.QUICK_FEEDBACK_CROSS_VERSION, TestType.SOAK)
                ) {