Release v0.1.3 - Fixed out of bounds custom curves issues and added reset to factory settings · TekuSP/SubZeroFramework

What's Changed

Settings → Service: "Reset fan settings to factory defaults". Returns every fan to the controller's
automatic mode and deletes all saved fan settings in one confirmed action — curve profiles in every slot,
the active profile per fan, "Applies to" links, CPU boost, and manual/max overrides — including entries for
fan indices the hardware no longer reports, which no per-fan action could reach. Display units, startup and
alert settings are untouched.

Curve points could be dragged off the chart and stranded there. The editor let a point be parked
outside the plotted temperature window (dragging past the plot edge keeps producing coordinates out in the
axis margin), where it was invisible and could never be grabbed again — the curve became uneditable. Points
now snap into a band inside the visible window, and curves already holding stranded points are pulled back
when they load. Pressing empty chart space also picks the new point straight up, so press-drag places a
point in one motion.
A curve no longer flatlines above its last point. The hidden anchor closing every curve at the top of
the temperature range inherited the last point's duty, so a curve ending at 0 % (or any low duty) held that
speed all the way to 130 °C instead of climbing. It is now pinned to full speed, matching the idle anchor at
the cold end: every curve ramps from idle to maximum across the range, however early the user's own points
stop. The client's drawn curve, its predicted-duty readout, and the service's actuation now share ONE
implementation of that rule (FanCurveDomain), so a preview cannot promise a speed the fan does not deliver.

Full Changelog: v0.1.2-alpha...v0.1.3