fix(orderbook): stabilize Bollinger markers and chart saves (2.7.198)

[jackhai9]

Summary

Publish the existing orderbook 2.7.198 artifact. This PR contains only the 13 reviewed orderbook files; unrelated Strategy27 changes remain excluded.

• Isolate chart interval sessions and reject stale exports and asynchronous marker results, including rapid A-B-A switches.
• Keep pending markers hidden until current-session publication; retain ownership for deferred cleanup and repair native marker eviction.
• Wait for the native chart model before reading chart resolution or depth geometry.
• Coalesce marker-triggered chart saves and drain pending marker mutations before continuous-save ownership, chart-order toggles, and native cancellation UI.
• Reduce temporary indicator allocations and repeated depth coordinate reads; cooperatively yield marker batches without changing signal thresholds or loaded-history coverage.
• Document observed performance causes, ownership contracts, limits, and diagnostic paths.

Validation

• Independent read-only review: no new functional blockers; targeted 85 tests passed.
• Node 24.16.0 full npm test: 759 passed (current workspace, including separately pending Strategy27 tests).
• Node 22 CI-equivalent orderbook toolchain: 582 passed.
• Playwright deterministic browser suite: 62 passed, no retries.
• Orderbook build: exact pre/post artifact identity; SHA256 a14c081fa0cc94ab0e9841f94aba73897d000c1d52eb19466ccd406dc22612cb.
• Orderbook syntax, release metadata, and git diff checks passed; source/artifact version 2.7.198 and install URLs match.

Live validation boundary

The user reports Tampermonkey version 2.7.198 is already installed. This release does not claim fresh exact installed/loaded-source verification or live Binance UI/performance validation. No browser reload, script synchronization, live order, cancellation, or other financial action was performed during this release.

Known limits

Default save callbacks are deferred only during marker bursts; synchronous return values in that window are intentionally not preserved. Nonstandard intervals sharing native visibility buckets remain subject to TradingView limits. A single native call and synchronous cleanup are outside the cooperative render budget.