A reference path ending in a condition hop resolves no column scope

<One-paragraph problem statement: what is missing or broken, and why it matters. Replace this and add a plan body when the item moves to Spec.>

An argument carrying @reference(path: [...]) resolves its column against the path’s terminal table: that is intent_argument_column_scope’s `PATH_TERMINAL basis, reading intent_argument_reference_step_target. A path step can be a key hop ({key: "..."}) or a condition hop ({condition: {className, method}}), and a condition hop names no foreign key, so the step target relation has no row for it and the scope relation has no row for the whole path.

Two coordinates in the sakila example schema are in this population, and both are deliberate fixtures for the shape:

The classifier resolves both. intent_argument_column_scope and intent_argument_column_match have no rows for either, so intent_argument_filter_role has no row either, absence in that relation meaning "a rejection’s population" where these two are nothing of the kind.

Found by diffing intent_condition_membership against what ConditionCommands.produce actually yields for the example schema: the producer emits a condition at both coordinates and the fold could not see either.