feat(sim): add radio policy compare workflow

[Komzpa]

Summary

• add a one-command radio policy comparison wrapper for static, DCR, and DCR+DTP runs on the same preset and traffic load
• write JSON and Markdown reports that can be used as CI artifacts
• add optional regression thresholds for reach, useful traffic, and TX-air changes
• document the quick workflow in README and a dedicated radio physics quickstart

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, and feat(sim): add batumi radio preset #73.
• Intended review commit: 2aa56dd (feat(sim): add radio policy compare workflow).

Validation

• .venv/bin/python -m unittest tests.test_radio_policy_compare tests.test_lora_mesh_cli
• /home/kom/.local/bin/ruff check tools/radio_policy_compare.py tests/test_radio_policy_compare.py
• .venv/bin/python -m compileall -q .
• .venv/bin/python tools/radio_policy_compare.py --simtime-seconds 5 --period-seconds 2 --policies static,dcr -- --no-clutter
• .venv/bin/python tools/radio_policy_compare.py --simtime-seconds 5 --period-seconds 2 --policies static,dcr --json-output out/radio_policy_compare_smoke.json --markdown-output out/radio_policy_compare_smoke.md --max-reach-drop-pp 100 --max-tx-air-increase-pp 100 -- --no-clutter
• .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 (132 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: 9b9a9e86c1

ℹ️ 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".