./verify still points at removed v1/ proof paths

[Fewmanism]

Running ./verify from a fresh clone fails before the proof pipeline runs because the wrapper looks under v1/data/proof and v1/src, while the files in the current repo are under archive/v1/....

Observed from a fresh clone:

FAIL: Reference signal not found at .../RuView/v1/data/proof/sample_csi_data.json
FAIL: verify.py not found at .../RuView/v1/data/proof/verify.py

Local minimal fix that allowed the wrapper to reach the proof script:

-PROOF_DIR="${SCRIPT_DIR}/v1/data/proof"
+PROOF_DIR="${SCRIPT_DIR}/archive/v1/data/proof"
 VERIFY_PY="${PROOF_DIR}/verify.py"
-V1_SRC="${SCRIPT_DIR}/v1/src"
+V1_SRC="${SCRIPT_DIR}/archive/v1/src"

Environment: macOS, Python 3.9.6.

[ruvnet]

Thanks for the diff @Fewmanism — applied verbatim in #562. The four occurrences (PROOF_DIR, V1_SRC, the Phase 3 scan-message, and the SKIP-state recovery hint) are all updated to archive/v1/..., and ./verify now passes end-to-end on a fresh clone.

🤖 Generated with claude-flow