asteria-game: drivers exit 0 on transient not-yet-ready conditions
The Antithesis 1h dispatch on testnets/asteria_game/ surfaced
two "Always: Commands finish with zero exit code" findings on
stub/serial_driver_asteria_bootstrap.sh and
stub/parallel_driver_asteria_player.sh. Decoded composer events:
- bootstrap: t=62.76s rc=1 (6.14s), t=106.5s rc=1 (52s),
t=110.5s rc=1 (55s), t=178.5s rc=0 (3s short-circuit)
- player: t=54.4-54.6s rc=1 (3 fast failures, ~5-15ms each),
t=249.9s rc=0 (3.04s)
The early bootstrap failures hit before the cluster forged its
first block (build/sign/submit fails on protocol-params or
validity-interval errors). The player failures are PlayerMain
calling `error` when seed.json is missing — the parallel driver
fires before bootstrap completes.
Antithesis treats every non-zero exit as an Always-violation,
regardless of subsequent successful fires. This commit makes
both drivers exit 0 on transient "not yet ready" conditions:
- PlayerMain: when readSeed returns Nothing, fire
asteria_player_seed_missing_<id> (sdkUnreachable, already
present) and return cleanly. The next composer fire retries.
- BootstrapMain.runDeploy: catch any exception from
resolveSeed / createAsteria, fire
asteria_bootstrap_create_asteria_deferred (sdkSometimes True)
with the error string, and return cleanly. Subsequent fires
re-derive the same seed (deterministic via seed.json) and
retry — the seed UTxO is preserved when the failure is
pre-submit, and consumed cleanly when the deploy actually
landed (next fire short-circuits via isAlreadyDeployed).
The signals Antithesis cares about — whether the deploy ever
succeeded, whether the singleton invariant held — still flow
through the existing sdkSometimes / sdkAlways assertions. We
just stop using process exit code to encode "world not yet
ready", which Antithesis interprets as a real bug.
