- Mark Issue #4 (Add TLS/SSL Support) as completed in IMPROVEMENTS.md
- Add v1.4.0 release notes to CHANGELOG.md with detailed TLS/SSL features
- Update Version Support Matrix to include v1.4.0 as current version

- Update README.md and README_KO.md with TLS/SSL features and examples
- Add TLS/SSL to Core Features and Protocol Support sections
- Update architecture diagrams to include secure components
- Add TLS/SSL secure server and client examples
- Add OpenSSL to dependencies (required)
- Update IMPROVEMENTS_KO.md to mark Issue #4 as completed
- Update CHANGELOG_KO.md with v1.4.0 release notes (TLS/SSL support)
- Update Version Support Matrix to include v1.4.0 as current version

* feat(internal): add secure_tcp_socket for TLS/SSL support

Implemented SSL/TLS wrapper for ASIO TCP socket:
- Created secure_tcp_socket class wrapping asio::ssl::stream
- Added async_handshake() for SSL handshake (client/server mode)
- Implemented encrypted async_read_some() and async_write()
- Thread-safe callback registration with mutex protection
- Support for receive and error callbacks
- Start/stop read loop control

This provides the foundation for TLS/SSL encrypted communication
on top of existing TCP infrastructure.

* feat(server): add secure_messaging_server with TLS/SSL support

Implemented secure server for encrypted TCP communication:
- Created secure_session class for SSL/TLS encrypted sessions
- Implemented secure_messaging_server with SSL context management
- Loads SSL certificate and private key at initialization
- Performs SSL handshake before data transmission
- Inherits session cleanup and backpressure from messaging_server
- Supports all monitoring and metrics collection features

SSL Configuration:
- Uses TLS 1.2+ (no SSLv2)
- Loads certificate chain and private key from PEM files
- Server-side handshake for incoming connections
- Automatic session cleanup every 30 seconds

This provides production-ready TLS/SSL encrypted server functionality.

* feat(client): add secure_messaging_client with TLS/SSL support

Implemented secure client for encrypted TCP communication:
- Created secure_messaging_client class for SSL/TLS encrypted connections
- Performs SSL handshake after TCP connection establishment
- Supports certificate verification (optional, configurable)
- Client-side handshake with server certificate validation
- Uses default system certificate paths for verification
- Synchronous handshake with 10-second timeout

Features:
- Encrypted data transmission via send_packet()
- Automatic connection state management
- Thread-safe operations with atomic flags
- Graceful error handling and cleanup
- Compatible with secure_messaging_server

This completes the TLS/SSL client-server implementation.

* feat(build): Add BUILD_TLS_SUPPORT option for conditional SSL/TLS compilation

- Add BUILD_TLS_SUPPORT option (default ON)
- Move TLS/SSL sources to conditional compilation block
- Update WebSocket section to avoid duplicate OpenSSL finding
- Add TLS/SSL support to build configuration summary

* docs: Update documentation for TLS/SSL support implementation

- Mark Issue #4 (Add TLS/SSL Support) as completed in IMPROVEMENTS.md
- Add v1.4.0 release notes to CHANGELOG.md with detailed TLS/SSL features
- Update Version Support Matrix to include v1.4.0 as current version

* docs: Update all documentation for TLS/SSL support

- Update README.md and README_KO.md with TLS/SSL features and examples
- Add TLS/SSL to Core Features and Protocol Support sections
- Update architecture diagrams to include secure components
- Add TLS/SSL secure server and client examples
- Add OpenSSL to dependencies (required)
- Update IMPROVEMENTS_KO.md to mark Issue #4 as completed
- Update CHANGELOG_KO.md with v1.4.0 release notes (TLS/SSL support)
- Update Version Support Matrix to include v1.4.0 as current version

* refactor: remove unused includes from secure_session.cpp

- Remove unused <type_traits> header
- Remove unused send_coroutine.h include
- Build verified successfully

)

* feat(samples): add messaging_system integration examples

- Created legacy_compatibility.cpp showing backward compatibility
- Created modern_usage.cpp demonstrating modern API features
- Both examples show thread pool and container integration
- Added CMakeLists.txt for building samples
- Successfully builds and ready for testing

* feat(tests): enhance compatibility testing

- Created comprehensive compatibility test suite
- Tests legacy namespace aliases and type compatibility
- Validates feature detection and initialization
- Tests cross-compatibility between old and new APIs
- Verifies actual message passing functionality
- Most tests passing successfully

* feat(benchmarks): add comprehensive performance benchmarks

- Add throughput tests for various message sizes (64B, 1KB, 8KB)
- Add concurrent connection benchmarks (10 and 50 clients)
- Add thread pool performance tests (1K and 10K tasks)
- Add container serialization benchmarks
- Measure latency percentiles (P50, P90, P99)
- Include performance rating system for production readiness

Results show excellent performance with 305K msg/s average throughput

* docs: update README and CHANGELOG for Phase 4

- Clean up README from 2400 lines to ~250 lines
- Add performance benchmark results to README
- Update project status to Phase 4 In Progress
- Add comprehensive CHANGELOG entries for Phase 3 and 4
- Include API examples for both modern and legacy usage
- Document achieved performance metrics (305K+ msg/s)
- Update architecture overview with new integration components

* docs: add comprehensive migration guide

- Create detailed MIGRATION_GUIDE.md for messaging_system users
- Provide two migration paths: compatibility mode and full migration
- Include step-by-step instructions with code examples
- Document namespace changes and API differences
- Add troubleshooting section for common issues
- Include performance considerations and benchmarking tips
- Provide migration checklist for systematic approach

* feat(internal): add secure_tcp_socket for TLS/SSL support

Implemented SSL/TLS wrapper for ASIO TCP socket:
- Created secure_tcp_socket class wrapping asio::ssl::stream
- Added async_handshake() for SSL handshake (client/server mode)
- Implemented encrypted async_read_some() and async_write()
- Thread-safe callback registration with mutex protection
- Support for receive and error callbacks
- Start/stop read loop control

This provides the foundation for TLS/SSL encrypted communication
on top of existing TCP infrastructure.

* feat(server): add secure_messaging_server with TLS/SSL support

Implemented secure server for encrypted TCP communication:
- Created secure_session class for SSL/TLS encrypted sessions
- Implemented secure_messaging_server with SSL context management
- Loads SSL certificate and private key at initialization
- Performs SSL handshake before data transmission
- Inherits session cleanup and backpressure from messaging_server
- Supports all monitoring and metrics collection features

SSL Configuration:
- Uses TLS 1.2+ (no SSLv2)
- Loads certificate chain and private key from PEM files
- Server-side handshake for incoming connections
- Automatic session cleanup every 30 seconds

This provides production-ready TLS/SSL encrypted server functionality.

* feat(client): add secure_messaging_client with TLS/SSL support

Implemented secure client for encrypted TCP communication:
- Created secure_messaging_client class for SSL/TLS encrypted connections
- Performs SSL handshake after TCP connection establishment
- Supports certificate verification (optional, configurable)
- Client-side handshake with server certificate validation
- Uses default system certificate paths for verification
- Synchronous handshake with 10-second timeout

Features:
- Encrypted data transmission via send_packet()
- Automatic connection state management
- Thread-safe operations with atomic flags
- Graceful error handling and cleanup
- Compatible with secure_messaging_server

This completes the TLS/SSL client-server implementation.

* feat(build): Add BUILD_TLS_SUPPORT option for conditional SSL/TLS compilation

- Add BUILD_TLS_SUPPORT option (default ON)
- Move TLS/SSL sources to conditional compilation block
- Update WebSocket section to avoid duplicate OpenSSL finding
- Add TLS/SSL support to build configuration summary

* docs: Update documentation for TLS/SSL support implementation

- Mark Issue #4 (Add TLS/SSL Support) as completed in IMPROVEMENTS.md
- Add v1.4.0 release notes to CHANGELOG.md with detailed TLS/SSL features
- Update Version Support Matrix to include v1.4.0 as current version

* docs: Update all documentation for TLS/SSL support

- Update README.md and README_KO.md with TLS/SSL features and examples
- Add TLS/SSL to Core Features and Protocol Support sections
- Update architecture diagrams to include secure components
- Add TLS/SSL secure server and client examples
- Add OpenSSL to dependencies (required)
- Update IMPROVEMENTS_KO.md to mark Issue #4 as completed
- Update CHANGELOG_KO.md with v1.4.0 release notes (TLS/SSL support)
- Update Version Support Matrix to include v1.4.0 as current version

* refactor: remove unused includes from secure_session.cpp

- Remove unused <type_traits> header
- Remove unused send_coroutine.h include
- Build verified successfully

Adds tests/unit/websocket_server_loopback_test.cpp registered via
add_network_test. The new fixture drives messaging_ws_server end-to-end
against a real RFC 6455 client (built from internal::websocket_socket
+ tcp_socket on a probed free port) so that branches reachable only
via a live handshake are exercised:

  - do_start_impl / do_stop_impl success paths
  - start_server(uint16_t,sv) already-running early-return
  - start_server(ws_server_config&) overload
  - i_websocket_server::start(port) interface delegation past start
  - do_accept loop with multiple concurrent clients
  - handle_new_connection success / max_connections-zero limit /
    handshake-failure (raw garbage payload) branches
  - on_message text + binary dispatch in invoke_message_callback
  - on_close path with peer-initiated close frame, including
    connection_count return-to-zero
  - broadcast_text / broadcast_binary populated-session branches
  - get_connection / get_all_connections success branches
  - ws_connection accessors (id, is_connected, path, remote_endpoint)
    and send/send_text/send_binary/close (no-arg + code+reason) reachable
    only after a real handshake
  - auto_pong true and false branches in handle_new_connection's
    ping_callback
  - bind_failed catch arm of do_start_impl (port held by a separate
    acceptor)
  - ~messaging_ws_server while running calling stop_server

The hermetic file test_messaging_ws_server.cpp explicitly documents a
no-peer / no-io_context invariant; mixing loopback tests there would
break that invariant. The new file is placed under tests/unit/ to align
with the existing websocket_server_branch_test.cpp / websocket_server_test.cpp
convention for the same class.

Local build verification was not possible (no C++ toolchain available
in the sandbox); CI is the source of truth for AC #1-#4. AC #5 (#953
post-merge coverage delta) is tracked separately.

Part of #1067

…0% branch (#1081)

* test(websocket): add loopback fixture for websocket_server.cpp coverage

Adds tests/unit/websocket_server_loopback_test.cpp registered via
add_network_test. The new fixture drives messaging_ws_server end-to-end
against a real RFC 6455 client (built from internal::websocket_socket
+ tcp_socket on a probed free port) so that branches reachable only
via a live handshake are exercised:

  - do_start_impl / do_stop_impl success paths
  - start_server(uint16_t,sv) already-running early-return
  - start_server(ws_server_config&) overload
  - i_websocket_server::start(port) interface delegation past start
  - do_accept loop with multiple concurrent clients
  - handle_new_connection success / max_connections-zero limit /
    handshake-failure (raw garbage payload) branches
  - on_message text + binary dispatch in invoke_message_callback
  - on_close path with peer-initiated close frame, including
    connection_count return-to-zero
  - broadcast_text / broadcast_binary populated-session branches
  - get_connection / get_all_connections success branches
  - ws_connection accessors (id, is_connected, path, remote_endpoint)
    and send/send_text/send_binary/close (no-arg + code+reason) reachable
    only after a real handshake
  - auto_pong true and false branches in handle_new_connection's
    ping_callback
  - bind_failed catch arm of do_start_impl (port held by a separate
    acceptor)
  - ~messaging_ws_server while running calling stop_server

The hermetic file test_messaging_ws_server.cpp explicitly documents a
no-peer / no-io_context invariant; mixing loopback tests there would
break that invariant. The new file is placed under tests/unit/ to align
with the existing websocket_server_branch_test.cpp / websocket_server_test.cpp
convention for the same class.

Local build verification was not possible (no C++ toolchain available
in the sandbox); CI is the source of truth for AC #1-#4. AC #5 (#953
post-merge coverage delta) is tracked separately.

Part of #1067

* docs(changelog): record websocket_server loopback coverage tests

Add Unreleased entries to root CHANGELOG.md and docs/CHANGELOG.md (SSOT)
covering the new tests/unit/websocket_server_loopback_test.cpp and the
exact branches it exercises (do_start_impl/do_stop_impl success paths,
do_accept loop, handle_new_connection success/limit/handshake-failure
branches, on_message text+binary dispatch, on_close, broadcast populated-
session branches, get_connection/get_all_connections success, auto_pong
true/false branches, bind_failed catch arm, ~messaging_ws_server while
running, ws_connection/ws_connection_impl methods).

Part of #1067