provider-management-workflow

What problem does it solve?

Provider-management workflows fail in practice when credentials are mishandled, health/degradation handling is inconsistent, UI logic blocks on network calls, or operators lack clear recovery state when a provider becomes unavailable.

Core Features & Use Cases

• Secure credential handling and redaction: Prevent secrets from leaking into logs, chat, screenshots, snapshots, and test artifacts while validating credentials safely.
• Provider readiness, health, and degradation orchestration: Implement setup, credential flows, health monitoring, calibration, validation, fallback, and operator recovery with explicit disabled reasons.
• Deterministic, testable WPF workflow design: Keep provider calls in services, projection/state in view models, and add tests for cancellation, retries/backoff, degraded/unavailable providers, and read-only/live-action guards.

Use Case: Add credential validation and clear operator recovery state to a Meridian WPF provider screen so operators can safely connect, observe degradation, and fallback without risking secret exposure or blocking the UI.

Quick Start

Use provider-management-workflow to implement credential validation, provider health/degradation recovery, and the WPF-ready operator state for a Meridian desktop provider screen.