PR #8 review fixes — 2026-10-17
Reviewed parent: 353fe0a7be31ef7c75b1fbdeae7e5de9340c1b9e in ParityLab/Hand-Datasets-Raw.
This maintenance change updates tools, tests, documentation and evidence bookkeeping only.
The data/ subtree and raw data are unchanged from that immutable parent.
The merge replaces the old release paths atomically and preserves other datasets.
Evidence scope
No full real-media decode, full numerical comparison or human visual acceptance was rerun for this maintenance change. Historical validation results remain historical, not new sign-off. Human review is still pending; this document does not grant approval. Git tree/blob identities establish unchanged tracked content, not annotation correctness. The maintenance audit records exact before/after Git trees and path changes outside the release; Git blob SHA1 identities must not be confused with file-content SHA256 hashes.
Fix and tests
verify.py requires existing source/target data directories and nonempty source views.
Unselected --complete additionally requires 6750 source views and identical relative
target view paths. Partial/incremental checks cannot replace formal acceptance or rebuild
the publication manifest. Both verify and validate reject a manifest as a report output,
including normalized path aliases. Invalid/empty selections fail before evidence writes.
python -B script/reinterhand_v1_1/test_review_fixes.py: 10 tests pass. The combined
ARCTIC/ReInterHand isolated CLI regression suite passes all 19 scenarios, including
missing source, partial evidence protection and ReInterHand media-valid failures.
Those CLI fixtures use cached numeric data; ARCTIC media/assets are marked placeholders,
and ReInterHand declares unavailable video. They test control flow, not media correctness.
Earlier independent numeric sampling covered 18 ARCTIC and 27 ReInterHand views; this
maintenance does not expand that sample into a full comparison.
FULL_MIGRATION_SUMMARY.json keeps its original validation claims as historical fields;
its maintenance section narrows their provenance. The author's external SHA256 publication
manifest was not available locally. A fresh external PUBLISH_MANIFEST.json is generated
from the final fixed Git tree: SHA256 is computed over ordinary file bytes, and LFS
content SHA256/size is taken from the exact stored pointer. This verifies published
content identities without downloading or decoding the LFS payloads. A separate
Git-identity ledger records paths and blob IDs for merge auditing.
The nine media-metadata schema gaps and finite values at invalid MANO positions are retained exactly from the source. Storage migration is not strict semantic compliance.