What problems was I solving

NamingUtils in api-builder's OpenAPI platform layer contained 14 helper methods and types that were written but never called, creating noise and slowing future refactors of the naming logic.

What user-facing changes did I ship

There are no user-facing changes. This is an internal code-quality cleanup that does not alter generated OpenAPI output or any public contracts.

How I implemented it

Deleted the unused ComponentOccurrence, NamingContext, extractActions, extractResourceFromPath, extractResourceWords, generateSemanticName, makePlural, makeSingular, resolveNamingConflicts, toCamelCase, and the generateParameterName/generateRequestName/generateResponseName/generateSchemaName family from NamingUtils. The two remaining helpers — generateComponentNameFromUsage and toPascalCase — are the only ones imported by the OpenAPI extractor modules, so all existing callers continue to work unchanged.

Description for the changelog

Removed 14 unused symbols from NamingUtils in the OpenAPI naming utility module, leaving only the generateComponentNameFromUsage and toPascalCase helpers currently referenced by the extractor modules. This internal cleanup eliminates dead code introduced with no callers and does not change any generated output or public API surface.