Reproducibility package for Failure-aware configuration selection for generalized-multiquadric DRBEM of coupled Burgers equations: residual ranking and compact portfolio transfer

This reproducibility package accompanies the manuscript "Failure-aware configuration selection for generalized-multiquadric DRBEM of coupled Burgers equations: residual ranking and compact portfolio transfer" (EABE-D-26-01280). Version 1.0.0 contains the complete 43-case definition matrix, manufactured fields, coordinates and seeds, 2,580 raw candidate records including failures, nodal states, portfolio construction traces, figure and table recipes, and a pinned Python environment. The revised manuscript and supplement are included with editable Word equations. The release is limited to files supporting the current revision and its reproduction; superseded manuscript copies and unrelated development material are excluded. Download instructions: the verified ZIP is distributed as six byte-preserving parts. Download all six .zip.part files, EABE_D26_01280_Download_Parts.json and assemble_eabe_release.py into one folder, then run python assemble_eabe_release.py. DOWNLOAD_README.txt gives the complete steps. The script verifies every part and the assembled ZIP before extraction. The separate .sha256 file applies to the assembled ZIP. The package provides commands for integrity verification, a bounded smoke test, and full reproduction. The numerical solver and retained results are unchanged from the internally verified C13.5.2 campaign. Fresh verification and a bounded smoke test were completed on 29 October 2026; a new full numerical campaign was not run on that date. Internal verification is distinguished from independent external replication. See README.md and reproduction/RELEASE_VALIDATION.json for scope and commands. Licence scopes: team-owned source code is released under the MIT License; team-created data and documentation are released under Creative Commons Attribution 4.0 International. These licences apply to their respective components, not as alternative licences for every file. Third-party components retain their own licences and credits; see LICENSES.md and THIRD_PARTY_NOTICES.md.