[GOOD FIRST ISSUE][RUST] Reproduce the v3.4 24-vector campaign on Linux

[blackmore-technology-group]

Difficulty

Easy / bounded reproduction task. No ENTITY implementation work is required.

Goal

Run the published BTG-controlled Rust v3.4 Global Passport campaign on a clean Linux environment and report whether the documented result reproduces exactly.

This is intended to take a contributor from clone → build → one campaign → short evidence report without requiring knowledge of the full ENTITY architecture.

Repository

Use the public Rust baseline:

https://github.com/blackmore-technology-group/ENTITY-RUST-CLEANROOM

Run

git clone https://github.com/blackmore-technology-group/ENTITY-RUST-CLEANROOM.git
cd ENTITY-RUST-CLEANROOM
cargo run --locked --release --bin passport_v34

The repository CI also verifies the sealed kit checksum before running the campaign.

Expected published result

• ENTITY release: v3.4.0 — Global Passport & Continuous Provenance
• vectors: 24/24 PASS — 12 valid / 12 invalid
• sealed-kit SHA-256: 5869a3fd0ed6cb9f65bf4b20c3bd64933cad82f4aef05c5809e2e05af921f230
• canonical result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba

What to report

Comment here with:

1. Linux distribution/version;
2. Rust/Cargo versions (rustc --version, cargo --version);
3. CPU architecture;
4. whether the build completed without undocumented setup;
5. the vector pass count;
6. the produced result hash;
7. any warning, portability problem or documentation ambiguity you encountered.

A reproducible failure is just as useful as a pass. Please do not change expected values to make the campaign pass.

Scope and evidence boundary

This task tests reproducibility of a BTG-controlled Rust baseline. A successful reproduction does not become unrelated third-party implementation evidence or independent security validation.

No credentials, production data, private keys or operational ENTITY state are needed or should be provided.

Contributing guidance

Please read the project contribution guidance before proposing code changes:

https://github.com/blackmore-technology-group/ENTITY/blob/main/CONTRIBUTING.md

If the problem is only a portability/documentation issue, a concise report here is sufficient; you do not need to open a code PR.