[GOOD FIRST ISSUE][FROZEN BENCHMARK] Benchmark ENTITY v3.4.2's inherited 24-vector Global Passport verifier

[blackmore-technology-group]

Version boundary

Current supported ENTITY runtime: v3.4.3. This issue intentionally benchmarks the frozen v3.4.2 inherited 24-vector verifier so timing results remain tied to one exact historical artifact and set of commitments.

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

Goal

Measure the sealed 24-vector Global Passport verifier carried by v3.4.2 on one clearly documented environment.

This is a benchmark/reporting task, not a request to optimize the protocol or claim production throughput.

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

The verifier must preserve:

• 24/24 expected classifications — 12 valid / 12 invalid;
• sealed-kit SHA-256 f95c2b347da97742fed3f20611f0eec2fd3df48694fed9494fb07163c537cfb7;
• schema SHA-256 3d72b4e67ec9929c5d960cee8fc52db35d85ba5103e361f3a61a8f5078079c5d;
• canonical result SHA-256 ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba.

Measure

Report OS/CPU/Python version, cold invocation time, repeated invocation time, methodology/timing tool, cache effects, and whether every repetition preserved classifications and hashes.

Optional: separate load/parse time from classification time if that can be done without changing semantics.

Evidence boundary

Do not describe this bounded frozen-verifier measurement as production transaction throughput or a universal ENTITY v3.4.3/BTDU performance result.