Repository navigation
v0.24.0 — the escape hatch's width bug is now measured in production, and the build pill tells the truth
Nothing about how the bot trades changes in this release. The escape hatch still fires on exactly the rule it always has.
- The escape hatch has a real width bug, and it is now being measured. It arms on a fraction of range depth, so the trigger price moves with how wide the range is — −26.4% on a 40%-deep range, −19.3% on a 30%-deep one, −8.8% on a shallow one. The fix (absolute drawdown from entry) is built but switched off: replayed against the book it changes 14 of the 96 positions the current rule reproduces faithfully — four carried by a single row, and ten are real escapes where no recorded data can say what holding would have done. The bot now logs an
escape_absolute_deferreddecision whenever the two rules disagree, so a week of live data decides instead of a backtest. - New config keys, all inert by default — back-filled into your existing
data/config.tomlautomatically, no action needed:escape_hatch_absolute = false,escape_hatch_drawdown_pct = 26.4,escape_hatch_recovery_drawdown_pct = 12.0. - The dashboard build pill and Changes tab were showing the wrong release. The deploy watcher fetched branch refs but never tags, so
git describestayed frozen at clone time — staging reportedv0.22.0whilemainwas two releases ahead. Fixed. Action: existing checkouts need onegit fetch --tagsto catch up; the watcher keeps them current after that. npm run simcan overlayescape_hatch_absoluteto replay either form of the hatch.- New:
RANGE-WIDTH-DECISION.md— a pre-registered rule for testing a narrower range, written before the data exists. The widely-shared −75% argument does not survive this book: 0 of 176 closed positions ever traded that deep, and 12 of the 13 that passed −50% had already been closed by P0/P1.