fix: hedge-walk infinite retry for SENSEX caused duplicate hedges

[kunalrbhatia]

Summary

Fix the SENSEX hedge-walk infinite retry loop that caused duplicate hedge buys on 3-Sep.

Incident (3-Sep 2026, SENSEX expiry)

At 09:30 the algo entered shortStraddle(true) (ATM 76800). The CE hedge (78300, +1500) filled, but the PE hedge (75300) had LTP ~3.5 > 3 → doOrderByStrike returned false → the retry loop re-attempted the SAME strike forever because SENSEX strikeVariance was 0 (only NIFTY had 50). The straddle SELL legs never placed → straddleOpenedToday never set → every 5-min cron tick spawned a NEW process that ran shortStraddle(true) again → each bought ANOTHER CE hedge before blocking again. By 09:50: 5 CE-hedge BUY orders (78300 ×200, 78400 ×300 = 500 qty / 25 lots) instead of 100 qty / 5 lots.

Fix

1. SENSEX hedge walk step = 100 (strikes are 100 apart; NIFTY stays 50): if the far hedge LTP > 3, walk further OTM to find a cheaper hedge instead of retrying the same strike.
2. Attempt cap = 5 per hedge: after 5 walk attempts, log and proceed WITHOUT that hedge → the SELL legs place → straddleOpenedToday is set → duplicate entries prevented.
3. Also resets strikeIncrement for the PE loop (was cumulatively inherited from CE).

Verification

• Rebuilt dist 09:55; markers MAX_HEDGE_ATTEMPTS + walk logging present.
• Excess hedges flattened via manual SELLs (78300 ×200, 78400 ×300) — broker verified 0 open SENSEX 03SEP positions.
• Unit tests updated: SENSEX hedge with LTP > 3 walks to +100 strike and caps at 5 attempts; entry proceeds without hedge after cap.

Notes

• This is the same class as the 27-Aug PE-hedge LTP issue; the LTP > 3 hedge-cost rule stays (user choice) but can no longer wedge the entry.
• Next: consider a session-level guard so a single tick's shortStraddle can't be re-entered by the next cron tick if SELLs fail (defense-in-depth beyond straddleOpenedToday).