What

Tracking epic for Phase 2 of vcpkg deployment readiness across all 8 ecosystem packages. A comprehensive audit revealed structural issues in vcpkg manifests and CMake export naming that could cause build failures or confusion for consumers.

• Current: network_system classifies required kcenon dependencies as optional feature; export naming conventions (targets file name, CMake namespace) are inconsistent across the 8 systems
• Expected: All required dependencies are in top-level dependencies; export naming follows a single convention ecosystem-wide
• Scope: vcpkg.json dependency classification (network_system), CMake install(EXPORT) naming convention (all systems)

Why

• network_system: kcenon-common-system and kcenon-thread-system are required at build time (CMakeLists.txt uses find_package(common_system REQUIRED)), but vcpkg.json places them under the optional ecosystem feature. If a consumer installs kcenon-network-system without [ecosystem], the build will fail because these dependencies won't be resolved
• Naming inconsistency: Consumer projects must guess between find_package(thread_system) + thread_system::thread_base vs find_package(ThreadSystem) + ThreadSystem::thread_base. This friction slows adoption and creates integration bugs

Export Naming Current State

Where

How

Sub-Issues

Phase 2a: Dependency Classification Fix

• kcenon/network_system#TBD — fix(vcpkg): Move required kcenon dependencies from ecosystem feature to top-level dependencies

Phase 2b: Export Naming Standardization

• kcenon/common_system#TBD — chore(cmake): Standardize ecosystem export naming convention

Acceptance Criteria

• network_system vcpkg.json lists kcenon-common-system and kcenon-thread-system in top-level dependencies
• All 8 systems use consistent export file naming pattern
• All 8 systems use consistent CMake namespace pattern
• Consumer project can find_package() all 8 systems using a predictable naming convention