fix(sim): make radio comparisons reproducible

[Komzpa]

Summary

• seed rebroadcast jitter from the simulation seed and node id so static/DCR/DTP comparisons do not drift with system entropy
• route interactive receiver calculations through the shared link-budget helper so terrain, clutter, antenna gains, and fitted calibration stay consistent
• switch the interactive node-config load to yaml.safe_load and remove small import/string cleanups
• print PHY-loss and capture-collision reason counters in direct loraMesh.py runs when those models are enabled
• add regression tests for deterministic rebroadcast jitter and near-field path-loss floor behavior

Stack

• Split from feat(sim): add Batumi radio physics for DCR #64.
• Stacked after refactor(sim): make lora mesh cli importable #67, feat(sim): add map and terrain inputs #68, feat(sim): add land-cover clutter inputs #69, feat(sim): add capture-aware rf physics #70, feat(sim): add dynamic coding rate policy #71, feat(sim): add dynamic tx power policy #72, feat(sim): add batumi radio preset #73, and feat(sim): add radio policy compare workflow #74.
• Intended review commit: e0d71f8 (fix(sim): make radio comparisons reproducible).

Validation

• .venv/bin/python -u loraMesh.py 2 --no-gui --simtime-seconds 2 --period-seconds 1 --phy-loss-model --capture-collision-model
• .venv/bin/python -m unittest tests.test_lora_mesh_cli tests.test_node tests.test_phy tests.test_radio_policy_compare
• /home/kom/.local/bin/ruff check batchSim.py lib/interactive.py lib/node.py loraMesh.py tests/test_node.py tests/test_phy.py
• .venv/bin/python -m compileall -q .
• .venv/bin/python tools/radio_policy_compare.py --simtime-seconds 5 --period-seconds 2 --policies static,dcr,dcr_dtp -- --no-clutter
• .venv/bin/python -m unittest (134 tests)
• git diff --check
• private-marker scan for deployment/source terms

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f72b56b3dc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".