Fix Sweeping Strikes / Whirlwind threshold config

[tough-griff]

Two related fixes for threshold configuration on the Warrior charge bars (Sweeping Strikes / Whirlwind Stacks).

1. Charge bar showed a threshold overlay when thresholds were disabled

These two powers have no Lua-comparable count, so their threshold coloring is routed through ns.WC_Thresholds and rendered by the engine module as a fill-masked range strip. In UpdateSecondaryResource() that call passed _tsThreshCount unconditionally:

ns.WC_Thresholds(powerType,
    (_tsEntry and _tsEntry.thresholdMode) or sp.thresholdMode,
    _tsThreshCount, _tsR, _tsG, _tsB, _tsA,
    ...)

When the threshold entry is disabled (or a tracked buff is active) the resolver nils _tsEntry, but _tsThreshCount still falls back to the legacy global sp.thresholdCount. HostThresholds then builds a single-band spec from any count > 0, so the strip rendered regardless of configuration. Every other threshold renderer in that function already guards on _tsEntry; this path did not.

Fix: pass the count only when the entry is enabled — _tsEntry and _tsThreshCount or nil. With count nil and no bands, HostThresholds clears the spec and StyleThresholds hides all strips.

2. Threshold input clamped to 10

The count-based threshold input for the class/secondary resource bar clamped to 10, but Sweeping Strikes stacks to 18 with Broad Strokes. Raised the pip/count cap to 20; bar-type (percent/value) and stagger caps unchanged.

Testing

• /reload on Arms Warrior with the Sweeping Strikes secondary bar, thresholds disabled: overlay no longer appears; enabling thresholds still renders the strip.
• Threshold input now accepts values up to 20.

🤖 Generated with Claude Code

[tough-griff]

Before:

After patching EUI with my fix:

[tough-griff]

Added thresholdsstill display correctly:

[tough-griff]

Additionally changed the max value for Threshold from 10 to 20. Since sweeping strikes can stack up to 18 this seemed like a sensible cap.