Skip to content

fix(binance): release stale owner under bounded preconditions - #275

Merged
Pigbibi merged 1 commit into
mainfrom
fix/binance-release-stale-owner-20260913
Sep 13, 2026
Merged

Pigbibi merged 1 commit into
mainfrom
fix/binance-release-stale-owner-20260913

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Sep 13, 2026

Copy link
Copy Markdown
Collaborator

What changed

Adds an explicit, manually selected release-stale-owner accounting action for the disabled main + reconcile_only Runtime workflow. It can delete only the existing MULTI_ASSET_STATE__owner document after protected account identity, empty open-orders, safe order state, valid ACTIVE_LKG control, and unchanged owner/ledger/control snapshots are confirmed.

The Firestore operation is one max_attempts=1 transaction with owner-only deletion and mandatory readback. Missing owner is read-only already_absent; any precondition change, transaction uncertainty, or readback uncertainty fails closed without retry. No ledger, control, risk, strategy, or execution fields are changed.

Validation

  • PYTHONPATH=. uv run --frozen pytest -q — 901 passed, 91 subtests passed
  • uv run --frozen ruff check scripts/migrate_daily_accounting_state.py tests/test_daily_accounting_migration.py tests/test_runtime_workflow_security.py
  • git diff --check

Co-Authored-By: Codex <noreply@openai.com>
@Pigbibi
Pigbibi merged commit 8dc270e into main Sep 13, 2026
1 check passed
@Pigbibi
Pigbibi deleted the fix/binance-release-stale-owner-20260913 branch September 13, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant