4ad285570c
The seat of a subscribed connection on the DesignWatch lived in the connection's serve thread. It left only when that thread saw the end of the stream, so one unbounded blocking read stood between a closed client and the count. Under load (GPU backend probing and crash-dump children on Windows) that read can sit for seconds; the test's 10 s deadline then expired and `!WATCH.subscribed()` failed (#7226). Move the seat onto the events thread. The thread ends on `stop`, or on the first write a closed client refuses, so the next publish retires the seat. The test now publishes while it waits, and its wait no longer depends on the serve thread.