Cardano Updates

Bumps the default sync grace window from 100 to 200 slots across env files,
Spring config, Helm values, and docs. The previous value caused the synced
flag on /network/status to flap when the HTTP link between rosetta-api and
yaci-indexer was briefly unstable.

Enriches the logs in YaciHttpGatewayImpl for both getStakeAccountRewards
and getDiscoveredPeers: non-2xx branches now include the target URL and
response body alongside the status code, and IOException/InterruptedException
branches include the URL plus the exception (full cause chain) so SSL and
connection errors are visible in the logs.

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

  cardano-node 10.7.x peer-snapshot format

  cardano-node 10.7.x dropped the legacy
  "domain" relay field — all relay
  addresses (both hostnames and IPs) now use
  the "address" key. The port
  field is also optional in the new format.

  - Detect relay type (domain/IPv4/IPv6) by
  inspecting the address value
    instead of checking for a non-null
  "domain" field
  - Default port to 3001 when the relay entry
  omits the port field
  - Retain "domain" field handling for
  backwards compatibility with
    older snapshot formats

Drops an /etc/apt/apt.conf.d/99-retries file into every ubuntu:24.04
stage before the first apt call:

  Acquire::Retries "5";
  Acquire::http::Timeout "30";
  Acquire::https::Timeout "30";
  Acquire::http::No-Cache "true";

Motivation: docker compose builds on shared hosts have been hitting
"File has unexpected size" errors from security.ubuntu.com when a
mirror edge is mid-sync. Retries + No-Cache let apt transparently
re-fetch from a fresh mirror instance instead of failing the whole
build. Does not help when the mirror is serving a permanently-wrong
file (nothing does), but cleans up the common transient case.

Applied to:
- api/Dockerfile                          (build-common)
- yaci-indexer/Dockerfile                 (build-common)
- docker/dockerfiles/mithril/Dockerfile   (cardano-builder + mithril-runner)
- docker/dockerfiles/node/Dockerfile      (cardano-builder + node-runner)
- docker/dockerfiles/postgres/Dockerfile

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

Drops an /etc/apt/apt.conf.d/99-retries file into every ubuntu:24.04
stage before the first apt call:

  Acquire::Retries "5";
  Acquire::http::Timeout "30";
  Acquire::https::Timeout "30";
  Acquire::http::No-Cache "true";

Motivation: docker compose builds on shared hosts have been hitting
"File has unexpected size" errors from security.ubuntu.com when a
mirror edge is mid-sync. Retries + No-Cache let apt transparently
re-fetch from a fresh mirror instance instead of failing the whole
build. Does not help when the mirror is serving a permanently-wrong
file (nothing does), but cleans up the common transient case.

Applied to:
- api/Dockerfile                          (build-common)
- yaci-indexer/Dockerfile                 (build-common)
- docker/dockerfiles/mithril/Dockerfile   (cardano-builder + mithril-runner)
- docker/dockerfiles/node/Dockerfile      (cardano-builder + node-runner)
- docker/dockerfiles/postgres/Dockerfile

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

Client feedback: on most Rosetta chains decimals is a native, mandatory
field on every asset — and on Cardano we need to enrich it via assets-ext
even when the rest of the token-registry metadata isn't exposed. So the
flag shouldn't gate DB access; it should gate only the extra enrichment
fields in currency.metadata.

New wire contract:
- currency.decimals              — always populated (CIP-26/CIP-68 value or 0 fallback)
- currency.metadata.policyId     — always populated
- currency.metadata.{subject,name,description,ticker,url,logo,version}
                                 — only when TOKEN_REGISTRY_ENABLED=true

Code changes:
- TokenQueryServiceImpl drops the enabled short-circuit and always
  queries the assets-ext tables; mergeMetadata seeds decimals=0 and
  always populates policyId + subject.
- TokenRegistryCurrencyData.decimals back to @Nonnull Integer.
- AccountMapperUtil / TransactionMapperUtils drop the
  getDecimalsWithFallback helper and inline metadata.getDecimals().
- DataMapper injects TOKEN_REGISTRY_ENABLED; when false it emits a
  policyId-only CurrencyMetadataResponse, when true it delegates to
  TokenRegistryMapper for the full mapping. Decimals continues to flow
  to CurrencyResponse.decimals unconditionally.

Tests:
- DataMapperTest gains a TokenRegistryEnabledFlagTests nested class
  covering both flag states and null-metadata input.
- AccountMapperUtilTest and TransactionMapperUtilsTest flip the flag on
  at construction since they assert on enrichment fields.
- TokenQueryServiceTest drops the RegistryEnabledFlagTests class and
  updates the 'nothing found' assertions to match the new contract
  (subject populated, decimals=0).

Env and docs:
- New .env.docker-compose-preview (NETWORK=preview, PROTOCOL_MAGIC=2,
  enrichment + logos on). Allow-listed in .gitignore.
- token-metadata.md rewritten to separate 'decimals always' from
  'enrichment gated'; per-network defaults table (mainnet off,
  preprod/preview on).
- env-vars.md, helm-values.md, kubernetes/deployment.md updated to
  reflect the new semantics.

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

Clients rely on a runtime switch to turn token-registry enrichment on and
off; the assets-ext refactor dropped it. Reintroduce a single flag,
TOKEN_REGISTRY_ENABLED (default false), and route it through
TokenQueryServiceImpl so disabled requests short-circuit to a policyId-only
fallback without hitting the DB.

Also revert the decimals-non-null contract from e5efb3b05: the disabled
fallback now mirrors main (policyId only, subject/decimals null), so the
mergeMetadata path no longer seeds decimals=0. Restored getDecimalsWithFallback
in AccountMapperUtil and TransactionMapperUtils and flipped
TokenRegistryCurrencyData.decimals back to @Nullable.

Stripped the legacy HTTP-era flags (TOKEN_REGISTRY_BASE_URL,
TOKEN_REGISTRY_CACHE_TTL_HOURS, TOKEN_REGISTRY_REQUEST_TIMEOUT_SECONDS)
from every env template, docker-compose, Helm chart, CI workflow, and doc
that still referenced them. Enabled token registry + logo on preprod
(.env.docker-compose-preprod, values-preprod.yaml). Rewrote
docs/docs/advanced-configuration/token-metadata.md to describe the new
DB-backed yaci-store assets-ext flow instead of the removed
cf-token-metadata-registry HTTP proxy setup.

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

update code

update code

fix: validation for payload endpoints max_val_size

update code