Comprehensive audit found 40+ naming inconsistencies across resource types, config keys, and YAML tags. Good candidate to fix as part of v1.0.0 since these are breaking changes.

Target conventions:

• Resource types: kebab-case (e.g., iam-role, ecs-cluster)
• Config keys (Go field + YAML tag): PascalCase with uppercase acronyms (e.g., IAMRoles, SESIdentity)

1. Critical bugs

2. Resource types not in kebab-case (concatenated words)

3. Resource types using camelCase or underscores

4. Cryptic / abbreviated resource types

5. YAML tag casing — acronyms should be uppercase

6. Config field casing — acronyms & brand names

7. Redundant / mismatched config names

8. Overly generic resource types

9. Code typo

10. Config field declared but unused at runtime

Preventing regressions

Add a Go test that iterates all registered resources and asserts:

1. Resource types match ^[a-z][a-z0-9]*(-[a-z0-9]+)*$ (strict kebab-case)
2. Config YAML tags match ^[A-Z][A-Za-z0-9]*$ (PascalCase, no lowercase-starting acronyms)
3. Every resource's ConfigGetter returns a unique config field (no two resources sharing one)
4. Every config field in the struct is referenced by exactly one resource

Alternatively, derive config keys automatically from resource types to eliminate ad-hoc mappings entirely.