Cardano Updates

Comment-only change. Brings release/1_x_x_hf's mithril entrypoint
in line with release/2_x_x_hf ef4c1e130 so both branches are
byte-identical; documents that /node is a bind mount and the marker
persists across restarts. No behavioural change.

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

Mirror of the 1.x change (release/1_x_x_hf bbfad4fe6). Mithril 2617.0
dropped the v1 backend; v2 refuses to download into a non-empty /node
unless --allow-override is set. Pass the override exactly once (to
migrate a legacy v1 / pre-v2-aware volume) gated on a provenance
marker the script writes itself (/node/.mithril-v2.done) after a
successful download; never override once the marker exists. /node is
a bind mount (${CARDANO_NODE_DIR}:/node) so the marker persists.

Captures the mithril-client exit code (previously discarded) so the
marker is written only on success; the container still exits 0 in the
steady-state "v2 refuses non-empty dir" case so downstream services
gated on service_completed_successfully are not blocked.

Premise (v1->v2 requires a fresh re-download) originates from AI
commit 3a2af2ecb and is not yet build-verified -- no Docker here.

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

Mithril 2617.0 dropped the v1 backend; v2 refuses to download into a
non-empty /node unless --allow-override is set. We need that override
exactly once (to migrate a legacy v1 / pre-v2-aware volume) and never
again, since a permanent override clobbers an already-synced node DB
on every restart.

Gate it on a provenance marker the script writes itself
(/node/.mithril-v2.done) after a successful download:
- /node empty            -> no override (empty dir needs none)
- non-empty, no marker    -> one-time --allow-override (v1->v2)
- marker present          -> never override; keep existing DB

Also captures the mithril-client exit code (previously discarded) so
the marker is written only on success. The container still exits 0 in
the steady-state "v2 refuses non-empty dir" case, so downstream
services gated on service_completed_successfully are not blocked.

Premise (v1->v2 requires a fresh re-download) originates from AI
commit 3a2af2ecb and is not yet build-verified -- no Docker here.

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

--allow-override was added (commit 3a2af2ecb, hard-fork prep) so the
Mithril 2617.0 v2 backend would overwrite an existing /node dir. In
practice that means every container restart clobbers a possibly
already-synced (and ahead-of-snapshot) node DB.

Removing it makes restore idempotent: fresh volume still restores
(empty dir needs no override); on restart mithril-client v2 declines
to overwrite, the entrypoint still exits 0, and the existing DB is
kept. Brings 1.x in line with 2.x (entrypoint now byte-identical).

Re-adding this flag should require an explicit, documented reason —
it forces a destructive re-restore on every start.

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

The mainnet preprod env and the mithril Dockerfile were already on
2617.0, but .env.docker-compose and .env.IntegrationTest still pinned
the temporary 2543.1-hotfix tag, which should not ship for a hard
fork. Aligns all Mithril references to 2617.0.

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

Mithril was only partially backported from 2.x: the .env files were
on 2617.0 but the Dockerfile ARG defaults still built 2537.0, so the
published mithril image would have been mis-versioned. Also drops the
temporary 2543.1-hotfix tag (not suitable for a hard fork) and fixes
a node version ref missed by earlier filename-scoped searches.

- docker/dockerfiles/mithril/Dockerfile + docker/Dockerfile: Mithril
  ARG default 2537.0 -> 2617.0 (mithril Dockerfile now identical to 2.x)
- docs/env-vars.md: documented Mithril version 2524.0 -> 2617.0
- .env.IntegrationTest: MITHRIL_VERSION 2543.1-hotfix -> 2617.0
  (CARDANO_NODE_VERSION kept at 0.0.0 — intentional DevKit sentinel)
- docker/.env.dockerfile: CARDANO_NODE_VERSION 10.5.3 -> 11.0.1
  (all-in-one runtime env, missed before; 2.x has no equivalent)

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

The standalone node image and .env files were already on 11.0.x, but
the monolithic all-in-one docker/Dockerfile was still pinned to 10.5.3
and never received the 11.0.x build fixes — so a bumped all-in-one
image would fail to build/start.

- Bump CARDANO_NODE_VERSION to 11.0.1 everywhere still lagging
  (all-in-one Dockerfile 10.5.3, node Dockerfile 11.0.0,
  test-integration config, docs)
- node/Dockerfile: add ENV LANG=C.UTF-8 + split `cabal build all`
  (UTF-8 Template Haskell fix), matching the 2.x node image
- all-in-one Dockerfile: add liburing/libsnappy/protobuf build deps,
  liburing2/libsnappy1v5 runtime libs, ENV LANG=C.UTF-8, and switch
  the submit-api config to the local trace-dispatcher tx-submit-config
  (prevents the `key "Options" not found` crash on 11.0.x)

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

The h2 env files, test-integration config default, and the
network/options golden fixture were still pinned to 11.0.0 while
the rest of the release moved to 11.0.1. Brings them in line so
all environments use the same node version.

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

Aligns the pinned yaci-store version with the SyncStatusService /
SyncStatus core API (yaci-store #860) that YaciSyncHealthIndicator
was already migrated to.

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