.github/workflows/release.yml, on a pushed tag v<version> or, as a dry
run, from "Run workflow":
- checks that the tag is v and the version of CMakeLists.txt, and takes
  the notes from the message of an annotated tag of more than one line,
  or else from the section of the version in CHANGELOG.md
  (scripts/ci/release_notes.sh);
- runs build.yml, now also a reusable workflow: the builds, the tests and
  the smoke tests of the three systems, with the existing CI scripts;
- packs the artefacts with scripts/ci/package_release.sh as
  AMORPH-<tag>-windows-x64.zip, AMORPH-<tag>-linux-x64.tar.gz and
  AMORPH-<tag>-macos-arm64.zip, each one folder with the executable, the
  Python post-processing, config.yaml, the OPTIONS files, easy_data.txt,
  the READMEs, the licence and the licences of the libraries linked in;
  it checks that each executable is for its system, and writes
  AMORPH-<tag>-SHA256SUMS.txt;
- uploads the files as an artefact and, for a tag push only, makes the
  GitHub Release of the tag with them.

The builds change for the release: the macOS executable targets macOS 11
(by default it needed the macOS of the runner), and windows_cross.sh puts
the licence of the mingw-w64 runtime, linked into AMORPH.exe, into
dist/windows/licenses.

CHANGELOG.md summarises #1-#11 as version 1.0.0. README.md and README.ru.md:
where to download, what each archive holds and on which systems it runs,
the warnings of SmartScreen and Gatekeeper about the unsigned executables,
and how to release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bzp4ZxiCYqTK1iWnVgomDV