Repository navigation
DisplayLink brightness restoration now becomes eligible 0.5 seconds after WCH detects the monitor, down from 3 seconds. The existing quarter-second timer starts the write without waiting for the next native brightness poll.
Display identity validation, acknowledgement checks, and bounded retries remain in place. DisplayLink discovery and monitor startup still contribute to the total reconnect time.
Regression coverage includes rapid disconnects, early vendor errors, stale acknowledgements, retry exhaustion, and independent brightness targets.
Validated by 164 Swift tests and 218 standalone regression checks. A physical reconnect test restored both monitor profiles, brightness levels, portrait layout, and nine windows, with both touch controllers active.