Cardano Updates

Use a short mktemp directory under /tmp for the Linux Memory Benchmark before running the existing benchmark command. This avoids the cardano-node Unix socket path limit while keeping other benchmark jobs on runner.temp.

Ignore local llm review artifacts and remove the tracked llm review file inherited from the rebased base so the repository keeps llm out of tracked source.

Verification: actionlint accepted linux-benchmarks.yml with repository custom runner-label warnings ignored. The representative issue path is 120 bytes, and the new representative socket path is 94 bytes.

Live verification: Linux Benchmarks workflow dispatch 25724369765 passed end to end and uploaded memory-bench-results.csv, memory.hp, memory.svg, memory.log, and memory.error.log.

Fixes #5283

Closes #5278.

Reworks `.github/workflows/restoration-benchmarks.yml` so every
restoration benchmark run starts from a fresh Mithril-provisioned node
database instead of relying on whatever the self-hosted runner happens
to have on disk. Each matrix leg (`base`, `seq0`, `seq1`, `rnd5`) gets
an isolated node DB so legs can run in parallel without sharing mutable
state. Mithril download/extraction/node startup/sync are timed and
logged separately from the wallet restoration benchmark.

## Status

Draft. Only the feature spec is in so far
(`specs/005-mithril-bench-snapshots/spec.md`). Plan, tasks, and
implementation follow as separate commits on this branch.

Support exporting and importing snapshots

  - Add TxLevel TopTx arg to Tx/TxBody throughout (new kind parameter)
  - Fix hashScriptIntegrity: move to Cardano.Ledger.Alonzo.Tx, use ScriptIntegrity record
  - Replace dsUnifiedL/raCredential with accountsL/addAccountState/AccountAddress
  - Fix ApplyTxError (now data family ConwayApplyTxError), TxSubmitResult constructors
  - Add ConwayEraOnwardsDijkstra catch-all cases
  - Replace deprecated ppMinFeeAL/ppMinFeeBL with ppTxFeePerByteL/ppTxFeeFixedL
  - Move RewardAccount import to Cardano.Ledger.Address (pattern synonym)
  - Add Peras fields (NoPerasEnabled) to Bound/EraParams record constructions
  - Replace throwErrorAsException with throwIO (ErrorAsException e)
  - hydra-plutus: remove GADTs from default-extensions, add NoPolyKinds per-file, bump target-version to 1.1.0

Signed-off-by: Sasha Bogicevic <[email protected]>

v1's iserv-proxy-interpreter.override added `--ghc-option=-optl-static
--ghc-option=-optl-ldl` (and `-optl-no-pie` on aarch32) via
`setupBuildFlags` so the cross-compiled binary is self-contained
— necessary because qemu-user-mode on the build host can't
satisfy Android's dynamic loader (`/system/bin/linker64` /
`/system/bin/linker`).  v2 ignores `setupBuildFlags`, so the
slice's binary came out dynamically linked and qemu refused to
launch it with
`qemu-aarch64: Could not open '/system/bin/linker64'`, breaking
cross-TH for any package that touched iserv on android.

Express the same flags in the iserv-proxy project's
cabalProjectLocal under `if os(android)`.  plan-nix now records
them in the slice's UnitId-relevant configure-args, so the
slice's cabal v2-build picks them up — same outcome as v1.

Use a short mktemp directory under /tmp for the Linux Memory Benchmark before running the existing benchmark command. This avoids the cardano-node Unix socket path limit while keeping other benchmark jobs on runner.temp.

Ignore local llm review artifacts so they do not enter the repository.

Verification: actionlint accepted linux-benchmarks.yml with repository custom runner-label warnings ignored. The representative issue path is 120 bytes, and the new representative socket path is 94 bytes.

Live verification: Linux Benchmarks workflow dispatch 25724369765 passed end to end and uploaded memory-bench-results.csv, memory.hp, memory.svg, memory.log, and memory.error.log.

Fixes #5283

Signed-off-by: Eric Torreborre <[email protected]>

v2 builder's slice cabal v2-build doesn't consume v1's
`setupBuildFlags`, so the cross-TH iserv ghc-options
(`-fexternal-interpreter -pgmi <qemu-wrapper>` etc.) never reached
the cross GHC and slices for packages with TH (e.g. th-orphans,
th-lift) failed with "Couldn't find a target code interpreter.
Try with -fexternal-interpreter" on aarch64-android-prebuilt,
aarch64-multiplatform, and other linux-cross targets.

Mirror `overlays/mingw_w64.nix`'s `wrapGhc`: a derivation that
`--add-flags`-wraps every ghc / ghci binary with the linux-cross
`ghcOptions` (already used by v1 via `setupBuildFlags`).  Cabal
still sees the unwrapped `ghc --info` output (compiler-id, target
platform, capabilities) so UnitId hash inputs are unchanged and
plan-nix's recorded UnitIds keep matching the slice's
computation.  Other GHC binaries (`ghc-pkg`, `hsc2hs`, `runghc`,
`haddock`, …) are symlinked through unchanged.

The v2 comp-v2-builder already consumes
`templateHaskell.wrapGhc` when set (see `sliceGhc`), so wiring
this through is purely additive — windows already had it.

v2 splits v1's monolithic `.dwarf` overlay into two pieces:
  * `debug-info:` in cabal.project for DWARF in the user's source
    (plan-nix records it → matching UnitIds).
  * `compilerSelection` swap to `c.dwarf` for DWARF in the RTS /
    `ghc-internal` (every plan/slice/dummy-ghc derives from the
    same GHC, so UnitIds stay consistent).

  * `docs/dev/debug-info.md` — parallel to docs/dev/profiling.md.
  * `builder/comp-v2-builder.nix` — `.dwarf` now throws with both
    knobs in the migration hint and a pointer to the new doc.
  * `test/cabal-simple-debug/default.nix` — uses both knobs and
    queries `.exePath` instead of `.dwarf.exePath`.

Update 2026-05-11--project-committee-meeting.md