Repository navigation
stack-encrypt conformance: expand fresh cross-language artifact exchange #1478
Description
Fresh Go-to-Rust exchange currently proves the scalar slice; wider fixtures mostly demonstrate frozen Rust-to-Go reads and local round trips.
Acceptance:
- Exchange freshly written wider values, records, blobs and EQL/JSON artifacts as each profile becomes available.
- Exercise both Rust/Go producer-consumer directions, then Python/TypeScript and their supported backends as those runners arrive.
- Record producer SDK, engine, backend, profile/capabilities and storage/SQL versions in artifacts and reports.
- Compare decrypted values and query semantics, not randomized ciphertext equality.
- Require nonempty fresh outputs and bypass producer test caches; a missing runner or guest must fail a required lane.
- Add supported released-version combinations once the compatibility policy is defined, coordinating with Docs: EQL v4 and Stack Encrypt compatibility policy #1314.
Depends on the relevant enrolled profiles (#1471–#1474 and #1476); Python integration is tracked in #1393. Do not claim every language pair before both implementations exist.
Plan: conformance roadmap and API redesign #1365.
Activity
test(conformance): exchange fresh values, records, blobs and EQL rows…
ci(conformance): run the fresh artifact exchange as a required lane
docs(conformance): define the artifact exchange contract