Build a unified connection center with actionable repair flows #6

Outcome

Users need one place to understand the separate agent, UltraCart, and warehouse connections and fix the exact failing boundary.

Priority: P1 · Product

Scope

• Show each connection's configured runtime, readiness, last check time, and relevant scope without exposing credentials.
• Keep installed, signed in, authorized, and verified states distinct.
• Reuse the warehouse diagnostics and add equivalent adapter-backed checks for the other connections.
• Provide a specific next action, copyable terminal command where useful, and contextual help for each failure.
• Warn when a successful check is stale or applies to a different configuration.

Acceptance criteria

• An invalid path, broken interpreter, expired login, missing permission, and network failure show distinct guidance.
• A logged-in user is not told to sign in again for an unrelated startup or IAM failure.
• Checking a connection does not publish content, allocate IDs, or execute warehouse SQL.
• Changing settings invalidates prior results; switching stores cannot display another store's check as current.
• Users can run a check and see a clear outcome without reading raw logs.

Validation

Cover error-state transitions with fixtures and verify the repair flow in the desktop UI using synthetic data or authorized read-only checks.

Dependencies

• Standardize tool adapters and runtime compatibility diagnostics #5 — Standardize tool adapters and runtime compatibility diagnostics