Cardano Updates

Aggregate all nodes' chain trees into a merged view showing fork
structure across the cluster. Each tip displays a badge with the
number of nodes currently on that fork. Shown as a blurred overlay
in the lower-right of the topology graph.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Three fixes for chainsync pipeline stalls found during deep concurrency audit:

1. Iterator rollback signal missed on new iterators (chain/chain.go):
   rollbackLocked() checked iter.lastPoint.Slot > point.Slot, but new
   iterators have zero-value lastPoint. Use startPoint as fallback
   reference so newly created iterators receive rollback signals.

2. Pipeline reader reads currentTip without lock (ledger/state.go):
   ledgerReadChain() read ls.currentTip.Point without RLock, racing with
   concurrent rollbacks. Snapshot under lock and handle FromPoint failure
   gracefully — the outer loop retries after rollback updates the tip.

3. Rollback doesn't wake blocked iterators (chain/chain.go):
   rollbackLocked() set needsRollback but never called
   notifyWaitingIterators(). Blocked iterators would sleep until new
   blocks arrived, stalling indefinitely if connections died after
   rollback.

Also includes defer close(resultCh) and cached batch done-channel fix
from the pipeline deadlock PR.

Signed-off-by: wcatz <[email protected]>

and extract missing data checks into a function analogous to
`missingRequiredDatums` check from Alonzo UTXOW

Three fixes for chainsync pipeline stalls found during deep concurrency audit:

1. Iterator rollback signal missed on new iterators (chain/chain.go):
   rollbackLocked() checked iter.lastPoint.Slot > point.Slot, but new
   iterators have zero-value lastPoint. Use startPoint as fallback
   reference so newly created iterators receive rollback signals.

2. Pipeline reader reads currentTip without lock (ledger/state.go):
   ledgerReadChain() read ls.currentTip.Point without RLock, racing with
   concurrent rollbacks. Snapshot under lock and handle FromPoint failure
   gracefully — the outer loop retries after rollback updates the tip.

3. Rollback doesn't wake blocked iterators (chain/chain.go):
   rollbackLocked() set needsRollback but never called
   notifyWaitingIterators(). Blocked iterators would sleep until new
   blocks arrived, stalling indefinitely if connections died after
   rollback.

Also includes defer close(resultCh) and cached batch done-channel fix
from the pipeline deadlock PR.

Signed-off-by: wcatz <[email protected]>

* Make sure sequencer starts without catchup

* Fix compilation

* Fix test

Signed-off-by: Eric Torreborre <[email protected]>

Display the node's consensus chain tree in the inspector panel as an
SVG diagram of linked blocks. The main chain is shown in blue with the
tip in green; fork blocks appear in orange. Fork blocks share the main
lane when their column is free, and only get their own lane when there
is a collision — descendants inherit their parent's lane.

Backend: add ChainTreeEntry type and ChainTree::snapshot() which walks
backward from the adopted tip for up to 10 blocks, collecting fork
blocks within the window and extending to include fork points. The
snapshot is included in the stats POST to the cluster server and
forwarded to the UI via the stats API.

Cluster: mirror ChainTreeEntry in net-cluster types with serde(default)
for backward compatibility with older net-node binaries.

UI: new ChainTreeView SVG component with auto-scroll to latest blocks.
Integrated into InspectorPanel below the tip display. Dark-themed
scrollbars across all components via MUI CssBaseline overrides.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

`mithril-client` now activate `reqwest/system-proxy` which add
additional system dependencies on windows.

Signed-off-by: Allain Magyar <[email protected]>

Since `ContextError`s are never stored and their reporting doesn't need
to be efficient (we always optimize for the positive case with valid
transactions, as invalid transactions don't propagate through the
network), there's no need for strictness annotations on the error
constructors.

This change removes the bang patterns (!) from:
- AlonzoContextError
- BabbageContextError
- ConwayContextError
- DijkstraContextError

Signed-off-by: Sasha Bogicevic <[email protected]>

As their last versions switched to reqwest 0.13 and they were the last
dependencies that we had that used [email protected]

+ use the default feature in CI instead (which use `rustls`)

+ adapt `mithril-client` lib re-exported reqwest features to the new
  reqwest features set