Understand connection limitations

A Shutdown Gate can claim only what the current DataHub connection verifies. Core metadata, schema, downstream lineage, and ownership/domain reads are required before analysis starts.

Exact lineage paths, query context, catalog documents, and current actor context can strengthen a conclusion but may be absent from a particular MCP server. Payne records those gaps and returns Insufficient evidence whenever a decisive claim depends on unavailable context.

The first analysis follows downstream lineage for at most three hops and 25 discovered consumers. A zero-result read means no consumer was found inside that boundary; it is not a guarantee of total dependency coverage.

Open Connection, inspect the named capability, and restore the MCP/DataHub service or permissions. Recovery is confirmed only when a fresh capability snapshot shows the required read.