[#500] Release DB ghosts when close is already recorded #548
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/500-release-recorded-ghost"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Production evidence: SOLUSDT short was absent on Bybit, while both exact close order IDs were already persisted in trades. The sync daemon skipped existing order IDs before validating side, timestamp and quantity, then preserved the missing DB position indefinitely. This change treats an exact existing close row as completion evidence after full validation, avoids duplicate trade writes, and allows normal DB removal. No signal, budget, pause, stop-limit or trade-frequency controls are changed. Verification: 65 targeted tests passed; gitleaks diff scan clean; GitNexus impact LOW.