Add Rust wasm target, trunk, and Bevy-class native build libs to the full dev-base tier #610

New issue

Closed

opened 2026-07-21 03:47:40 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-21 03:47:40 +00:00

Member

Follow-through on #382 and prep for the factory-game Bevy/Wasm shell (coilyco-gaming/factory-game-v3#18).

Findings from the current published family:

Rust landed in core via #382, but the outcome comment pointed downstream at v0.230.0 - that tag was cut from e69540e, which predates the rustup commit (3badc26). The first release actually containing Rust is v0.243.0. factory-game-v3 has been pinned to the Rust-less v0.230.0 for 11 days, which is the whole cause of its red main (coilyco-gaming/factory-game-v3#24).
agentic-os:v0.254.0 (current latest, full tier) verifies clean: cargo/rustc 1.97.0 on PATH. But rustup target list --installed shows only the host triple - no wasm32-unknown-unknown - and there is no trunk.
The planned Bevy/Wasm shell needs: wasm32-unknown-unknown for the Wasm build, trunk for static-site packaging, and the Bevy-class native build libraries (libasound2-dev, libudev-dev, pkg-config) so cargo test --workspace with a Bevy dependency compiles natively in CI instead of going red the moment the shell crate lands.

Implementation:

All three additions go in the full tier only. full is the fan-in default surface that downstream CI and warded engineer containers pull, and keeping wasm/game tooling out of core preserves the lean lower tiers and the family build cache (no core layer invalidation).
trunk pinned as a prebuilt release binary (v0.21.14, trunk-<arch>-unknown-linux-gnu.tar.gz), reusing the existing /tmp/arch.env triple spelling.
rustup target add wasm32-unknown-unknown with the same world-writable chmod parity core applies to the rustup tree.
Docs updated where the tier inventory lives.

Acceptance criteria:

Repo validation passes.
The change lands on main and the automatic release publishes a new family tag.
The new full image verifies: trunk --version, rustup target list --installed includes wasm32, and the alsa/udev dev libs resolve via pkg-config.
Downstream follow-up: bump factory-game-v3 CI to the new tag and confirm its main goes green (tracked in coilyco-gaming/factory-game-v3#24).

Follow-through on #382 and prep for the factory-game Bevy/Wasm shell (`coilyco-gaming/factory-game-v3#18`). Findings from the current published family: * Rust landed in `core` via #382, but the outcome comment pointed downstream at `v0.230.0` - that tag was cut from `e69540e`, which predates the rustup commit (`3badc26`). The first release actually containing Rust is `v0.243.0`. `factory-game-v3` has been pinned to the Rust-less `v0.230.0` for 11 days, which is the whole cause of its red main (`coilyco-gaming/factory-game-v3#24`). * `agentic-os:v0.254.0` (current latest, full tier) verifies clean: cargo/rustc 1.97.0 on PATH. But `rustup target list --installed` shows only the host triple - no `wasm32-unknown-unknown` - and there is no `trunk`. * The planned Bevy/Wasm shell needs: `wasm32-unknown-unknown` for the Wasm build, `trunk` for static-site packaging, and the Bevy-class native build libraries (`libasound2-dev`, `libudev-dev`, `pkg-config`) so `cargo test --workspace` with a Bevy dependency compiles natively in CI instead of going red the moment the shell crate lands. Implementation: * All three additions go in the `full` tier only. `full` is the fan-in default surface that downstream CI and warded engineer containers pull, and keeping wasm/game tooling out of `core` preserves the lean lower tiers and the family build cache (no core layer invalidation). * `trunk` pinned as a prebuilt release binary (`v0.21.14`, `trunk-<arch>-unknown-linux-gnu.tar.gz`), reusing the existing `/tmp/arch.env` triple spelling. * `rustup target add wasm32-unknown-unknown` with the same world-writable chmod parity `core` applies to the rustup tree. * Docs updated where the tier inventory lives. Acceptance criteria: * Repo validation passes. * The change lands on `main` and the automatic release publishes a new family tag. * The new full image verifies: `trunk --version`, `rustup target list --installed` includes wasm32, and the alsa/udev dev libs resolve via pkg-config. * Downstream follow-up: bump `factory-game-v3` CI to the new tag and confirm its main goes green (tracked in `coilyco-gaming/factory-game-v3#24`).

coilyco-ops referenced this issue from a commit

2026-07-21 03:51:41 +00:00

feat(dev-base): add wasm target, trunk, and native game-build libs to full (closes #610)

coilyco-ops closed this issue

2026-07-21 03:51:41 +00:00

coilyco-ops referenced this issue from a commit

2026-07-21 03:59:01 +00:00

fix: make forgejo rerun tests hermetic and docs fit the layout cap (refs #610)

coilyco-ops referenced this issue from a commit

2026-07-21 04:08:45 +00:00

refactor(dev-base): move Rust into a lang-rust tier as specced (refs #610)

coilyco-ops referenced this issue from a commit