1 files changed, 19 insertions, 2 deletions

diff --git a/CONTEXT.md b/CONTEXT.md
index aa9385b..39ce0bd 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -186,8 +186,25 @@ Single Rust crate (`x86_64-unknown-uefi` target).  Module breakdown:
   `-device ide-hd,drive=disk,bus=ide.0` puts the data disk on AHCI port
   0; the ESP gets `bus=ide.1`.  (The implicit `-drive file=fat:rw:esp`
   otherwise grabs port 0.)  Make targets (`run`, `run-gui`, `debug`)
-  attach `$(DISK_IMG)` (default `/tmp/disk.img`).  OVMF writes its
-  `NvVars` varstore file onto the first FAT volume — harmless.
+  attach `$(DISK_IMG)` (default `/tmp/disk.img`) and auto-create it when
+  missing.  OVMF writes its `NvVars` varstore file onto the first FAT
+  volume — harmless.
+
+  The whole disk workflow is scripted (no manual mkfs/mcopy):
+
+- `make disk` / `./scripts/mkdisk.sh` — create the FAT32 image with
+    `mkfs.fat -C` (the flag that actually creates the file; plain
+    `mkfs.fat` needs an existing file), label `RSDOS`, seed from
+    `seed/` via mtools; `--fresh` re-formats, `--size 128M` sizes it
+- `make inspect` — `mdir -i` listing of the image (mtools)
+- `make test-disk` / `./scripts/test-disk.sh` — full automated round
+    trip: build → deploy → ensure image → boot QEMU headless → drive
+    the shell via `sendkey` through the monitor (`ls /disk`, `mkdir`,
+    `echo >`, `cat`, `poweroff`) → fsck-clean check → `mtype` verifies
+    the written file survived poweroff
+- `./scripts/sendkeys.py` — types lines into the guest via the QEMU
+    monitor (`--sock`, US layout, named keys for punctuation; bare
+    `-`/`.`/`/` are not valid sendkey names)
 
 ## Known issues / perf notes