fix: preserve flat all-in entry transaction sizing#113
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.
Summary
Why
The target chronology contains two independent broker-emulator defects that mask one another. An exhaustive, route-locked N=2 matrix shows neither change alone reaches parity; only both produce exact 481/481/481 canonical and 591/591/591 raw strict+price-exact trades. A second exhaustive N=2 matrix on an independent community strategy shows MARKET alone reaches exact canonical count while STOP is byte-inert.
Evidence
2827a9eb9243ac476e0c923cbb9f4fb5c9245f8bf1a44c4fa3326cd5c3c620bb.00 == 10and01 == 11; MARKET tape5e19626ac7b296084f69af23547bbfe4d029c8f36c53b6e553504ab3487f9e93.Identity
98260ae39fd04e0ea3aacbde5cf65f2bd43e4d8d930b67e38000e4317b05f77e4ce9dc6c3e253be3d710529c54887c6028b4d0cb11d6ae8ca95ec35ed05bb85e38c99dc14311c8c9731dc8f1e818e8b4146366d4e2b9f17cc72591a695abec688bc8013424f13e5f6e97b9b0c1ebbe8d9d136779012c876a4a6ec92552ca91a95d435c658e03954d0f49d52f38624ca88f11e3baedcace1dbdcdb838Scope
No Pine source, TradingView tape, OHLCV feed, verifier routing, tier rubric, corpus pointer, or codegen behavior changes.