The preflight outcome: what Lotus knows about the relations a statement touches.

The outcome is one of:

• a list of {schema, table} relations preflight proved the statement touches — an empty list means it touches none;
• {:unrestricted, reason} for an adapter that cannot name the relations a statement touches, when the host opted in;
• {:skipped, reason} for a statement the adapter does not preflight.

The two tuples both mean "unknown". A consumer that gates on the list matches when is_list/1 and refuses any tuple rather than reading it as an empty set.

Lotus.Preflight.analyze/4 returns the outcome as a value, and Lotus.Runner carries it down the pipeline explicitly: middleware reads it from the :relations key of the :before_execute and :after_query payloads. The runner neither writes nor reads the process dictionary.

put/1, get/0, take/0 and clear/0 still store an outcome in the process dictionary for callers that did so themselves. They are deprecated: process state is invisible to supervision, leaks across queries in a reused process and cannot cross a Task boundary. They are removed in v2.0.