fix(strategy29): preserve connection state and order recent signals by close time - #286
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.
Background polling repeatedly replaced a completed connection state with “connecting”, and insertion sequence made cross-period signals appear out of time order. Preserve the last completed connection state during polling and display/retain recent signals by candle close time descending, with sequence breaking ties. Actual backend failures remain visible.
Strategy29 0.5.1 validates the chronological v3 API envelope separately from durable v2 event records. The server selects the same bounded close-time window and keeps the atomic sequence cursor for subsequent increments. Existing event identities and recovery state remain unchanged. Publish the server v3 API before this client; no additional gateway credentials are required.
Validation: 929 unit/DOM tests and 68 Playwright scenarios passed, including iframe-crossing drag and reload position. Syntax/build and diff checks passed. A real server SQLite/HTTP fixture passed through this generated artifact: API v3, latest sequences [1,3], increment [4], and HTTP 400/401/409/503 contracts. Artifact SHA-256: cba1d48551b3b9265e259ed012b0b03127d41b737c79346a6d444fd23d7defa0. Independent read-only review approved the final implementation and documentation. Tampermonkey synchronization and live acceptance follow server deployment.