Persist duplicate live run heartbeat reports

[Pigbibi]

Summary

• persist a duplicate-skip strategy run report when live monthly idempotency blocks a repeat run
• keep duplicate runs from submitting orders while refreshing latest/history report timestamps
• update duplicate live run tests to assert report persistence

Tests

• .venv/bin/python -m pytest tests/test_rebalance_service.py -q -k 'duplicate_live_monthly or funding_block'
• .venv/bin/python -m pytest -q

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8903fa03e5

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

[chatgpt-codex-connector]

Use a distinct history stage for duplicate runs

When a duplicate request is processed in the same second as the terminal run it is skipping, persisting it with the original duplicate_stage can overwrite the original history object: persist_strategy_run_state names history entries from run_period, stage, and a seconds-resolution timestamp. In that case the audit entry containing the actual submitted orders can be replaced by this duplicate payload with submitted_orders: [], leaving only the heartbeat in history; use a duplicate-specific stage/suffix or otherwise unique history key for skipped duplicates.

Useful? React with 👍 / 👎.