You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(trade): preserve every valid influence pair in the query UI
The influence callback was over-normalizing Ignore+None and None+specific
pairs, forcing them back to None/None and locking users out of states the
query state resolver already supports (exactCount=1, exactCount=1 plus
that specific). Users stuck at None/None could not return to an
unfiltered pair.
Drop the UI normalization. The callback keeps only the eldritch
side-effect it was carrying. All pair combinations now flow through to
resolveInfluenceQueryState as intended.
Same specific on both sides (Shaper/Shaper) is redundant at the item
level, so resolveInfluenceQueryState treats the second slot as None:
the pair now generates the same query as Shaper/None (exactly 1 of that
type, pseudo_has_influence capped at 1). Without the None constraint the
duplicate specific would have silently produced a looser query than the
paired form. Test coverage added asserts state equality and query-cost
equality with the paired form.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments