feat(strategy31): annotate server-confirmed volume reversals - #302
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
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.
Display server-confirmed red-to-green higher-volume candles as upward arrows on the active Binance chart. The Strategy31 companion uses the existing private CorsairQuant signal provider and a bounded server snapshot; it draws only exact loaded candle times, waits for native interval data completion, and resumes after unsupported periods.
This release updates the shared signal-client capability (0.6.6), Strategy29 bridge consumer (0.5.6), and introduces Strategy31 (0.1.0). Source, generated installers and installation documentation are included.
Validation: Node 24 full suite 2,099 passed; Playwright 379 passed; test lint, affected builds, syntax and release contracts passed. Ten Strategy31 native-host scenarios cover deduplication, interval readiness, loaded-history limits, unsupported market/period recovery, transient native snapshots and stale results. Independent full-PR review passed for the final head. Current Binance export/readiness APIs were inspected through CDP; installed-source and rendered-page acceptance follow backend deployment. No financial browser actions were performed.
Companion: https://github.com/jackhai9/CorsairQuant/pull/407.