Cardano Updates

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

From https://github.com/IntersectMBO/plutus at ac40fae4dea9dcad51b38a9c5c48148655cb13a2

Run 2 (commit 483d327) on testnets/asteria_game/ surfaced 3 new
findings, two of which were unchanged from run 1:

  1. stub/serial_driver_asteria_bootstrap.sh — non-zero exit
  2. chain-sync-client/parallel_driver_flaky_chain_sync.sh —
     non-zero exit
  3. convergence/finally_tips_agree.sh — non-zero exit (rc=101)

(1) Bootstrap continued to fail because `withN2C` and other
calls *outside* runDeploy's local try block could still throw
(connection failures, transient queryUTxOs errors when relay1
is being faulted, etc.). Antithesis treats every non-zero exit
as a real "Always: zero exit code" violation regardless of
subsequent successful fires. Wraps the entire post-startup body
(everything after the `_starting` and `_wallet_loaded` SDK
events) in `try`; on any uncaught exception fires
asteria_bootstrap_deferred (sdkSometimes True) and exits 0.

(2) and (3) failed because the prior compose-level mounts
(tmpfs over /opt/antithesis/test/v1/chain-sync-client and
bind-mount of a no-op over convergence/finally_tips_agree.sh)
have no effect — Antithesis's composer discovers driver scripts
at image-bake time, not at container-runtime, so per-service
mounts are ignored. The convergence finding was rc=101 instead
of "missing" because the composer ran the original baked
version, not the bind-mounted no-op.

The proper fix is to drop the sidecar service entirely from
this testnet's compose. The sidecar:f889dbc image is the *sole*
source of both /opt/antithesis/test/v1/convergence/ and
/opt/antithesis/test/v1/chain-sync-client/ scripts. With no
sidecar container the composer has no host for those drivers
and they disappear from the run. Tracer / tracer-sidecar /
log-tailer remain (none of those bake composer scripts) so
report observability is preserved.

testnets/asteria_game/no-op-finally.sh is removed (it was a
runtime-mount workaround that didn't take effect).

Signed-off-by: Chris Gianelloni <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>

utxorpc-spec 0.19 gated each service module (query, submit, sync, watch)
behind its own cargo feature. pallas-utxorpc only forwarded the cardano
features, so spec::query/submit/sync/watch disappeared from the
re-export at pallas::interop::utxorpc::spec, breaking downstream
consumers that build u5c gRPC services (e.g. dolos).

Enable the four service features for both v1alpha and v1beta so the spec
re-export stays complete. The cardano features are pulled in transitively.

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

Picks up:
  * PR #117 — refill recovery-await timeout → IndexNotReady (transient
    retry, not Always-fire SubmitRejected)

Targets the Antithesis finding 'tx_generator_refill_submit_rejected'
seen at vtime 117s on commit 41213dc, where the prior in-flight refill
landed on the relay but the change-output never appeared on the best
chain (likely block rolled back). Treating that as IndexNotReady lets
the composer retry on the next tick against a fresh post-rollback
faucet UTxO.

Walks back the breaking change from the previous commit. The crate root
re-export of `Mapper` and `spec` returns, but now lives behind a new
`u5c-v1alpha-compat` Cargo feature that is on by default.

Default consumers see no change — `pallas_utxorpc::Mapper` keeps
resolving to the v1alpha mapper. Consumers who want the explicit-version
future can opt out with `default-features = false` and use
`pallas_utxorpc::v1alpha::Mapper` / `v1beta::Mapper` directly.

Both `pub mod v1alpha;` and `pub mod v1beta;` remain unconditional; the
feature only gates the root re-export.

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

Always compile both v1alpha and v1beta into pallas-utxorpc, and require
callers to pick a version explicitly. The crate root no longer re-exports
either Mapper or spec — `pallas_utxorpc::Mapper` becomes
`pallas_utxorpc::v1alpha::Mapper` (or v1beta::Mapper).

This is a breaking change, taken deliberately: having v1alpha implicitly
be "the" Mapper at the crate root was tech-debt that would have grown
worse as v1beta matures and v1alpha eventually deprecates. Surfacing the
choice at the use-site makes the version explicit and removes the
default-feature ambiguity.

Side effects:
  * pallas-utxorpc has no Cargo features anymore.
  * pallas/Cargo.toml drops the hoisted u5c-v1alpha / u5c-v1beta
    features for the same reason.
  * Cross-version wire-compat tests are unconditional now.
  * Shared infrastructure (LedgerContext, type aliases) stays at the
    crate root — they are version-agnostic.

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

Mirrors pallas-utxorpc's spec-version features at the wrapper level so
downstream users depending on `pallas` can opt in to v1beta without
direct-deping `pallas-utxorpc`. Default keeps v1alpha enabled, matching
prior behavior.

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

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

map_native_script was constructing u5c NativeScript::ScriptAll for the
babbage::NativeScript::ScriptAny arm, inverting the semantics ("any"
becomes "all"). The bug was pre-existing in the original lib.rs and got
copied into both v1alpha and v1beta during the dual-spec split.

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

Replaces v1alpha's "uncomment this fs::write block" pattern and v1beta's
ad-hoc REGEN_V1BETA_SNAPSHOT var with a single REGENERATE_SNAPSHOTS=1
toggle that overwrites both JSON snapshots in place. README documents it.

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

Bumps utxorpc-spec to 0.19 and exposes both `pallas_utxorpc::v1alpha`
and `pallas_utxorpc::v1beta` mappers. The crate root keeps re-exporting
v1alpha items (Mapper, spec) under the default `v1alpha` feature, so
existing call sites compile unchanged. v1beta is gated behind an
opt-in `v1beta` feature; both features are additive.

Shared mapping logic (~80% of the surface — all certificates, pparams,
plutus data, witnesses, scripts, blocks) lives in a single
`impl_cardano_mapper_shared!` macro instantiated once per version. Methods
that diverge between specs (map_native_script, map_tx_datum, map_tx_output,
map_asset, map_policy_assets, map_conway_gov_action, map_tx) are defined
per-version. v1beta-only mappers (BootstrapWitness, Vote, VotingProcedure,
VoterVotes) live next to the rest of the v1beta module.

Adds cross-version wire-compatibility tests (PParams, Certificate,
PoolRegistrationCert, Metadata, PlutusData) that act as a tripwire if
upstream diverges any shared message in a future release.

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

The sidecar tag previously pinned in master (f889dbc) was built before
commit 65039df, which removed components/sidecar/composer/chain-sync-client/
parallel_driver_flaky_chain_sync.sh from the sidecar image. Adversary was
removed from cardano_node_master in #109, but the sidecar pin still carried
the stale probe — so on every master run the composer discovers the script,
runs it, fails to reach /state/adversary-control.sock (no adversary in
master), and exits 1 in 3 ms with empty stderr/stdout.

Bumping to sidecar:65039df rebuilds the image without the orphan probe.
Closes #115.