From 9b7dee05526bcda28ea906a6265f222714d0e6c0 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Tue, 26 May 2026 13:14:16 +1000 Subject: [PATCH 1/3] template: require Mac + Linux build support Add a Supportability criterion to the prize template requiring submissions to build and run end-to-end on both macOS (Apple Silicon) and Linux (x86_64). The current template is silent on platforms, leading to darwin-only flakes that block Linux reviewers at nix evaluation time. Co-Authored-By: Claude Opus 4.7 (1M context) --- prizes/LP-0000.md | 1 + 1 file changed, 1 insertion(+) diff --git a/prizes/LP-0000.md b/prizes/LP-0000.md index 7293d7e..917a7ee 100644 --- a/prizes/LP-0000.md +++ b/prizes/LP-0000.md @@ -36,6 +36,7 @@ > > **Supportability** — standard requirements (adapt as needed): > - The program is deployed and tested on LEZ devnet/testnet. +> - The submission builds and runs end-to-end on both **macOS (Apple Silicon)** and **Linux (x86_64)**. The demo script must succeed without modification on both platforms from a clean clone. If a component is genuinely platform-bound (e.g. Mach-O install-name fixup), the flake/build system must conditionally skip it on the other platform rather than fail evaluation. > - End-to-end integration tests run against a LEZ sequencer (standalone mode) and are included in CI. > - CI must be green on the default branch. > - A README documents end-to-end usage: deployment steps, program addresses, and step-by-step instructions for interacting with the program via CLI and Basecamp app. From 43819bfcff99c3c4b552a1d1964fca3a3857d467 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Tue, 26 May 2026 13:16:47 +1000 Subject: [PATCH 2/3] template: drop prescriptive how-to, add module-builder requirement - Trim the cross-platform bullet: state the outcome (works on both platforms) rather than prescribing the implementation. The earlier wording told builders how to structure their flake, which isn't the template's job. - Add a new Supportability bullet pointing builders at logos-module-builder + the Logos tutorial. Hand-rolled module flakes are how cross-platform packaging breaks in the first place; the shared builder already handles Mach-O vs ELF correctly. Co-Authored-By: Claude Opus 4.7 (1M context) --- prizes/LP-0000.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/prizes/LP-0000.md b/prizes/LP-0000.md index 917a7ee..a146ff3 100644 --- a/prizes/LP-0000.md +++ b/prizes/LP-0000.md @@ -36,7 +36,8 @@ > > **Supportability** — standard requirements (adapt as needed): > - The program is deployed and tested on LEZ devnet/testnet. -> - The submission builds and runs end-to-end on both **macOS (Apple Silicon)** and **Linux (x86_64)**. The demo script must succeed without modification on both platforms from a clean clone. If a component is genuinely platform-bound (e.g. Mach-O install-name fixup), the flake/build system must conditionally skip it on the other platform rather than fail evaluation. +> - The submission builds and runs end-to-end on both **macOS (Apple Silicon)** and **Linux (x86_64)**. The demo script must succeed without modification on both platforms from a clean clone. +> - Logos Basecamp modules are built with [`logos-module-builder`](https://github.com/logos-co/logos-module-builder) (`mkLogosModule`). > - End-to-end integration tests run against a LEZ sequencer (standalone mode) and are included in CI. > - CI must be green on the default branch. > - A README documents end-to-end usage: deployment steps, program addresses, and step-by-step instructions for interacting with the program via CLI and Basecamp app. From c3269697b1e617ddca51eb5e81b4be89448a0489 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Mon, 10 Aug 2026 11:12:24 +1000 Subject: [PATCH 3/3] template: require module catalog publishing via logos-modules-release-action MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Basecamp modules must be published to a catalog forked from logos-modules-release-base, using logos-modules-release-action to build, verify, and release the .lgx — completing the pipeline started by the logos-module-builder requirement. Co-Authored-By: Claude Sonnet 5 --- prizes/LP-0000.md | 1 + 1 file changed, 1 insertion(+) diff --git a/prizes/LP-0000.md b/prizes/LP-0000.md index a146ff3..2a5f40b 100644 --- a/prizes/LP-0000.md +++ b/prizes/LP-0000.md @@ -38,6 +38,7 @@ > - The program is deployed and tested on LEZ devnet/testnet. > - The submission builds and runs end-to-end on both **macOS (Apple Silicon)** and **Linux (x86_64)**. The demo script must succeed without modification on both platforms from a clean clone. > - Logos Basecamp modules are built with [`logos-module-builder`](https://github.com/logos-co/logos-module-builder) (`mkLogosModule`). +> - Logos Basecamp modules are published to a module catalog: a fork of [`logos-modules-release-base`](https://github.com/logos-co/logos-modules-release-base), publishing releases via [`logos-modules-release-action`](https://github.com/logos-co/logos-modules-release-action). The catalog's `logos-repo.json` URL must be included in the submission so evaluators can install the module through the package-manager UI / `lgpd`. > - End-to-end integration tests run against a LEZ sequencer (standalone mode) and are included in CI. > - CI must be green on the default branch. > - A README documents end-to-end usage: deployment steps, program addresses, and step-by-step instructions for interacting with the program via CLI and Basecamp app.