v0.2.22

v0.2.22: add Mihomo local proxy management and environment bindings

This tag captures the first complete Mihomo / Clash-Verge local proxy integration after v0.2.21.

Changes included:

• Added a Mihomo management flow in Proxy Center, including entry points in the sidebar and proxy page, a connection dialog for external-controller configuration, and a dedicated Mihomo page for viewing groups and nodes.

• Added Mihomo backend integration in Tauri, including controller connectivity checks, overview loading, node delay testing, group delay testing, and connection config persistence.

• Added local proxy node orchestration based on Mihomo selections: selected nodes can now be compiled into local listeners, persisted in Simprint, and displayed as a separate Local Proxy mode in Proxy Center.

• Added Mihomo runtime detection and status polling, including multi-process detection for Clash Verge / Mihomo runtimes and stricter connected-state semantics so the UI only shows a healthy state when the controller is actually reachable.

• Added environment and create-window support for choosing between remote proxies and local Mihomo proxies, including local binding persistence, recovery, and display in environment lists and proxy selection drawers.

• Added listener self-healing during Mihomo runtime polling so persisted local proxy listeners can be restored automatically after Clash / Mihomo restarts reset the active config.

• Updated the Proxy Center header to mark the Mihomo local proxy workflow as experimental and explicitly note Clash-Verge availability.

Expected result:

• Users can connect Simprint to an existing Mihomo / Clash-Verge instance, inspect available groups and nodes, select nodes into Simprint-managed local proxies, and bind those local proxies to environments without introducing a bundled sidecar core.

• If the external controller remains reachable, local listener configuration can be recovered automatically after runtime restarts.