fix: isolate backtest result route loading - #184
Merged
Conversation
hjcud
marked this pull request as ready for review
September 3, 2026 07:50
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
2 participants
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.
Summary
/backtestsresult route from the shared operations/competition moduleVerification
pnpm exec vitest run --no-file-parallelism --maxWorkers=1— 688/688pnpm exec playwright test --workers=1— 26/26pnpm e2e:operator-session— 1/1pnpm e2e:real-api— 3/3 against an isolated real backendpnpm typecheckpnpm buildRelease-proof status
Draft only. The prior machine's verified 44-object actual-market-data corpus is not present on this host. The unchanged real strategy → release → worker → result journey and Task 7 soak must be rerun after that ignored local corpus is restored. No synthetic OHLCV was used.