max / alloy

image: build the console into the image The Alloy console was not in the image at all. A distro whose headline surface is its console shipped without one, and the gap was invisible because the Containerfile's own header asserted the policy that caused it ("single-stage, no cargo-built binaries") rather than recording a decision. Adds a `rust-build` stage on fedora:43 — the same base as the runtime stage, so the toolchain and the glibc the console links against are the ones it runs on. Not built on fw13 and copied in: fw13 is Pop!_OS, a different libc, and builds are native per architecture. The dependency graph builds against a stub main before the real source lands, so a console edit rebuilds one crate rather than the whole graph. Measured: 9.5s instead of a full compile. The COPY sits last before the lint, so a console-only rebuild reuses every package and config layer. Adds .containerignore, which did not exist. Every build was tarring output/ — a 3.5GB ISO — into its own build context before reading the first instruction. Two doc corrections found while doing this. IMAGE.md claimed the rust-build stage already existed and held wl-screenrec; it did not, since wl-screenrec was deferred, so there was no stage at all. STACK.md defers wl-screenrec until "a second cargo-built binary shares the stage's cost" — now half true, since the toolchain is paid for but clang and the ffmpeg headers are not. Re-cost it rather than assume it, next time it comes up. Verified: image builds, bootc container lint passes, /usr/bin/alloy is 1.9M and links only libc/libm/libgcc. ISO built and written to USB, readback sha256 matches.