Source "Not Initialized" Incorrectly Shown as "Disconnected"

Version: 3.1.0 Date: 2026-06-12

Goal: Sources that have never been initialized were displayed with a "Disconnected / Initialization failed" error banner, which is misleading — the state is expected before the first init run.

Solution: Distinguish connected: null (never initialized) from connected: false (init ran and failed). Replace loose !connected checks with strict === false comparisons. Replace the confusing ? icon with a hourglass icon on the "Not initialized" badge. The same three-state model also fixes a related false "Not configured" badge on workflow tiles (getSourcesConnectionStatus seeds connected: null and sets true on an ok entry).

Files Modified:

• ui/src/pages/workflows/workflowEditor.tsx — !connectionStatus.connected → connectionStatus.connected === false
• ui/src/pages/workflows/WorkflowSummary.tsx — ConnectionBanner returns null when connected === null
• ui/src/pages/workflows/WorkflowTile.tsx — HelpOutlineIcon → HourglassEmptyIcon for "Not initialized" badge; three-state badge rendering
• ui/src/pages/workflows/sources.utils.ts — connected: null seed + ok entry handling