Part of #455

What

Standardize CMake install(EXPORT) target file names and namespace prefixes across all 8 ecosystem systems. Some systems have already adopted snake_case at the portfile level (kcenon/network_system#843, kcenon/monitoring_system#562), but the source-level export names remain inconsistent.

• Current: Mixed conventions for export files and namespaces (see matrix below)
• Expected: All systems use <name>-targets.cmake (snake_case + hyphen) and <name>:: (snake_case) namespace
• Scope: CMakeLists.txt and cmake/*Install*.cmake across all 8 systems

Current State Matrix

Proposed Standard

Why

• Consumer projects must currently guess the correct namespace for each system: is it kcenon::common_system or kcenon::common? Is it ThreadSystem::thread_base or thread_system::thread_base?
• thread_system exports two namespace aliases, creating ambiguity
• Some portfiles already have snake_case wrappers (feat(cmake): adopt snake_case install(EXPORT) name for vcpkg compatibility network_system#843, chore(vcpkg-ports): Migrate portfile PACKAGE_NAME to snake_case (remove PascalCase wrappers) monitoring_system#562), meaning the portfile and source code are now misaligned in the opposite direction
• Inconsistency increases friction for new consumers and makes cross-system integration fragile

Where

How

Technical Approach

Each system needs:

1. Change install(EXPORT ...) to use <name>-targets (snake_case + hyphen)
2. Change NAMESPACE to <name>:: (snake_case)
3. Update *Config.cmake.in to include("${CMAKE_CURRENT_LIST_DIR}/<name>-targets.cmake")
4. Update overlay portfile if it has PascalCase wrapper workarounds (remove wrappers)

Phase Plan

Acceptance Criteria

• All 8 systems use <name>-targets.cmake export file pattern
• All 8 systems use <name>:: snake_case namespace
• No PascalCase wrapper files in overlay ports
• Consumer project can find_package() + target_link_libraries() using a predictable, consistent pattern across all 8 systems
• Config templates reference correct targets file names