[jackhai9]

Root cause

After a ladder submit, Binance can keep the same controlled quantity input node while restoring its value to empty across multiple React commits. The previous one-recovery-write contract could therefore fail before the form became writable again. This affects all ladder directions, including Close Long.

Changes

• require ladder input values to remain stable before accepting them
• permit bounded, spaced rewrites only while Binance restores the original empty value
• share a strict per-input write budget across synchronization phases
• cancel recovery if the user or page changes the field to another non-empty value
• keep ordinary orderbook input synchronization unchanged
• bump the userscript version to 2.7.136

Validation

• npm test (369/369)
• npm run build:binance-orderbook-trade
• npm run check:binance-orderbook-trade
• git diff --check
• focused trade-form/source regression tests (76/76)
• independent read-only root-cause and final-diff reviews