Ship a supported native desktop and offline client

[alexschmander]

Problem

The shared Rust UI and native inspector do not constitute a supported desktop client with defined authentication, persistence, packaging, updates, and support.

Current behavior

The inspector is a development/QA tool, may mutate disposable datasets in live mode, and omits browser-only and production-client behaviors.

Desired behavior

Create a separately supported native client that reuses shared domain/UI behavior while owning a complete desktop/offline product contract.

Acceptance criteria

• Define supported operating systems, packaging/signing, installation, updates, and release lifecycle.
• Define authentication, credential storage, filesystem permissions, offline workspace, sync, and conflict behavior.
• Keep inspector-only presets/MCP behavior out of production crates and binaries.
• Provide accessibility/input/display support matrices and end-to-end tests.
• Document support, telemetry/log redaction, migration, backup, and uninstall/data-removal behavior.

Scope

New native product surface; not promotion of egui-mcp-inspector as-is.

Implementation notes

Keep dependencies flowing through the client facade and avoid direct production filesystem policy in the shared UI.

Tracking source

docs/tracking/feature-requests.md:31

Supported native desktop/offline client.