max / alloy

todo: add Gram to v0 stack + follow-up cargo-install list; add VM boot test Gram is picked in STACK.md as the graphical editor but isnt in Fedora repos — needs the same multi-stage cargo-install stage as ironbar/anyrun/ wl-screenrec. VM boot test added as a separate follow-up item so the image is verified beyond linting clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-07-04 16:28 UTC

Signed with PGP, not checked

Commit: 26222c96487f17b2404efce9138645203fd2f88d

Parent: 3d81bd7

1 file changed, +5 insertions, -2 deletions

M docs/todo.md +5 -2

			@@ -15,8 +15,10 @@
15	15
16	16		## Follow-up build work
17	17
18		-	- [ ] Multi-stage cargo-install build for the three Rust tools without published Fedora packages: `ironbar` (bar), `anyrun` (launcher), `wl-screenrec` (screen recorder). New `FROM fedora:42 as rust-build` stage runs `cargo install`, then copies binaries to `/usr/local/bin` in the runtime stage.
	18	+	- [ ] Multi-stage cargo-install build for Rust tools without published Fedora packages: `ironbar` (bar), `anyrun` (launcher), `wl-screenrec` (screen recorder), and Gram (graphical editor — Zed fork, larger build). New `FROM fedora:42 as rust-build` stage runs `cargo install`, then copies binaries to `/usr/local/bin` in the runtime stage. Gram may deserve its own stage due to build weight.
19	19		- [ ] Address bootc lint's `/var` warnings — Flatpak install writes to `/var/lib/flatpak` at build time, but bootc prefers `/var` empty at build so systemd-tmpfiles populates at first boot. Options: (a) accept the warnings, (b) move Flatpak installs to a first-boot systemd oneshot instead of build-time, (c) `bootc container lint`'s official escape hatch if there is one.
	20	+	- [ ] Boot the image in a VM (`bootc-image-builder` → qcow2 or ISO) to verify it actually runs as an OS beyond just linting clean.
	21	+	- [ ] Package Alloy-authored config files that STACK.md references but the Containerfile doesn't yet ship: `niri.kdl` defaults, ironbar theme (blocked on ironbar landing), anyrun plugin config (blocked on anyrun), rio config (color palette + kitty-graphics identification), yazi previewer defaults, mako theme, satty defaults, swaylock config, starship prompt.
20	22
21	23		## When distribution starts
22	24
			@@ -56,7 +58,8 @@
56	58		- rio (TOML config, kitty-graphics enabled)
57	59		- Floorp (Flatpak; Alloy `user.js` + `userChrome.css` from `usr/share/alloy/floorp/`)
58	60		- nushell as login shell + starship prompt (`etc/skel/.config/nushell/`); bash unchanged at `/bin/sh` and `/bin/bash`
59		-	- helix (`etc/skel/.config/helix/` — Alloy Flatwhite theme, `EDITOR=hx` set by nu env)
	61	+	- helix (`etc/skel/.config/helix/` — Alloy Flatwhite theme, `EDITOR=hx` set by nu env; TUI editor for $EDITOR contexts)
	62	+	- Gram (graphical editor per STACK.md; needs cargo-install stage — see "Follow-up build work")
60	63		- mpv (`etc/skel/.config/mpv/`)
61	64		- imv (`etc/skel/.config/imv/`)
62	65		- zathura (`etc/skel/.config/zathura/`)