What
RelativeClearanceCondition::evaluate_for_entity (core/src/ir/interaction_condition.cpp:437-442) is an unconditional return false with every parameter unused. Its comment defers to p3-s4, which is merged: the road backend, lane queries, and the s/t distance plumbing (core/src/runtime/distance_measure.cpp) all exist now. The coverage matrix row points at the closed owner, so nothing tracks the remainder.
Options
- Implement the declared semantics — adjacent-lane / longitudinal-window freeness over
IRoadQuery (checked area in lane coordinates per ASAM OpenSCENARIO XML 1.4 §6.4.5, oppositeLanes, distanceBackward/Forward, RelativeLaneRange, freeSpace, entityRef filter) — with fixtures in road_integration_test.cpp / condition_byentity_interaction_test.cpp on the hand-authored maps.
- Or re-scope to Post-v0.0.1: emit a proper road-guarded UnsupportedFeature diagnostic, flip the matrix row to Post with this issue as owner, and add it to the roadmap's post-v0.0.1 list.
Silently returning false while the matrix implies delivery is the one state that must not survive to the tag.
What
RelativeClearanceCondition::evaluate_for_entity(core/src/ir/interaction_condition.cpp:437-442) is an unconditionalreturn falsewith every parameter unused. Its comment defers to p3-s4, which is merged: the road backend, lane queries, and the s/t distance plumbing (core/src/runtime/distance_measure.cpp) all exist now. The coverage matrix row points at the closed owner, so nothing tracks the remainder.Options
IRoadQuery(checked area in lane coordinates per ASAM OpenSCENARIO XML 1.4 §6.4.5,oppositeLanes,distanceBackward/Forward,RelativeLaneRange,freeSpace,entityReffilter) — with fixtures inroad_integration_test.cpp/condition_byentity_interaction_test.cppon the hand-authored maps.Silently returning false while the matrix implies delivery is the one state that must not survive to the tag.