v1.0.0 – Runtime Core Stabilization

This release establishes the stable runtime core of EdgeNetSwitch.

EdgeNetSwitch v1.0.0 focuses on the user-space daemon architecture that forms the foundation of an embedded Linux edge device. The goal of this milestone is not feature completeness, but correctness, testability, and architectural clarity before introducing hardware, networking, or Yocto integration.

What’s included

• Long-lived, signal-aware daemon with deterministic tick loop
• Thread-safe Logger with JSON-configured levels and outputs
• In-process MessagingBus (pub/sub) with fan-out delivery
• JSON ConfigLoader with robust defaults and error handling
• Telemetry subsystem publishing uptime and tick counters
• Heartbeat-based HealthMonitor with transition-only publishing
• Lifecycle events (SystemStart, SystemShutdown)
• Full Catch2 unit test coverage for all core components

What’s intentionally deferred

• Yocto image and BSP integration
• QEMU device bring-up and boot automation
• Networking stack and switching logic
• Industrial protocols (PROFINET, EtherCAT, etc.)
• Kernel drivers and hardware-specific optimizations

These areas are deferred by design to keep v1.0 focused on a clean, verifiable runtime core.

Why v1.0

v1.0.0 marks the point where the runtime architecture is stable, observable, and test-locked. The messaging model, lifecycle hooks, telemetry, and health monitoring semantics are considered production-quality foundations that future layers can build on without structural rewrites.

Next steps

• Yocto-based root filesystem integration
• QEMU-based device simulation
• Networking and control-plane extensions
• User-space ↔ kernel interaction experiments

Full Changelog: https://github.com/togunchan/EdgeNetSwitch/commits/v1.0.0