TriQAS: reproducibility record (v1) and frozen protocol v2

Record of the study "TriQAS: What the Evaluator Decides in Quantum Architecture Search"(S. Alla, A. Shiri Sichani, University of Missouri). (1) v1 record: code at git tag results-v1 (commit ebbeb67) with all raw run records(development seeds 100-119, confirmatory seeds 1000-1029). (2) Protocol v2, frozen at git tag protocol-v2 (commit b297218867243b11c8464b45cd397a9e5e450c52,2026-11-03 04:33 UTC). The archive contains the code at that tag, including the analysis code(triqas_tqe/analyze_v2.py), and the development data used for the checkpoint decisions(seeds 2100-2119). protocol-v2.md is also attached on its own. SHA-256triqas_tqe_repro_results-v1.tar.gz 2c2a7cc4b9551bd9a47923a1a44a6fb1dc59baf3019d34524f8d9d5e9af50565triqas_tqe_repro_protocol-v2.tar.gz e6732330889ec62b8901fbf52b8d7ac877ccbc033a9c2de6344ec976c7ab6bdd Disclosure: 24 confirmatory search runs (seeds 4000-4029) completed between the protocol-v2tag and this deposit (2026-11-03 04:46-04:48 UTC), all from the tagged commitb297218867243b11c8464b45cd397a9e5e450c52. They are listed with SHA-256 checksums inearly_runs_before_deposit.txt (SHA-256 c565d41be22758738930adc45e0e2666dbb7366dd7c5f4907fc54f781378de4a),were not inspected, and are kept and reported like every other run. Note: the SHA256SUMS file inside each archive lists its own checksum, which cannot match(it was written while the listing was made); every other entry verifies.