1.9 KiB
Prompt
Preserve the existing Binance USD-M commit above the reviewed flake/xonsh stack, then add missing deterministic tests and correctness fixes as a separate follow-up with a complete editor-gated commit plan.
Response summary
Hardens Binance feed startup around its supported one-symbol contract, direct websocket routes, current provider schemas, and first-quote readiness. Adds deterministic Binance regressions and separates generic reconnect behavior into its own tested commit boundary.
Files changed
piker/brokers/binance/feed.py- validate feed cardinality, route USD-M stream classes, and declare readiness after either quote class.tests/test_binance.py- cover routes, first-quote startup, cardinality, and documented book-ticker and aggregate-trade schemas.ai/prompt-io/opencode/20260829T175542Z_e09e306a_prompt_io.raw.md- retain the triggering prompt, generated-code summary, and verification output.ai/prompt-io/opencode/20260829T175542Z_e09e306a_prompt_io.md- record structured provenance for the follow-up.
Human edits
The user rejected reconstructing already committed Binance work, required preservation through cherry-pick, selected the flake/xonsh stack base, and required the review fixes to remain a separate tested boundary. The user also corrected the workflow to require an automatic /commit-plan at every stack review gate. During Tuicr review, the user rejected trade-gated startup, requested a feed-specific initialization error and async-generator TODO, and required generic reconnect changes and tests to land independently. The user then clarified that either L1 or trade data must unblock startup, rather than preferring one stream class or waiting independently for both.