a549989332
- move runtime policy/diag contracts to domain-owned facade and remove control_plane leapfrog usage - enforce single declaration point for direct debug config in domain public API (constraint #6) - harden timeout/idempotent semantics in REST/voice/printer/wifi/ble paths
Control Plane Layer
Purpose: lifecycle, policy, health checks, retry/backoff, and orchestration decisions.
Rules:
- Contains "decision + orchestration" only.
- Calls domain APIs; does not absorb hardware details.
- Maintains dependency whitelist decisions for exceptional lateral coupling.