Shipped in AD 1.9.218, with a deliberate design change from the literal ask.
What you reported is real and is fixed: a manual Disconnect (individual or Disconnect All) used to be silently re-dialed within 30 seconds by the reconnect supervisor, which made the button look broken. As of 1.9.218 an explicit Disconnect STICKS - the supervisor and every automatic connect path skip that server, and the row shows a 'paused until relaunch' pill.
Why we did NOT flip auto_connect persistently: Adom Desktop is the machine's remote recovery channel. A persisted disconnect-all would mean one forgotten click permanently severs remote access to the box - the next reboot comes up disconnected and the machine goes dark for every cloud agent, with nobody at the keyboard to notice why. That failure class has bitten before (a deleted boot artifact left a machine unreachable for a day), so durable off-switches for connectivity are something we avoid by policy.
The shipped model: the pause is session-scoped. It holds until you press Connect (or Connect All), or until Adom Desktop next launches - at which point normal auto-connect resumes. You get 'my click means what it says' for the whole session; the machine keeps its guarantee that a reboot restores reachability. If you genuinely want a server to never auto-connect, that already exists as the per-server auto-connect toggle in the row menu - an explicit, visible, durable setting rather than a side effect of a Disconnect click.