fix(lifecycle): preserve backtest runs by identity - #634
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Preserve distinct lifecycle backtest results when separate runs share
computed_at. Results with a nonblankrun_idnow use a bounded SHA-256 path segment underruns/; legacy writes without a run ID retain their existing path. Add exactload_backtest_by_run_idacross new and legacy files with domain/profile/run ID checks and optional parameter version. Keepload_latest_backtestbaseline selection unchanged.Evidence
uv run --frozen python -m unittest tests.test_lifecycle_performance_store -q: 14 tests OK.uv run --frozen --with pytest python -m pytest tests/test_lifecycle_performance_store.py tests/test_strategy_performance_export.py -q: 23 passed.git diff --check: passed.Boundaries
This is a shared storage contract change. No consumer pin, production configuration, market data, account, order, deployment, or promotion status is changed here. The repository's existing
uv.lockdoes not matchpyproject.toml, so local checks used--frozen; this PR does not modify the lock file.