[GOOD FIRST ISSUE] Reproduce ENTITY v3.4.2's inherited sealed Global Passport campaign on Windows

[blackmore-technology-group]

Goal

From a clean Windows environment, reproduce the sealed Global Passport campaign carried by the current supported ENTITY v3.4.2 release.

This is a bounded portability/reproduction task. No protocol implementation is required.

Current release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.2

Run from the current release

git clone https://github.com/blackmore-technology-group/ENTITY.git
Set-Location ENTITY
git checkout v3.4.2
python .\tools\verify_v3_4_global_passport_release.py

The verifier and kit retain their v3.4 campaign versioning because this is an inherited sealed Global Passport campaign. It is reproducibility evidence carried by v3.4.2, not a claim that the 24 vectors cover BTDU or every current-release feature.

Current v3.4.2 commitments encoded by the verifier:

• vectors: 24 total — 12 valid / 12 invalid;
• sealed kit SHA-256: f95c2b347da97742fed3f20611f0eec2fd3df48694fed9494fb07163c537cfb7;
• Global Passport schema SHA-256: 3d72b4e67ec9929c5d960cee8fc52db35d85ba5103e361f3a61a8f5078079c5d;
• canonical result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba.

Completion evidence

Report:

1. Windows version;
2. Python version;
3. shell used (PowerShell/cmd/Git Bash/etc.);
4. exact command used;
5. verifier output;
6. whether all 24 vectors classify as expected;
7. whether the three commitments reproduce exactly;
8. any setup, path, encoding or documentation issue encountered.

A reproducible failure is useful evidence. Report it rather than changing expected values.

Evidence boundary

A successful reproduction proves this sealed campaign reproduced on the reported Windows environment. It does not by itself establish independent protocol implementation, independent security audit or complete v3.4.2/BTDU qualification.