Tranche: Temporal wrong-row semantics (14 cases) under #1353 #1365

Summary

One-PR tranche under meta-issue #1353: resolve temporal wrong-row semantics in direct-Cypher execution.

Current bucket size: 14 wrong-row cases.

Scope (keys)

• expr-temporal7-1-1
• expr-temporal7-1-2
• expr-temporal7-2-1
• expr-temporal7-2-2
• expr-temporal7-3-1
• expr-temporal7-3-2
• expr-temporal7-4-1
• expr-temporal7-4-2
• expr-temporal7-5-1
• expr-temporal7-5-2
• expr-temporal7-6-8
• expr-temporal6-6-2
• expr-temporal6-6-8
• expr-temporal2-6-5

Why this tranche

• High practical impact (temporal filters/sorts/comparisons are common).
• Dense cluster likely sharing comparator/canonicalization logic.
• One PR size is realistic and measurable.

Acceptance criteria

• All listed keys move from success_wrong_rows to success_matches_expected.
• unexpected_success_expected_error does not increase.
• No regression in direct-cypher support snapshot and focused tck contract checks.
• Keep semantics vectorized and cuDF-compatible.

Repro

• PYTHONPATH=/home/lmeyerov/Work/pygraphistry:/home/lmeyerov/Work/tck-gfql UV_EXCLUDE_NEWER="6 days" uv run --python 3.13 --no-project --with pytest --with pandas python -m pytest -q tests/cypher_tck/test_tck_runner.py -k "test_direct_cypher_xfail_contract"
• PYTHONPATH=/home/lmeyerov/Work/pygraphistry:/home/lmeyerov/Work/tck-gfql UV_EXCLUDE_NEWER="6 days" uv run --python 3.13 --no-project --with pytest --with pandas python -m tests.cypher_tck.report

Cross-reference

• Parent meta-issue: Meta: Prioritized direct-Cypher wrong-row bugfix tranches (92 cases) #1353
• Upstream tck harness fix already landed separately in tck-gfql PR Python keywords cannot be used as fields of edges.  #37.