logly/mureo

Fixed

mureo configure no longer misroutes Claude Desktop users on the Meta connector finalize (#118)

A Claude Desktop user who had connected the Meta hosted MCP saw a misleading "not connected yet — finish the Meta login" on finalize. The in-memory session.host could reset to the claude-code default, so the Claude Code claude mcp list verification path ran for a Desktop user (no CLI ⇒ accusatory dead-end). The official Meta MCP itself was always usable — only the switch-native-off step was wrongly blocked (tool ambiguity, never a strand).

• Client-authoritative host — confirm / native-toggle resolve host from the request payload (validated, self-heals a stale session).
• Host-sync hardening — explicit choice persisted to localStorage and preferred over the server-echoed value; /api/host retries once + toast instead of silent swallow; host re-asserted on load.
• Tri-state connectivity — connected / not_connected / unknown; unknown (no Claude Code CLI / timeout) is not "not connected". Desktop / unknown now offer an explicit "I've verified it" affirm path that applies the native↔official switch — no-strand preserved.

Full changelog: CHANGELOG.md