REVIEWER QUICK START — 1.0.2
========================================================================

This reviewer-package update corrects finite-path endpoint bookkeeping in the custom/reference lane.
The frozen photon steering law and preserved historical H-099/H-109 research archives are unchanged.


ENDPOINT BOOKKEEPING CORRECTION — 1.0.2
---------------------------------------
Fresh reviewer inputs can place +/-half partway through a FrostCell. The older
wrapper inherited H-089's whole-wall completion behavior while its sanity check
used rounded endpoint wall indices. For some inputs (for example R17, half=4.2
or R18, half=5.3) that mismatch could abort a physically monotonic trajectory
with errors such as "expected 142 forward-wall hits, got 144".

Version 1.0.2 fixes the reviewer lane without changing the frozen steering law:

  * the final FrostCell exposure is capped at the exact requested +half endpoint;
  * expected travel-wall crossings are counted from the actual finite interval,
    not from rounded endpoint indices;
  * the post-seal GR ruler is sampled at the same exact finite endpoints and the
    intervening travel-axis wall planes.

The historical H-099/H-109 ZIPs under original/ remain byte-for-byte unchanged,
and the historical reproduction menu options still execute those preserved files.
The R11 / b=4.85 / half=3 reference remains numerically unchanged because its
endpoints already lie exactly on lattice walls.

FIRST-TIME SETUP
----------------
Extract this ZIP and open a terminal in the extracted Frostyverse_Photon_Flyby_Python_Test folder.
A virtual environment is recommended.

Windows PowerShell:
  py -3 -m venv .venv
  .\.venv\Scripts\Activate.ps1

Windows Command Prompt:
  py -3 -m venv .venv
  .venv\Scripts\activate.bat

macOS / Linux / WSL Ubuntu:
  python3 -m venv .venv
  source .venv/bin/activate

Then:
  python -m pip install --upgrade pip
  python -m pip install -r requirements.txt

Dependencies for this Lab: NumPy >= 1.24 and SciPy >= 1.10.

RECOMMENDED REVIEWER WORKFLOW
-----------------------------
1. Verify the preserved research archive(s):
   python lab_test.py --verify

2. Reproduce the quick/reference result:
   python lab_test.py --reference

3. Try a fresh input:
   python lab_test.py --custom --resolution 11 --impact 3.17 --orientation XZ --half 3.0

The custom lane varies normalized fly-by geometry only; it does not invent a new body-mass-to-source mapping.

4. Guided interactive menu:
   python lab_test.py

5. Show every command-line option:
   python lab_test.py --help

The --flags are shortcuts into the same reviewer wrapper. They are useful for
repeatable tests and are not hidden physics parameters.

TROUBLESHOOTING
---------------
Check:
  python --version
  python -m pip install -r requirements.txt

For NumPy/SciPy Labs:
  python -c "import numpy, scipy; print('NumPy', numpy.__version__); print('SciPy', scipy.__version__)"

A fresh-input failure is a useful audit result; do not retune the preserved
historical package just to make a result pass.

========================================================================
DETAILED LAB NOTES
========================================================================

FROSTYVERSE — PHOTON FLY-BY / LIGHT-DEFLECTION PYTHON TEST
=========================================================

WHAT THIS PACKAGE IS
--------------------
This is the self-contained Python Test ZIP for the Frostyverse Laboratory
Photon Fly-by / Light Deflection item.

You do NOT need to accept the Frostyverse as a real theory to use this package.
The purpose is to let an outside reviewer reproduce the declared software result,
change meaningful fly-by inputs, and compare the fresh output with the same
post-seal General Relativity ruler used by the historical audit.

Nothing in the original H-099 or H-109 research archives has been modified.
They are preserved under original/ with their published SHA-256 hashes.

REQUIREMENTS
------------
Python 3.10 or newer is recommended.

Required public libraries:
  NumPy >= 1.24
  SciPy >= 1.10

Install them globally or in your own virtual environment:

  python -m pip install -r requirements.txt

RUN
---
Windows:
  double-click RUN_PHOTON_FLYBY_TEST.bat

macOS / Linux:
  ./run_photon_flyby_test.sh

Direct:
  python lab_test.py

The interactive menu offers:

  1. Reproduce the lightweight H-099 reference fingerprint
  2. Test your own normalized fly-by geometry
  3. Run the unchanged historical H-099 validation profile
  4. Run the unchanged historical H-109 validation profile
  5. Run the unchanged historical H-099 FULL high-R audit (heavy)
  6. Run the unchanged historical H-109 FULL R80 audit (very heavy)
  7. Verify frozen archive hashes
  0. Exit

WHAT "CUSTOM INPUT" MEANS HERE
-------------------------------
The frozen H-099 photon test is expressed in normalized source-radius geometry.
The reviewer can independently vary the inputs that the historical photon audit
itself treats as geometric/numerical test dimensions:

  * impact parameter b, in source-radius units;
  * resolution R, in FrostCells per source radius;
  * travel/impact orientation relative to the cubic grid;
  * path half-length, in source-radius units.

Example fresh test:

  python lab_test.py --custom --resolution 11 --impact 3.17 \
      --orientation XZ --half 3.0

The requested impact parameter is snapped to the legal R-grid exactly as in the
historical test. The program prints both the requested and realized value. The
finite path itself now stops exactly at the requested +/-half endpoints even when
those endpoints lie inside FrostCells.

IMPORTANT SOURCE-MAPPING BOUNDARY
---------------------------------
This package does NOT invent a new Sun/Jupiter/planet mass-to-source mapping.
The historical photon development deliberately kept the planetary/Jupiter
source holdout sealed. Therefore the custom lane tests fresh impact parameters,
resolutions and orientations of the SAME normalized frozen source model.

That is intentional scientific conservatism: a website convenience wrapper must
not add a physical source-transfer rule that the frozen H-099/H-109 calculation
did not contain.

If/when a separate declared physical source mapping is published, it can be
added as its own auditable input layer without changing this frozen package.

FALSIFICATION ORDER
-------------------
For a focused custom run the program does this in order:

  1. Build the Frostyverse field from the frozen H-099 source/model rules.
  2. Generate the FV WALL_CONTINUOUS photon trajectory with GR closed.
  3. Record an FV seal fingerprint and release the field from memory.
  4. Only then open the exact fractional-b GR ruler.
  5. Report FV bend, GR bend, wire nRMSE, maximum physical separation, and
     separation in nominal/local FrostCell widths.

The GR answer does not generate or steer the FV path.

REFERENCE VS FRESH TEST
-----------------------
A reviewer-friendly sequence is:

  A. Run option 1 and confirm the R11 / b=4.85 reference fingerprint.
  B. Run option 2 with a fresh b such as 3.17 and/or a different orientation.
  C. Compare the fresh result with the post-seal GR ruler shown by the program.
  D. Report any failure, large discrepancy, directional dependence, or source/
     scoring leakage found.

A failure is a useful result.

RESOLUTION / HARDWARE
---------------------
The custom lane intentionally uses the historical direct field solver so the
calculation is transparent. Runtime and RAM grow rapidly with R.

  R9-R11   : recommended for a quick independent spot-check
  R12-R16  : stronger numerical spot-check; more RAM/time
  R17-R24  : allowed, but can require substantial RAM

The custom convenience lane is capped at R24 to reduce accidental out-of-memory
runs. The unchanged historical full H-099/H-109 options remain available for
the original high-resolution audits.

RESULT FILES
------------
Focused reference/custom runs write both TXT and JSON records under results/.
Historical runs copy their generated result TXT/CSV files into timestamped
results/ subfolders before the temporary extraction is deleted.

SCIENTIFIC CLAIM BOUNDARY
-------------------------
A successful run shows only that the supplied frozen software behaves as stated
for the tested case. It is not experimental proof that nature uses Frostyverse.
The published H-099 residual is explicitly nonzero and must not be tuned away.

FROZEN HISTORICAL ARCHIVES
--------------------------
original/Frostyverse-Test-H-099.zip
  SHA-256: b26e38ce66dbfa7d18897d59b7c7f744dade66c26a011da36cfa0b4f53ff9d20

original/Frostyverse-Test-H-109.zip
  SHA-256: 7bf655837903d7a6d77b56b03c076870c1594a902ce3be1df0f4249a9b2e8463

Website:
  https://frostyverse.FrostCandy.com
