* Keep commits discrete. Avoid including multiple unrelated changes in a single commit.
* Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation.

### Testing changes

After making changes, you can test your code in 2 ways:

#### Run tests

        assertNotNull(defaultGroups, "Default groups should not be null");
        assertNotNull(defaultRoles, "Default roles should not be null");
    }

    /**
     * Test list isolation during concurrent updates.
     */
    @Test
    public void test_listIsolation_duringConcurrentUpdates() throws Exception {
        List<String> originalGroups = new ArrayList<>();

 *   <li>Selective crawling based on configuration IDs</li>
 *   <li>Document expiration handling</li>
 *   <li>Hot thread monitoring for performance analysis</li>
 *   <li>Process isolation with separate JVM</li>
 * </ul>
 */
public class CrawlJob extends ExecJob {

    private static final Logger logger = LogManager.getLogger(CrawlJob.class);

    /**

            <option value="$PROJECT_DIR$/platforms/core-configuration/flow-services" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/graph-isolation" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/graph-serialization" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/guava-serialization-codecs" />

        // Create a completely isolated context to avoid handle reuse issues on Linux Docker
        try {
            // Create a new context with fresh configuration each time
            // This ensures complete isolation between operations
            Properties props = new Properties();
            props.setProperty("jcifs.smb.client.minVersion", "SMB202");
            props.setProperty("jcifs.smb.client.maxVersion", "SMB311");

              <!-- TODO(cpovirk): Enable NullArgumentForNonNullParameter for
                   prod code. It's disabled automatically for "test code"
                   (which is good: our tests have intentional violations), but
                   Error Prone doesn't know it's building test code unless we
                   pass -XepCompilingTestOnlyCode, and that argument needs to

h3. Plugins need a specific metadata model

        assertEquals(25, groovyEngine.evaluate("return x * 5", params));
        assertEquals(10, groovyEngine.evaluate("return x * 2", params));
    }

    /**
     * Test that cached scripts maintain binding isolation between evaluations
     */
    @Test
    public void test_evaluate_cacheBindingIsolation() {
        final Map<String, Object> params1 = new HashMap<>();
        params1.put("name", "Alice");

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library

            closeableContext.close();
            closeableContext.close(); // Second call
            closeableContext.close(); // Third call
        });
    }

    @Test
    @DisplayName("Should maintain key isolation between instances")
    void testKeyIsolationBetweenInstances() {
        // Given
        byte[] key1 = new byte[16];
        byte[] key2 = new byte[16];
        new SecureRandom().nextBytes(key1);