The slider's track reaches past the tier, and the ticks carry the claim

[JIRPOS]

Release notes

CHANGED: The slider in a filter's range editor now reaches past what your copy of the modifier
rolled, instead of stopping at it. The range the game printed is marked by two ticks on the track,
so it is still clear which numbers are the item's and which are yours, and dragging a little better
or a little worse than the roll no longer means typing.

CHANGED: A row whose modifier rolls a single number gets a real track to drag on, and keeps the
ticks that say so.

CHANGED: A knob released hard against an end grows the track by a quarter of its length rather than
a fifth, so it takes fewer pulls to get somewhere.

Review notes

ADDED: ui::widen_track in ppc_core — the one rule every slider track is built with: half again
either side of the numbers it is drawn around, at least one step at the row's own precision,
rounded outwards.

ADDED: tests/track_test.cpp, which is why the arithmetic sits in ppc_core rather than beside the
ImGui widget.

CHANGED: a published range is what the track is built around rather than where it ends, and the two
ticks are what mark it.

• The tier in hand is the only tier anything we have can name, so a track stopping there made the
  two most useful drags — a bit better than this, a bit worse — impossible without typing. The width
  is a convenience; the ticks are the claim, and they stay on roll_min/roll_max wherever the ends
  get to.

CHANGED: RangeTrack carries tick_lo/tick_hi in place of a published flag, so the ticks are
there from the first frame instead of appearing once the track has been grown.

CHANGED: a tier that rolls a single number keeps its ticks; it used to fall through to the derived
branch and lose them.

CHANGED: the reach's floor is one step at the row's dp rather than a flat 1, which was ten steps
on an attack speed.

CHANGED: a pegged knob grows the track by a quarter of the span it started with rather than a
fifth, measured against the widened track the user can actually see.

CHANGED: docs/roadmap.md records what a per-tier affix table would really cost.

• The Mods table the data build already extracts carries the ladders — grouping its 4,369
  item-domain prefix and suffix rows by stat-key set gives local_physical_damage_+% as eight tiers,
  40–49 through 170–179. What is missing is the spawn weights that decide which ladders can appear on
  the base in hand, without which the union overstates the range.

REMOVED: kDerivedSpread and kDerivedFloor, folded into the single constant.

🤖 Generated with Claude Code