Cardano Updates

  After a deposit snapshot confirms, maybeRequestNextSnapshot fires
  ReqSn(ver=N) immediately for pending L2 txs. With a slow network,
  CommitFinalized arrives and bumps the version to N+1 before the echo
  returns. The stale ReqSn(ver=N) is rejected with ReqSvNumberInvalid
  and nobody re-triggers a fresh request, leaving the head stuck.

  Two-part fix mirroring the DecommitFinalized fix:
  - aggregateNodeState: use LastSeenSnapshot{lastSeen=confirmedSn}
    instead of toLastSeenSnapshot, keeping seenSnapshotNumber at the
    confirmed value so the next ReqSn number is correct
  - onOpenChainIncrementTx: add maybeRequestSnapshotAfterCommit so the
    leader immediately sends ReqSn(ver=newVersion) for pending L2 txs
    after CommitFinalized, instead of waiting for the next timer tick

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

  After a deposit snapshot confirms, maybeRequestNextSnapshot fires
  ReqSn(ver=0) immediately. With a 25s network delay, CommitFinalized
  arrives first and bumps the version to 1. The stale ReqSn(ver=0) echo
  is rejected with ReqSvNumberInvalid and nobody re-triggers ReqSn(ver=1),
  leaving the head permanently stuck.

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

Use Gen.shuffle to vary cert ordering across runs, giving meaningful
random variation now that the test covers multiple cert types with
both Nothing and Just witnesses.

 name = "client-cardano-database-v2" -version = "0.0.17" +version = "0.0.18" * client-cardano-database from `0.1.40` to `0.1.41`
* client-cardano-stake-distribution from `0.1.16` to `0.1.17`
* client-cardano-transaction from `0.1.25` to `0.1.26`
* client-mithril-stake-distribution from `0.2.14` to `0.2.15`
* mithril-metric from `0.1.20` to `0.1.21`
* mithril-aggregator from `0.8.35` to `0.8.36`
* mithril-client-cli from `0.12.43` to `0.12.44`
* mithril-client-wasm from `0.9.12` to `0.9.13`
* mithril-client from `0.13.5` to `0.13.6`
* mithril-common from `0.6.57` to `0.6.58`
* mithril-relay from `0.2.3` to `0.2.4`
* mithril-signer from `0.3.23` to `0.3.24`
* mithril-end-to-end from `0.4.122` to `0.4.123`
* [js] mithril-client-wasm from `0.9.12` to `0.9.13`
* mithril-test-lab/mithril-devnet/VERSION from `0.4.24` to `0.4.25`

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

Extract shared indexCertificatesWith helper that preserves certificates
with Nothing witnesses (non-witnessed certs like ConwayRegCert without
deposit). Previously, all three indexTxCertificates implementations
filtered out Nothing-witness certs, causing mapScriptWitnessesCertificates
in both the legacy and experimental APIs to silently drop them during
fee balancing.

Also replaces the inlined cert-indexing in the experimental API's
mapScriptWitnessesCertificates with a call to indexTxCertificates,
and expands the cert-preservation property test to cover delegation
and registration+delegation cert types.

Fixes #1138

Pay down test coverage debt for Flat serialization instances.
This ensures encoding stability is verified by tests before
we attempt to fix the Generic derivation bug in a follow-up PR.

Adds roundtrip and stable byte encoding tests for:
- Flat library types (Maybe, Either, NonEmpty, Complex, Ratio,
  Set, Tree, Map, Seq, DList, Filler, PreAligned, and
  monoid/semigroup wrappers)
- TPLC types (Version, Name, Kind, DeBruijn, NamedDeBruijn,
  SrcSpan, SrcSpans, DefaultFun, DefaultUni, and all newtype
  wrappers including TyName, Unique, TyDeBruijn, etc.)
- PIR types (Recursivity, Strictness)
- UPLC types (Binder variants, FakeNamedDeBruijn, minimal
  Program encoding)
- Value types (K encodes as ByteString, Quantity as Integer)

Also adds a standalone encoding generator executable
(cabal run flat-encoding-generator) for reproducing expected
byte constants.

  DecommitFinalized aggregate now resets seenSnapshot to
  LastSeenSnapshot{confirmedSn} instead of toLastSeenSnapshot(seenSnapshot).
  This prevents seenSnapshotNumber from advancing to the requested snapshot
  number (which blocked re-requesting), and allows onOpenChainDecrementTx
  to emit a fresh ReqSn with the new version for any pending L2 txs.

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

  After a decommit snapshot confirms, the leader immediately requests the
  next snapshot via maybeRequestNextSnapshot, sending ReqSn(ver=N). If
  DecommitFinalized arrives before the network echo returns, it bumps the
  version to N+1, causing the stale ReqSn(ver=N) echo to be rejected with
  ReqSvNumberInvalid. Since nothing re-triggers a fresh request, the head
  gets permanently stuck in RequestedSnapshot.

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

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

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

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

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