XPathRecordedMatchIT fails on the EMBEDDED conformance lane (rift 0.23.0 and 0.24.0) #349

Problem

rift-java-conformance/src/test/java/io/github/achirdlabs/rift/conformance/XPathRecordedMatchIT.java:49 asserts imposter.recorded(RequestMatch.of(List.of(body(equalTo("undefined")).xPath("//a").build()))) returns 1 match (the <a><b/>z</a> request, whose //a selection reads as undefined per rift#1495). On CONFORMANCE_TRANSPORT=EMBEDDED it returns 0. The SPAWN lane passes, and the assertion on the line above (equalTo("x")) passes on both lanes.

Evidence

• Reproduced locally (macOS arm64, JDK 21) with the v0.24.0 librift_ffi-darwin-aarch64.dylib and also with the v0.23.0 dylib, so it predates the engine bump in PR chore(deps): bump rift engine to 0.24.0 and write behaviors the way it admits them #346. The test was introduced in verify: align recorded(RequestMatch) XPath element value with rift 0.23 (rift#1495) #335.
• CI's EMBEDDED conformance jobs did not fail on it. Either CI does not exercise this IT on the embedded lane, or the difference is platform-specific (macOS arm64 only so far).
• Repro:

  RIFT_IT=1 CONFORMANCE_TRANSPORT=EMBEDDED ./mvnw verify -pl rift-java-conformance \
    -Dtest=XPathRecordedMatchIT -Dsurefire.failIfNoSpecifiedTests=false \
    -Drift.corpus.root=<sdk-conformance-v0.24.0> -Drift.ffi.lib=<librift_ffi dylib>
  

  (JDK 21)

Proposed fix

First step: dump imposter.recorded() for the XPath request on both lanes and diff the recorded body. Working hypothesis: the embedded journal stores or returns the request body differently from the HTTP path (for example via the FFI rift_get_imposter recorded path), so the client-side XPath filter in verify/PredicateEvaluator sees a different body than over HTTP. Once the root cause is confirmed, either fix the embedded body path so both lanes match, or correct the test if the embedded behaviour is the intended contract. Also confirm which CI job runs XPathRecordedMatchIT on the EMBEDDED lane, and add it there if it is missing.

Provenance

Found by an agent while verifying PR #346 (engine 0.24.0 bump), /ship-issues run 21. Out of scope for that work, filed as a follow-up.