Doing this provides the following specific benefits:
- **Reduce the API surface** - We no longer need to maintain two methods.
- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

* **Inconsistent API surface**: Public APIs with mixed spelling conventions appear less professional and polished
* **Harder for non-native speakers**: Contributors and users for whom English is a second language benefit from a single, consistent convention

While both American and British English are valid, establishing a single standard improves consistency, readability, and maintainability of the codebase.

        assertNotSame(item1.hashCode(), item3.hashCode());

        // Consistent hashCode
        assertEquals(item1.hashCode(), item1.hashCode());
    }

    @Test
    public void test_hashCode_withNullInput() {
        // Test hashCode with null input - should not throw, returns consistent hash for null
        ProtwordsItem item1 = new ProtwordsItem(1, null);

it is unlikely that we'll be able to remove `null` entirely.

After migrating to Java 8, we can use pluggable type checkers to ensure that our annotations are consistent, 
and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

        // Each call should return a new instance
        assertNotSame(option1, option2);
    }

    @Test
    public void test_provideMappingOption_consistency() {
        // Test that multiple calls provide consistent configuration
        JsonMappingOption option1 = provider.provideMappingOption();
        JsonMappingOption option2 = provider.provideMappingOption();

        assertEquals(option1.getFieldNaming(), option2.getFieldNaming());

        assertSame(invertibleCryptographer, first);
    }

    @Test
    public void test_providePrimaryInvertibleCryptographer_consistency() {
        // Test multiple calls return consistent results
        for (int i = 0; i < 10; i++) {
            InvertibleCryptographer cryptographer = securityResourceProvider.providePrimaryInvertibleCryptographer();
            assertNotNull(cryptographer);

        assertNotSame(item1.hashCode(), item4.hashCode());
    }

    @Test
    public void test_hashCode_withNullInput() {
        // Test hashCode with null input - should not throw, returns consistent hash for null
        StopwordsItem item1 = new StopwordsItem(1, null);
        StopwordsItem item2 = new StopwordsItem(2, null);

        // Should not throw
        int hash1 = item1.hashCode();

But now that FastAPI 0.99.0 and above uses OpenAPI 3.1.0, that uses JSON Schema 2020-12, and Swagger UI 5.0.0 and above, everything is more consistent and the examples are included in JSON Schema.

### Swagger UI and OpenAPI-specific `examples` { #swagger-ui-and-openapi-specific-examples }

    }

    @Test
    public void test_hashCode() {
        // Test hashCode consistency
        int metadataHashCode = SsoResponseType.METADATA.hashCode();
        int logoutHashCode = SsoResponseType.LOGOUT.hashCode();

        // Hash code should be consistent for the same object
        assertEquals(metadataHashCode, SsoResponseType.METADATA.hashCode());

        String result = crawlerEngineClient.toString();
        assertNotNull(result);
    }

    // Test hashCode method
    @Test
    public void test_hashCode() {
        // Test that hashCode returns consistent value
        int hashCode1 = crawlerEngineClient.hashCode();
        int hashCode2 = crawlerEngineClient.hashCode();
        assertEquals(hashCode1, hashCode2);
    }

    // Test equals method
    @Test