StopAndWait closed signal loop

Trap: ignoring nil values from a systemd signal channel looks like harmless filtering, but a closed channel returns nil forever and creates a tight loop; a later context.Background() property query can then hang indefinitely. Fix: use the two-value receive to detect closure and apply explicit deadlines to every subscription, state query, session wait, shutdown, and orphan-cleanup operation.