v1.5.0 — Persistent Telemetry Stabilization

v1.5.0 — Persistent Telemetry Stabilization

This release introduces durable, file-based telemetry export while preserving the deterministic runtime and control-plane semantics established in previous versions.

v1.5 focuses on lifecycle correctness and persistence guarantees without altering runtime execution or protocol contracts.

What’s new in v1.5

Persistent telemetry export
• FileTelemetryExporter writes telemetry samples to telemetry.log
• Append mode (std::ios::app) preserves log contents across restarts
• Integrated into TelemetryExportManager during daemon startup

Lifecycle guarantees
• Deterministic RAII-based teardown
• Destructor acquires lock and guarantees flush() and close()
• Internal std::mutex ensures thread-safe writes and shutdown behavior

Runtime semantics
• Export path remains synchronous within the tick-driven runtime flow
• No asynchronous export introduced in this release

What did NOT change
• SnapshotPublisher and memory ordering semantics
• Runtime tick loop behavior
• Control protocol version (still v1.2)
• Existing CLI commands and outputs
• Threading and isolation model

Design principles reinforced
• Deterministic runtime execution
• Read-only control plane
• Explicit resource ownership
• Forward-compatible architectural evolution

This release marks the point where telemetry persistence is considered stable and safe for future asynchronous export evolution (planned for v1.6).