fix(smartproxy): Fix route security configuration location and improve ACME timing tests and socket mock implementations

readme.problems.md

@@ -75,4 +75,12 @@ TypeError: Cannot read properties of undefined (reading 'type')
 - SmartProxy forwards raw HTTP data to HttpProxy's HTTPS port
 **Impact**: Plain HTTP connections cannot be handled by HttpProxy, despite `useHttpProxy` configuration suggesting this should work.
 **Root Cause**: Design mismatch - HttpProxy is designed for HTTPS/TLS termination, not plain HTTP forwarding.
-**Status**: Documented. The `useHttpProxy` configuration should only be used for ports that receive TLS connections requiring termination. For plain HTTP forwarding, use direct forwarding without HttpProxy.
+**Status**: Documented. The `useHttpProxy` configuration should only be used for ports that receive TLS connections requiring termination. For plain HTTP forwarding, use direct forwarding without HttpProxy.
+
+## 9. Route Security Configuration Location Issue
+**Problem**: Tests were placing security configuration in `route.action.security` instead of `route.security`.
+**Evidence**: 
+- `test.route-security.ts` - IP block list test failing because security was in wrong location
+- IRouteConfig interface defines security at route level, not inside action
+**Impact**: Security rules defined in action.security were ignored, causing tests to fail.
+**Status**: ✅ FIXED - Updated tests to place security configuration at the correct location (route.security).