Keep native AUTO path independent of legacy host overrides - #245
Merged
Conversation
luisleo526
marked this pull request as ready for review
September 12, 2026 14:50
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.
A native confirmed-bar run inherited a forced high/low path from a different legacy host running on the same thread. Identical native input could visit extrema in a different order when nested inside a legacy callback.
Compute native AUTO directly from the bar distances, with Low first on ties. The regression test covers both directions and ties under opposing legacy overrides: all three cases fail against the accepted pre-fix engine and pass on this candidate.
Validation on
9dce114246d402f881b7ec9e3b9a23455dde53fb:exp-native-auto-9dce114-20260912: 72/72 cases, 4,190/4,190 probes; zero full-grade, raw-trade, substantive-verifier, configuration, or coverage differences against the accepted R2a reference. Raw verifier changes are limited to the existing volatile fields. Both pipeline and runner completed successfully.pineforge-pr-gate-zkh27: FAIL, target.not-positive only. Results did not improve. This FAIL is retained under the standing neutral-refactor merge authorization; no PASS receipt or baseline promotion is claimed.Broader native resting-order lifecycle work continues separately. This PR does not complete R2 or resume the parity campaign. Squash merge must preserve tree
7065afdbf53a171e16cd2e66644e7f30ddf20202.