Could you make a kill switch to switch between offline and online?

### Feature Idea

Right now ComfyUi looks like the huge security risk, connecting to the Internet in unknown ways with the nodes APIs, updates and other things. You never know when it's going online and for what.
It doesn't quit its multiple processes after closing the desktop version.
It caches your workflows that you already discarded including your personal prompts in some weird, secret locations.
It seems to have no control over custom code, possibly malicious, distributed via its manager, git or other ways.

Come on guys, we're in 2026 here, where surveillance by tech companies of everything you do in life and hordes of malicious actors using AI like advanced programmers is the new reality.
How about a kill switch that simply puts everything offline and stays that way until you turn the switch to online
when you want that?

### Existing Solutions

_No response_

### Other

_No response_

No files, tests, or entry points are named. Start by mapping the desktop process lifecycle, network-access paths, workflow caching, and custom-node or manager integrations; define the offline boundary and verify that all affected processes remain offline until the switch is reversed.

Written by the indexing model from the issue text.