Cardano Updates

* `epochInfoRange`
* `startStep`
* `pulseStep`
* `completeStep`
* `lift`

Signed-off-by: Tripura Repalle <[email protected]>

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

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

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

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

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

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

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

Signed-off-by: Akhil Repala <[email protected]>

Apply review feedback from Copilot and @whankinsiv on the
docs/configuration.md, docs/getting-started.md, and README.md changes:

- Fix incorrect TOML types in examples (download-max-age, write-full-cache)
- Update mithril-fetcher pause/stop/profile examples to use
  every-nth-epoch / every-nth-block (matches parser)
- Drop accounts-state spdd-* settings that are not implemented in code
- Remove blockfrost-specific module sections (assets-state, address-state,
  historical-accounts-state, historical-epochs-state, rest-blockfrost)
  from the configuration reference and reorganise README into an
  "API Persistent State" group
- Drop topic-only settings throughout configuration reference for
  consistency
- Clarify config-file paths (cd processes/omnibus) and REST host ports
  for preview (4340) vs mainnet (5340) under Docker Compose
- Note mainnet magic number 764824073
- Drop the unnecessary 'make build' step before make run / cargo test
- Remove the non-existent processes/mcp_standalone entry
- Tidy Genesis Bootstrapper and Snapshot Bootstrapper descriptions

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

Signed-off-by: Akhil Repala <[email protected]>

createCompatibleTx now takes [Exp.TxOut (ShelleyLedgerEra era)] plus an
explicit Map L.DataHash (L.Data ...) for supplemental datums, mirroring
how it already takes Exp.TxCertificates / Exp.TxVotingProcedures /
Exp.TxProposalProcedures. Supplemental datums were previously rescued
out of the legacy TxOut constructor inside convScriptData' and folded
into TxBodyScriptData; Exp.TxOut intentionally does not carry them
(only the hash; the full datum lives in the witness set), so callers
now thread them in explicitly.

Deletes the legacy bridge helpers from Experimental.Tx
(fromLegacyTxOut, legacyDatumToDatum, supplementalDatumFromLegacy,
toLedgerDatum, DatumDecodingError). They existed only to migrate
callers from legacy TxOut CtxTx era; with the Compatible API no longer
accepting that type, the bridges have no remaining callers inside
cardano-api. They were re-exported only via the experimental namespace,
whose stability contract permits breaking changes.

After this change, neither Cardano.Api.Compatible.* nor
Cardano.Api.Experimental.* references OldApi.TxOut / TxOut CtxTx era.
The legacy TxOut ctx era type itself stays in place — UTxO, Tx body
construction, fee/balancing, LedgerState, and Byron all still depend
on it.

CIP-158 was merged 2026-03 and is a sibling CIP-13 extension authority
(adamkdean / @adamKDean). The draft already cited CIP-45 (connect
authority) and CIP-162 (drep authority) as precedents for CIP-13
extensibility; CIP-158 (browse authority) belongs in that list.

Two small additions in the Relationship to CIP-13 section:

  - Family-of-extensions list: add CIP-158 alongside CIP-45 and
    CIP-162, with its grammar and a note that CIP-158 is explicitly
    navigation-only and scopes out signing flows / callback paths
    per its own Rationale.

  - Future minor-revision paragraph: note that the prospective
    web+cardano://cip30dl/v1/... form mirrors CIP-158's grammar
    precedent for the established CIP-13 extension shape.

Public conversation thread on this (Adam Dean raised the comparison
on X; we credit CIP-158's isolation-of-authorities framing back at
him for CIP-30-DeepLink sitting in its own namespace) is linked from
the Discussions: preamble.