Cardano Updates

Signed-off-by: Hyperledger Bot <[email protected]>
Co-authored-by: Hyperledger Bot <[email protected]>
Co-authored-by: Pat Losoponkul <[email protected]>

The ci-runner runs tsx scripts that import the Mesh SDK (core-csl -> whisky
WASM), so it needs --experimental-wasm-modules too — not just the app build.
Move NODE_OPTIONS to the shared base stage. Validated in a Linux container:
`@meshsdk/core-csl` now imports cleanly (was: "does not provide an export named
'js_evaluate_tx_scripts'").

Co-Authored-By: Claude Opus 4.8 <[email protected]>

* Fix global slot in zkapp command

* Fix global slot in payments

The app build (with the WASM-aware production next build) succeeds and the app
starts healthy — but the bootstrap step rebuilds the ci-runner service from the
same Dockerfile, re-running next build (which ci-runner doesn't need; it only
runs tsx scripts) and failing. Split Dockerfile.ci into a base stage (deps +
source) and an app stage (base + build); ci-runner targets base so the
bootstrap runs the real runtime createWallet test against the healthy app.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

Has those functions are in the `WaitContext` we do not need to repeat
`wait_` in their names.

Diagnosing a wedged catch-up against the public Leios dev relay
required grepping across the orphan / fork-mismatch INFO traffic and
inferring the cause from cache state.  Two new WARNs hand the
diagnosis directly to an operator skimming logs:

- **ChainSync ingress contiguity check** in `record_peer_tip`: when an
  arriving header's `prev_hash` doesn't match the previously-announced
  one's hash, log the (block_no, hash) pair on each side and the
  implied skipped-block count.  Throttled per peer
  (`GAP_WARNING_INTERVAL = 10 s`) so a sustained non-contiguous forward
  doesn't flood the log.  This is the direct signal — the WARN fires
  the moment upstream commits the offence.

- **Stuck-validation rollup** in `retry_select_chain`: when validation
  has been frozen for `STUCK_THRESHOLD = 30 s` and some peer offers a
  strictly-better tip, emit one rollup line summarising stuck duration,
  adopted vs best-peer block_no, the count of entries in that peer's
  replay whose parent_hash we don't have locally, and the peer-chain
  size.  Throttled to one fire per `STUCK_WARNING_INTERVAL = 60 s`.
  This covers the general "stuck for any reason" case and stays
  informative when the ingress check has gone quiet under its
  per-peer cooldown.

Both lines were verified against the dev relay: ingress fires within
~30 s of catch-up reaching the wedge boundary (with the exact missing
block hash prefix in the message), and the rollup fires 30 s later
with `unreachable_parent_hashes > 0`, both throttled correctly under
sustained wedge load.

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

The production build's page-data worker (and `next start`) load @meshsdk/core-csl
as a native ESM external, which `import`s whisky-evaluator's WASM-backed exports.
node's ESM loader needs --experimental-wasm-modules to resolve them, otherwise:
`whisky-evaluator does not provide an export named 'js_evaluate_tx_scripts'`.
Set via NODE_OPTIONS so it covers both `next build` and the runtime `next start`.
Validated: the Dockerfile.ci image now builds end-to-end on linux.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

Snarks certificates are significantly slower to run than concatenation
certificates, this lighter scenario will be useful to still keep an e2e
test without taking hours to run.

* implemented a new `MinimalScenario` to validate artifact production
  and signing under minimal configurations
* integrated `MinimalScenario` into the `scenario` module

- `Full` and `RunOnly` Scenarios are now subcommands
- Default scenario to `full`
- Moved `check_client_cli_snapshot_converter` to full subcommand as it's
  only relevant here
- Moved `signed_entity_types` to both full and runonly subcommands
  (note: upcoming "minimal" scenario will only allow one signed entity
  type, this give the flexibility to parametrize that)
- Simplified infrastructure and CLI parsing logic by removing redundant
  arguments.
- Updated `README.md` and CI to reflect changes in Mithril execution
  commands.

Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 6.0.1 to 7.0.0.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/codecov/codecov-action/compare/e79a6962e0d4c0c17b229090214935d2e33f8354...fb8b3582c8e4def4969c97caa2f19720cb33a72f)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/de0fac2e4500dabe0009e67214ff5f5447ce83dd...df4cb1c069e1874edd31b4311f1884172cec0e10)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 6.0.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>