Split bot dashboards and bound log recovery

[KillariDev]

Summary

• Split the arbitrager and liquidator dashboards into route-backed pages, place lifecycle and transaction tables on full-width rows, and force external links into new tabs.
• Apply signer, RPC, network, quorum, and market-source preferences live at scan boundaries without restart prompts; show the effective REP allowlist and simplify operator copy.
• Bound default log reads to the newest configurable 256 blocks, add newest-first optional historical synchronization with durable chunks and exact failing ranges, and distinguish dashboard availability from operator capability.
• Persist arbitrager scan progress only after complete evaluation cycles and add durable liquidator per-operation recovery cursors.

Runtime safety

Initial connectivity setup now persists immediately but keeps the active network, market chain, and RPC pool unchanged until one scan boundary applies them atomically. Source and lookback changes clear incompatible market evidence and report scan state before evaluation resumes.

Screenshots

Arbitrager overview

Arbitrager markets

Manual QA also covered arbitrager and liquidator operations/settings routes at 1440x900 and 390x844, including liquidator log-sync and staged-recovery states.

Validation

• bun run tsc
• bun run ensure-contract-artifacts && bun run check:shared-dependencies && bun run test:run -- --bail=1 — 2,942 passed, 16 intentional external/mainnet-fork skips, 0 failed
• Arbitrager suite after final review fixes — 380 passed, 0 failed
• Focused connectivity, configuration, execution-state, and dashboard regressions — 29 passed, 0 failed
• bun run format:check
• bun run check
• bun run check:changed
• bun run knip
• bun run check:generated-clean
• git diff --check

The full suite had one transient Bun EEXIST: epoll_ctl loader error on its first post-sync run. The affected installer file passed 3/3 in isolation, and the complete rerun passed with the totals above.

Review

• Visual review: 98/100, no findings
• Documentation review: 100/100, no findings
• Final review after fixes: 99/100, no findings

The branch is current with origin/main.