S11: packaging and release — jlink, AppCDS, man pages, Homebrew and Scoop #15

Part of #17. Design: docs/design.md §7.3.

Scope

• A jlink image per platform (macOS arm64 and x86_64, Linux x86_64 and arm64, Windows x86_64). It includes relix-solver-ojalgo and relix-docs. Picocli and the H2 driver are force-merged in.
• AppCDS archive. The image carries one generated at build time, and the launcher passes -XX:SharedArchiveFile, because each stage of a pipeline pays JVM start-up.
• Man pages and completion scripts, generated from the picocli model and shipped in the archive.
• A release workflow that attaches the archives and their SHA-256 checksums to this repository's GitHub Releases.
• Homebrew and Scoop. The release workflow pushes the new version and checksums to the tap DarkCollective/homebrew-relix and the bucket DarkCollective/scoop-relix.
  • The formula installs the man pages and completions, and its test do block runs a pipeline.
  • The Scoop manifest registers the PowerShell completion.
• Before the first public release:
  • make the tap and the bucket public
  • set their license to Apache-2.0 and their homepage to this repository or the site
  • add the HOMEBREW_TAP_PAT/SCOOP_BUCKET_PAT secrets here

Dependencies

• S9 (S9: management commands — drivers, connectors, doc, help, version, completion #13) for completion.
• The command surface settled (S1–S9).

Acceptance

• Smoke tests run the packaged launcher in a pipe: script on stdin, a catalog in a temp tree, TSV out.
• A test shows the CDS archive is used, by running with -Xshare:on, which fails without it. No wall-clock assertion.
• The man pages render (man -l).
• A dry-run release produces a formula and a manifest whose checksums match the archives.