# disk/ QEMU disk images used for Artemis (block-storage VM) persistence testing. Mounted via `Makefile.starkernel`'s `ARTDISK` variable (default `disk/artemis.img`) as a `virtio-blk-pci` device on all three architectures' kernel QEMU boots — not `scripts/rundisk.sh`, which targets a separate, currently-unused `disks/` (plural) directory for the *hosted* VM's `--disk-img=` flag instead. - `artemis.img` — standard Artemis persistence test disk. **Reformatted 2026-08-02**: this image had been stuck in a corrupted state (valid `LithosAnanke` magic header, but data not matching what `ART-READ-TEST` expects) since before this repo's own git history begins (`git log` shows it already broken at the initial commit, carried over from the pre-split monorepo). Chasing down the resulting persistent `FAIL: persist-read` traced to the *data*, not the code — the write→reboot→read round trip works correctly on a fresh image (see `artemis-debug-roundtrip.img` below). Reformatted by blanking the file and letting a normal boot format+write-test it; verified `PASS: persist-read` on amd64, aarch64, and riscv64 against the same image afterward (cross-arch resume, matching the arch-neutral on-disk format `.claude/ARTEMIS.md` specifies). - `artemis-debug-roundtrip.img` — round-trip regression fixture created during that investigation. Known-good: format → self-test → write-test → reboot → resume → `PASS: persist-read`, confirmed 3 times in a row. Keep this in a passing state; if a future change breaks it, that's a real regression, not a stale-fixture artifact like `artemis.img` was. - `artemis-persist-test.img` — persistence round-trip test image (pre-existing; history/state not re-verified during the above investigation). - `artemis-poison.img` — a separate test image (exact scenario not documented elsewhere in the repo as of this writing; name suggests an adversarial/corruption test, not confirmed). These are regenerable QEMU raw disk images, not source — see `.claude/ARTEMIS.md` for the storage model they exercise.