Release pulse#
A Cargo version is not a release plan. CI and docs stay unknown until a plan records them.
| Project | Next release | Plan state | CI / docs | Distribution |
|---|---|---|---|---|
| VFSTool | not planned | unknown | unknown | crates-io, github-releases, aur |
| S3LightFixes | not planned | unknown | unknown | github-releases, aur |
| Morrobroom | not planned | unknown | unknown | github-releases, source |
| greenmote | not planned | unknown | unknown | github-releases, source |
| dream-ini | not planned | unknown | unknown | github-releases, source |
| dream_archivetool | not planned | unknown | unknown | github-releases, crates-io |
| CHIMERA manager | not planned | unknown | unknown | source |
Cross-project campaigns#
| Campaign | State | Next attention |
|---|---|---|
| LLVM / Luau / L3i alignment | blocked | Prove the portable artifact on the intended device/runtime |
| Make the engineering supply chain legible | active | Review lifecycles and the projects without a public repository |
Blockers#
- LLVM / Luau / L3i alignment: Prove the portable artifact on the intended device/runtime — Nobody has run an LLVM-built PortMaster binary on a handheld yet. Link the Actions run, the readelf output and the device test when somebody does.
Plan a release by adding a record to war-room/plans.toml.