[META-split] Direct-Cypher wrong-rows tranche C: tri-valued list/map/null semantics

[lmeyerov]

Summary

Split from #1353. Tranche C for direct-Cypher wrong-row debt: tri-valued comparison semantics (list/map/null/IN).

Scope

• Null-propagation and tri-valued logic in comparison operators.
• IN/list/map comparison semantics and edge-case consistency.

Representative failing scenarios

• expr-comparison3-{1..8}
• expr-comparison1-6-5
• expr-comparison1-7-{12..16}
• expr-list5-{21,29,31,34}
• expr-null{1,2}-3

Acceptance

1. Targeted tri-valued/list/null wrong-row scenarios pass.
2. No increase in unexpected_success_expected_error.
3. Add focused regression tests for ambiguous/null edge cases.
4. Post merge, add receipts to Meta: Prioritized direct-Cypher wrong-row bugfix tranches (92 cases) #1353 and refresh Meta: benchmark coverage unlock plan for GFQL and GFQL/Cypher #992/Meta: GFQL compiler/planner post-M4 execution DAG (active wave) #1259 descriptions.

Related

• Parent meta: Meta: Prioritized direct-Cypher wrong-row bugfix tranches (92 cases) #1353
• Benchmark meta: Meta: benchmark coverage unlock plan for GFQL and GFQL/Cypher #992
• Execution meta: Meta: GFQL compiler/planner post-M4 execution DAG (active wave) #1259