Scope Dashboard Source Evidence

The owner console can show multiple configured connections for the same connector type. The current dashboard still has routes and cards that fall back from a concrete connection to connector-wide run evidence. That makes real sources look broken, duplicated, or actionable based on sibling/orphan connector runs.

The owner-facing goal for Sources is: "I know what data I have, I know what is broken, and I know what to do next." That fails when the console mixes connector type identity (amazon, chase) with configured source identity (connectorinstanceid / connection_id).

The GET /_ref/connectors connection-summary route SHALL accept an optional connection-selector query parameter. When the selector is present, the route SHALL project and return only the connection the selector resolves; when it is absent, the route SHALL return summaries for all configured connections exactly as before. The scoped projection SHALL be the same per-connection projection used to build the unscoped list, so a single-connection summary cannot diverge from the connection's entry in the full list.

Owner dashboard surfaces that present, diagnose, or recover one configured data source SHALL address that source by its configured connection identity (connectionid / connectorinstanceid) rather than by connector type alone. Connector-type identifiers (connectorid) MAY be used for catalog, setup, aggregate, or explicitly connector-wide views, but SHALL NOT be used as a silent fallback for a per-source detail, recovery, or action route when multiple active configured connections share that connector type.