feat: ready to submit, a run to watch, the README, the review's fixes

Sprint 08 (roadmap/08. ready to submit.md), the last milestone.

- scripts/watch.sh runs the collector with a live view of its log, stops
  cleanly on Ctrl-C, then checks the output (reconcile) and shows one
  symbol's book as text (show, a new binary).
- The README for the solution, with the final runs: Polymarket through an
  outage it recovered from on its own, Kalshi's demo with two slow
  connections recycled.
- From a review of the whole codebase: Kalshi takes RSA keys too
  (RSA-PSS-SHA256); a slow Kalshi connection takes the hourly recycle's
  next turn, which it nearly never got before; a market tracked again no
  longer fails reconcile; Book::add checks for overflow; usage and --help
  name the key variables; the first scan says how far it got.
- Tests for every gap the reviews found, an offline run of the whole
  orchestrator among them; ShellCheck in CI.
This commit is contained in:
pascal committed 2026-11-12 22:32:39 +01:00
1 parent 515e85941d
commit cf6c16c9cf
35 files changed
+2791 -207

No files matched your search

+8 -2
View File
@@ -48,8 +48,14 @@ _Avoid_: Order book state, depth
**Connection**:
One websocket to the exchange. Every live symbol is subscribed on two
connections, chosen independently of each other.
_Avoid_: Socket (for the concept; fine for the code), stream, lane (the
retired pairing of one connection with one book thread)
_Avoid_: Socket (for the concept; fine for the code), stream (that is one
connection's changes of a symbol), lane (the retired pairing of one
connection with one book thread)
**Stream**:
One connection's changes of one symbol, in the order it delivers them. The
two streams of a symbol carry the same changes, each at its own pace.
_Avoid_: Feed (the book thread's code), using it for the connection
**Load**:
How much a market weighs on a connection: the bytes per second of its frames