fix(provably-fair): return 1.01 (not 1.0) for instant-crash — respects the advertised payout floor

[amathxbt]

Bug

When result % 33 === 0, computeCrashPoint() returns 1.0 via an early return:

if (result % 33 === 0) return 1.0;

However, the JSDoc comment and the clamp logic at the bottom of the same function both state the valid output range is [1.01, 100.0]:

// JSDoc: "Result is clamped to [1.01, 100.0]."
if (crashPoint < 1.01) crashPoint = 1.01;

The early return bypasses the clamp and produces a value below the advertised minimum. Players on the losing end of an instant-crash outcome receive a 1.0× multiplier (no winnings) when the published rules imply the worst possible outcome is 1.01×.

Fix

Change the early return to 1.01 so every code path respects the [1.01, 100.0] range stated in the documentation.

// Before
if (result % 33 === 0) return 1.0;

// After
if (result % 33 === 0) return 1.01;