;;; -*- scheme -*-
;;; enum-name-collision fixture: the interface declares `enum S` at its
;;; top AND a second `enum S` inside `behavior`. This is a LEGAL
;;; nested-scope shadow (the behavior body is the inner scope; nearest
;;; wins), so the inner `S` shadows the outer and `S.X`/`S.Y` resolve to
;;; the inner enum. nucleos accepts it, matching dzn's frontend (dzn
;;; parse + wfc emit nothing). dzn's mCRL2 BACKEND, however, crashes on
;;; the name clash (internal codegen bug) and can produce neither an LTS
;;; nor a verify report — so `lts.override.aut` and `verify.override` are
;;; nucleos-self goldens (sanctioned "nucleos handles what dzn's backend
;;; can't"; see memory feedback_no_overfit_to_dzn). The stale dzn
;;; pipeline-failure line is kept in `baseline/verify` for reference.
