27df47af5e
The per-profile cold-start probe took its running set from the socket-paused ordinary gateways only. A profile whose gateway is alive under an SCM service is skipped by the socket pause, so it looked "not running"; with an empty current-PID list its live start attestation read as dead and the profile landed in cold_start_profiles. On resume the service was restarted AND a second, unsupervised gateway was spawned for the same profile. Build the running set from every profile that had ANY live gateway at discovery time: paused profiles, profile-mapped processes, and service gateways' profiles. Review finding: service-supervised running profile was cold-started beside its restarted SCM service (double gateway).