feat: log liq_trade, liq_transfer and liq_event lines from committed events [RAI-3104]

[JuaniRios]

Part of RAI-3104.

The bot now writes liq_trade, liq_transfer, and liq_event log lines from committed events, each with a stable event_id. Item 5 of the RAI-2998 stack, the part that #1695 left out.

Live effect: new INFO lines on three new targets. Dashboard broadcast and trade delivery are unchanged · Risk: low to medium (one extra SQLite read per trade event inside the commit's reactor dispatch, and more log volume) · Ships: with the next bot release, but not before the merge condition below

Merge condition

Switch st0x-event-sorcery and sqlite-es in Cargo.toml back to a released tag before merge. Both pin a git rev of ST0x-Technology/event-sorcery#64 for now, cause that's where Reactor::react_committed lives and it isn't released yet. Order: merge event-sorcery#64, release it (v0.3.2 or whatever it gets), bump the tag here, then merge this. Plus the same conditions as the stack below.

Why

The board (item 6b) needs real trade and transfer rows from the bot instead of the exporter's liquidity-trades and liquidity-transfers logs. Each line needs an id that doesn't change across restarts, so a duplicate is harmless. The id is <aggregate type>:<aggregate id>:<sequence>, and the sequence comes from the event store.

Writing lines from evolve() would re-log everything on every replay. The Reactor trait dropped the sequence, so that needed event-sorcery#64 first.

What

• Broadcaster overrides react_committed. react and react_committed share handle(event, Option<Committed>). Lines only get written with a commit, so replay, hydration, view rebuilds, and the handoff retry path write nothing.
• src/dashboard/event_lines.rs:
  • liq_trade: one line per terminal trade. Fields event_id, id, occurred_at, venue, direction, symbol, shares, status, error, price (Trade.price from feat: carry the fill price on the dashboard trade [RAI-3101] #1693), and usd (shares * price). A venue correction (SourceAttributed) writes the trade again with the new venue.
  • liq_transfer: one line per status change. Fields event_id, kind, id, symbol, direction, amount, status, started_at, and usd. Equity is valued at the symbol's mark when the event commits (empty with no live mark). USDC is valued at its amount. The last status per transfer is kept in memory to skip events that don't change it.
  • liq_event: one line per committed trade or transfer event. Fields event_id, parent (trade or transfer), venue or kind, id, sequence, step, and payload. step and payload have the same shape as the /liquidity-read/.../events endpoints, and those now share the helpers.
  • Every line always has the same fields. A value that isn't known is "".
• New targets in DOMAIN_TARGETS and in the docs/observability.md targets table, plus a section with the full contract.

Decisions

• payload is a JSON string, not a nested object (tracing has no stable nested fields). 6b's detail.js has to JSON.parse it.
• signature and raw values are redacted at any depth in payload. Some events persist a signed mint authorization or a signed tx before it's delivered or broadcast, and those shouldn't sit in Cloud Logging. Tested on the real events.
• Position events get no liq_event: they belong to no trade or transfer.
• I added occurred_at to liq_trade even though the plan didn't list it. The exporter used it as the row time, and a caught-up onchain fill would otherwise show the catch-up time.

Known gaps (honest list)

• At most once. A crash between the commit and the reactor, or a failed entity reload in the reactor (WARN on dashboard with the event_id), loses the line for good.
• Stores built without the Broadcaster write no lines: send_command and the operator paths with their own store (CLI manual transfers, fails, reconciles, clear-pending-burn, and the hedge release). Those events still reach the events table and the event endpoints. Fixing that means routing them through the conductor's stores, so it's a follow-up, not this PR.
• The lines live in the dashboard Broadcaster. Stage 6 retires the dashboard, so it must move them out first.

Proof

• Exact field sets and values for every line type, transfer dedupe (including terminal statuses and Failed to Reconciled), redaction, and USD with and without a mark.
• Through real stores: an onchain fill writes liq_event and liq_trade with OnChainTrade:<id>:1. Then a restart (new store, view rebuild_all, load_entity) writes nothing, and the next command writes :2. Also a failed counter trade, a USDC bridge, a source correction, a Position event (no line), and react without a commit (no line).
• Full cargo nextest run -p st0x-hedge -p st0x-config --all-features: 5350 of 5351 pass. The one failure is the known anvil timing flake in api::tests (a_signed_burn_that_fails_to_record_releases_its_nonce), and it passes alone. Clippy, fmt, and pre-commit are clean.
• Multi-model review (sol, Cursor Grok, composer, flash, opus), 4 passes. Pass 1 found 2 highs (signed material in payloads) plus mediums on transfer dedupe and docs. All fixed. Passes 2 and 3 were lows only, fixed. Pass 4 had one low left (this repo's docs/cqrs.md doesn't mention react_committed yet). I left that for the tag bump, since the upstream docs cover it.
• Not verified: real lines on staging. That needs log_format = "json" and t0.devops#792, which this PR doesn't flip.

[linear-code]

RAI-2998

RAI-3063

RAI-3104

[JuaniRios]

@coderabbitai full review

[coderabbitai]

✅ Action performed

Full review finished.

[JuaniRios]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• test: harden the liq_ store tests and the parity tool [RAI-3146] #1723
• fix: seed the log counts by file length and give them a family [RAI-3145] #1722
• fix: make the collector metrics say how fresh they are [RAI-3144] #1721
• perf: replay the P&L ledger once for all six windows [RAI-3143] #1720
• fix: bound each P&L window refresh without cancelling its report [RAI-3142] #1719
• test: pin each alert's kind to its message [RAI-3141] #1718
• fix: keep the board's dialogs open and add Copy buttons [RAI-3148] #1717
• fix: pin, legend and sort the board's native rows correctly [RAI-3147] #1716
• fix: write opentelemetry's internal logs with one message key [RAI-3140] #1715
• fix: say what was filled on the liq_trade line [RAI-3150] #1714
• feat: restore missing transfer status lines with a sweep [RAI-3139] #1713
• feat: publish the allocation planner's band verdict per chain [RAI-3137] #1712
• feat: grey the USDC ratio while the corridor is off, and tighten the settings family [RAI-3136] #1711
• feat: publish per-chain equity in flight and take the hedged chains from config [RAI-3135] #1710
• fix: wait for the auxiliary supervisor when the bot shuts down [RAI-3134] #1709
• fix: hold the liq_ inventory series when a snapshot event fails to apply [RAI-3133] #1708
• fix: complete the recovery steps and parse-check the shown commands [RAI-3132] #1707
• docs: close the burn nonce before failing a pre-burn USDC transfer [RAI-3128] #1706
• observability: let the liquidity board's log panels read the bot's own lines [RAI-3064] #1697
• feat: log liq_trade, liq_transfer and liq_event lines from committed events [RAI-3104] #1696 👈 (View in Graphite)
• feat: log a typed kind on every operational alert [RAI-3103] #1695
• feat: flatten console JSON so the alert text stays at message [RAI-3102] #1694
• feat: carry the fill price on the dashboard trade [RAI-3101] #1693
• observability: show each liquidity row's recovery commands in its detail dialog [RAI-3100] #1692
• observability: open a detail dialog from each liquidity trade and rebalance row [RAI-3099] #1691
• observability: show the liquidity inventory as per-chain Grafana tables [RAI-3098] #1690
• observability: give every liquidity board tab the SPA header and recovery guide [RAI-3097] #1689
• feat: show the SPA's recovery commands for the operations client [RAI-3096] #1688
• observability: let the liquidity boards read liq_ from the exporter or the bot [RAI-3095] #1687
• feat: publish the liq_ pending-order and Raindex series from the bot [RAI-3094] #1686
• feat: publish the liq_pnl_* windows from the bot every 5 minutes [RAI-3093] #1685
• refactor: share the /pnl report path so other callers build the same report [RAI-3092] #1684
• feat: count error and warning logs natively for liq_ reliability [RAI-3091] #1683
• feat: publish the liq_ performance families from the bot [RAI-3090] #1682
• feat: count dependency calls and order-fill polls natively [RAI-3089] #1681
• feat: publish liq_ prices and exposure and refresh the inventory every 60 s [RAI-3088] #1680
• feat: publish per-chain inventory and USDC corridor liq_ series [RAI-3087] #1679
• feat: publish the liq_ inventory series on every inventory write [RAI-3086] #1678
• feat: publish the liq_* foundation families from the bot [RAI-3085] #1665
• feat: add the liq_* parity comparison tool [RAI-3084] #1674
• observability: pin liq_ board queries to the exporter job and fix process start [RAI-3083] #1673
• master

---

How to use the Graphite Merge Queue

Add the label add-to-gt-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.