fix(strategy27): clarify symbol monitoring and connection states - #280
Merged
Merged
Conversation
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.
After a symbol was removed from Strategy 27 monitoring, the panel stayed on its last historical observation while the compound connection could still say connected. That wording made stopped symbol coverage look like a frozen panel or resumed monitoring.
Add a prominent last-reported monitoring status independent of history selection and connection state. Restore removal/stop evidence from accepted ordinary events, including outcome-only bootstrap records, before chart rendering. Prevent delayed older events and active replay for a closed event from undoing the report. Display the ordinary data connection separately and clarify that compound connectivity does not confirm symbol monitoring. The gateway paths, selection rules, trading behavior, and marker-retention contract are unchanged. Generated version: 0.4.5.
Validation: 148 Strategy 27 checks and 848 full-suite tests pass, along with build, syntax, release contract, and diff checks. Source/generated regressions cover removal across resets and outcome-only bootstrap; panel tests cover selection, reconnect, delayed events, reentry and clear. An isolated browser render verified the removed-symbol and connected-feed messages together, viewport fit, and collapse/restore. Production post-release evidence is reported separately.