Summary

Create C++20 module files for kcenon.monitoring as part of the Tier 3 libraries migration effort.

• Add C++20 module structure with three partitions:
  • kcenon.monitoring.core: Core types, interfaces, concepts, and utilities
  • kcenon.monitoring.collectors: Metric collector implementations and registry
  • kcenon.monitoring.adaptive: Adaptive monitoring, alerts, and load-based adaptation
• Add primary module interface kcenon.monitoring
• Update CMakeLists.txt with module support (opt-in via MONITORING_ENABLE_MODULES)
• Document changes in CHANGELOG (English and Korean)

Related Issues

Closes #310

Part of C++20 Module Migration Epic (common_system#256)

Module Structure

src/modules/
├── monitoring.cppm      # Primary module interface
├── core.cppm            # Core partition
├── collectors.cppm      # Collectors partition
└── adaptive.cppm        # Adaptive partition

CMake Configuration

# Enable C++20 modules (requires CMake 3.28+)
cmake -DMONITORING_ENABLE_MODULES=ON ..

# Use the module library
target_link_libraries(my_app PRIVATE monitoring_system_modules)

Usage Example

import kcenon.monitoring;

using namespace kcenon::monitoring;

// Use core types
metric_sample sample("cpu_usage", 75.5);

// Use collectors
auto& registry = collector_registry::instance();
auto metrics = registry.collect_all();

// Use adaptive monitoring
auto& controller = global_adaptive_controller();
controller.adapt_all(load_metrics);

Prerequisites Status

• [REFACTOR] Consolidate buffering layer - C++20 Module preparation #309 - Consolidate buffering layer (COMPLETED)
• common_system#269 - common_system module (Tier 0) - Blocked
• thread_system#371 - thread_system module (Tier 1) - Blocked
• logger_system#275 - logger_system module (Tier 2, optional) - Blocked

Note: The module files are ready but dependent module imports are commented out until Tier 0/1/2 modules are available.

Test Plan

• Verify header-based build still works (default)
• Verify module build works with CMake 3.28+ and compatible compiler
• Run existing test suite to ensure no regressions
• Test module import syntax with supported compilers

Breaking Changes

None. Module support is opt-in and header-based builds remain the default.