|
All checks were successful
deploy / deploy (push) Successful in 31s
Proof: Live investigation found the executor could stay disconnected from the solver relay after websocket error without close; relay client now reconnects after error and request timeout covers connection wait. Added regression coverage and npm test passes. Assumptions: Historical relay OK responses were technically accepted and mostly not filled because they were not selected or settled, while the current disconnected relay state was a repo-side runtime bug affecting new submissions. Still fake: Venue-native terminal fill events, fee attribution, realized per-trade PnL, and full inventory-skew strategy controls remain incomplete. |
||
|---|---|---|
| .. | ||
| alert-engine.test.mjs | ||
| alert-notifier.test.mjs | ||
| armed-state-store.test.mjs | ||
| executor-state-store.test.mjs | ||
| funding-observations.test.mjs | ||
| inventory-and-history.test.mjs | ||
| json-state-store.test.mjs | ||
| legacy-schema-compat.test.mjs | ||
| liquidity-state.test.mjs | ||
| liquidity-withdrawals.test.mjs | ||
| operator-dashboard-ui-static.test.mjs | ||
| operator-dashboard.test.mjs | ||
| ops-sentinel-static.test.mjs | ||
| portfolio-metrics.test.mjs | ||
| quote-outcomes.test.mjs | ||
| render_release_manifest_test.py | ||
| repo_deployments_test.py | ||
| runtime-health.test.mjs | ||
| signing.test.mjs | ||
| solver-relay-ws.test.mjs | ||
| strategy.test.mjs | ||
| submission-copy.test.mjs | ||