Persist stop lifecycles with shared SQLite and PostgreSQL migrations

.github/workflows/tests.yml

@@ -2,7 +2,7 @@ name: tests
 
 on:
   push:
-    branches: [main]
+    branches: [main, codex/order-lifecycle-storage]
   pull_request:
 
 jobs:
@@ -49,3 +49,32 @@ jobs:
           out=$(env -i HOME=/tmp/norust-home PATH=/usr/bin:/bin /tmp/norust/bin/python -m pip install --no-deps dist/*.tar.gz 2>&1 || true)
           echo "$out" | tail -20
           echo "$out" | grep -q "sh.rustup.rs" || { echo "the install-Rust message did not appear"; exit 1; }
+
+
+  postgres:
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres:18
+        env:
+          POSTGRES_DB: synpath_test
+          POSTGRES_PASSWORD: postgres
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U postgres -d synpath_test"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - run: pip install -e ".[dev,postgres]"
+      - name: PostgreSQL journal, recovery and mocked venue contracts
+        run: pytest -q tests/test_postgres_storage.py tests/test_owner_migrations.py tests/test_routed_execution_scope.py tests/test_routed_scope_transactions.py tests/test_routed_audit_pagination.py
+        env:
+          SYNPATH_TEST_POSTGRES_DSN: postgresql://postgres:postgres@localhost:5432/synpath_test

README.md

@@ -204,10 +204,12 @@ async with KalshiTrading(require("kalshi", creds)) as kalshi, \
 **REST server**
 
 ```bash
-python -m synpath.server                           # http://127.0.0.1:8000/docs
+python -m synpath.server                           # http://127.0.0.1:8000/docs, no auth: keep it on localhost
 curl "localhost:8000/venues/kalshi/markets?limit=1"
 ```
 
+`synpath serve` runs the same routes (batch reads and search included), plus live books at `/ws/market` (a bucket's merged book too, with a router preview at `/trading/buckets/{id}/plan`) and Synpath's hosted matching and tick history at `/matching` and `/history` (with serve's own Synpath API key), behind its access token; see [docs/server.md](docs/server.md).
+
 Trading has its own app, with per-account keys and an append-only audit log:
 
 ```bash
@@ -252,3 +254,10 @@ secret.
 ## License
 
 MIT
+
+
+Experimental execution storage on `codex/order-lifecycle-storage` supports SQLite
+(default) and explicitly configured PostgreSQL, with one active execution worker.
+See [engine README](synpath/engine/README.md) for configuration, recovery and test
+coverage. Terminal integration and remaining live venue guarantees are tracked
+separately; this experimental branch stays unmerged.

docs/api.md

@@ -151,6 +151,12 @@ Because results are ranked by relevance, paging deep into a large result set
 is best effort. To enumerate every market, walk `fetch_markets()` without a
 query.
 
+Over HTTP, `synpath serve` answers one venue's search at
+`GET /venues/{venue}/markets?query=`, and several venues' at once at
+`GET /search/markets` and `GET /search/events`, each venue's page reported
+separately; `GET /markets?ids=` and `GET /books?ids=` are the batch reads
+([server](server.md#batch-reads-and-search)).
+
 ### Sort
 
 `volume`, `liquidity` or `newest`, on every venue -- but not the same way on
@@ -241,6 +247,11 @@ synpath.match_event("kalshi:KXHIGHTATL-26SEP23")
 #            events={"polymarket": ["polymarket:1003798"]})
 ```
 
+`synpath serve` makes these calls for its clients, with its own key, at
+`GET /matching/market`, `GET /matching/event` and (the hosted cross-venue
+scan) `GET /matching/arbitrage`; tick history is at `GET /history/...`
+([server](server.md#hosted-services-matching-and-tick-history)).
+
 ### Status
 
 One vocabulary, one meaning per word, on every venue.

docs/capabilities.md

@@ -221,7 +221,10 @@ onboarded firms.
 | `fetch_settlements` | yes | yes, from the redemption activity | yes | no | no | no | no | no | no |
 | `fetch_queue_position` | yes | no | no | no | no | no | no | no | no |
 | `fetch_fee_estimate` | yes | yes | yes | yes | yes, from the fee contract, 0.25 USDT minimum | yes, the closing charge; opening fills pay nothing | yes, `rate * min(p, 1 - p)` a share | yes, the venue's buy-fee curve on the token bought | yes, 1% of a winning taker bet's profit |
-| `rfq` | yes | no | no | no | no | no | no | no | no |
+| `rfq` | yes; the older key, kept one release: the typed methods below | no | no | no | no | no | no | no | no |
+| `rfq_taker` | yes; two-sided RFQs by contracts (`contracts_fp`) or USD (`target_cost_dollars`), accept with `worst_price` (buy YES sends `accepted_side=no`) | yes; combo RFQs, one side of the combo's YES: buy by pUSD, sell by shares; accept signs an Exchange v3 order, refused on `worst_price` before signing; Deposit Wallet, proxy or Safe only (EOAs refused) | yes; two-sided RFQs by contracts or USD (`cashOrderQty`), accept with `worst_price` | no | no | no | no | no | no; no API requests a parlay (a bettor asks on sx.bet) |
+| `rfq_quoter` | yes; quote (`yes_bid`/`no_bid`), cancel, confirm (30 s, 3 s on combos); replace is cancel then send | yes; requests over the quoter WebSocket (400 ms window), quotes as signed Exchange v3 orders over REST, cancel, confirm (1 s last look, venue opt-in); replace is cancel then send | yes; quote, replace, cancel, confirm (3 s last look) | no | no | no | no | no | yes; parlay requests from `parlay_markets:global`, a quote is signed orders on the parlay market expiring with it (60 s); cancel, replace (cancel then send); no last look, so no confirm |
+| `combos` | yes; multivariate collections, create (5,000 a week) and fetch by `KXMVE…` ticker, no read-only lookup by legs | yes; RFQ-only: no create or lookup at the venue; `create_combo` is offline (a provisional id until an RFQ names `combo-<condition_id>`), legs from the public catalogue | yes; create (idempotent) and fetch by symbol, no read-only lookup by legs | no | no | no | no | no | yes; a parlay market and its legs, fetched and looked up among the requests heard; none created through the API |
 | `split_merge` | no; contracts are not tokens | partial: Deposit Wallets and EOAs | no | no | no | no | no | no | no |
 
 Order types are a separate question. A venue holds `limit` and `market`;
@@ -256,12 +259,15 @@ Every stream answers the `watch_*` keys the same way
 | `LimitlessUserStream` | no | no | no | no | yes | yes | no | no |
 | `SxBetMarketStream` | yes | partial | yes | yes | no | no | no | no |
 | `SxBetUserStream` | no | no | no | no | yes | yes | no | no |
+| `SxBetParlayStream` | no | no | no | no | no | no | no | no |
 | `BetfairMarketStream` | yes, best offers to 10 levels | partial: top of book | no: no public trades | yes, per runner | no | no | no | no |
 | `SmarketsMarketStream` | partial: polled from REST quotes, every 5 s by default | partial: polled | no: read the recent tape with `fetch_trades` | partial: polled every few rounds | no | no | no | no |
 
 The exchange API's other gRPC streams carry one thing each and say so:
 drop copy and trade capture carry fills, position and position-change carry
 positions, instrument state carries market status, and the balance ledger
-carries account movements as venue events.
+carries account movements as venue events. `SxBetParlayStream` carries
+parlay requests (`parlay_markets:global`) as `parlay_request` venue events,
+each with the request as an incoming `Rfq`.
 
 ---