Fix SG durable next-session execution and reconciliation - #469
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
1 participant
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.
SG emits next-session strategy decisions, but its live cycle previously rejected them without a durable consumer. Add a default-off SOXL live path that saves each daily signal, executes the prior immutable target only in its effective exchange session, and continues saving the next daily signal.
The consumer uses fresh account capital and the original loss/consecutive-loss diagnostics, RiskEngine limits, account-owner fence and atomic execution claim. Old unresolved orders block newer commands; known order IDs are reconciled through LongPort order_detail, including actual SDK enum normalization. Unknown outcomes are never resubmitted. Normal queued signals are reported as waiting rather than as a missing execution path.
Validation: confirmed failing regressions before correction; related suite 129 passed and 22 subtests passed, focused report-summary regression passed, Ruff and diff checks passed. Coverage includes three trading sessions, prior-order blocking, immutable targets and SDK order identity/status handling. No broker orders were sent during validation. The live flag remains off by default; production business recovery still requires the original scheduled signal/consumption cycle.