WL-0MN0SS4UD0SJAC3T: lock non-stacking of in-progress & ancestor boosts in computeScore (add regression test)#981
Merged
SorraTheOrc merged 2 commits intomainfrom Mar 22, 2026
Conversation
added 2 commits
March 22, 2026 08:36
…spawns system browser; interferes with local runs)
SorraTheOrc
deleted the
fix/computeScore-non-stacking-WL-0MN0SS4UD0SJAC3T
branch
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.
This PR adds a focused unit test to prevent regression of multiplier stacking in computeScore.\n\n- Adds which directly exercises to verify the in-progress multiplier (1.5) is applied when the item itself is in-progress and the ancestor boost (1.25) is not applied.\n- Keeps integration test.\n\nNo production code changes needed; this PR is a tests-only safeguard.\n\nRefs WL-0MN0SS4UD0SJAC3T.