Redesign Settings around Conduit readiness

[dougrathbone]

Redesigns Settings around a clearer picture of whether Conduit is ready to use.

Readiness overview

• A prominent overall state leads with Conduit is ready, needs attention, or not fully ready.
• Git, encryption, and MCP connections are presented as separate status tiles with plain-language states and details.
• MCP failures include the affected connection and a direct action to review MCPs.

Settings hierarchy

• Wider, responsive page layout with stronger section hierarchy.
• Agent credentials are grouped into compact, consistent connection cards instead of a long stack of repeated panels.
• Technical timeout copy is simplified and unsupported settings are clearly marked.
• Prompt components are reframed as Run defaults with concise explanations.
• Storage is simplified around usage and the cleanup action.

Health checks

• Git — confirms git is available on PATH and displays its version/path.
• Encryption — verifies the configured key with an encrypt/decrypt round trip and confirms existing encrypted credentials can still be read.
• MCPs — probes enabled global MCPs and distinguishes authentication issues from connection failures.

Validation

• Unit tests cover git, encryption, and MCP health outcomes.
• Server and renderer TypeScript checks.
• Manual browser verification of the ready state, refresh behavior, and an unreachable MCP state.