Put a disk of your own in drive 1

make run-voyager and make run-cosmos now attach Disks/personal.img as the
second drive. It is made the first time it is wanted and then left alone:
a rule with no prerequisites, so make never looks at it again.

NOT UNDER build/, and that is the whole point. Everything else in this
repository is made from source and can be thrown away without losing
anything, so 'clean' empties build/ without a thought - and a disk of your
own that a clean deletes is not a disk of your own. It is the one place
here where something MADE ON THE MACHINE can live, which starts to matter
the moment there are tools on it that make things.

Disks/ is in .gitignore for the same reason: what you make on the machine
is yours and not the repository's.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW

Programs/CosmOS/README.md

@@ -841,6 +841,18 @@ file` - which it is, since there is nowhere for the rest of it to be.
 remembers the drive it was opened on and returns there for each block. Between them the copy
 walks back and forth without `Copy` itself knowing there is more than one disk.
 
+### A Disk Of Your Own:
+
+`make run-voyager` puts a second disk in **drive 1**, at `Disks/personal.img`. It is made the
+first time it is needed and then left alone: never rebuilt, never cleaned, never committed.
+
+That last part is the point. Everything else in this repository is made from source and can be
+thrown away without losing anything - but a disk is where something *made on the machine*
+lives, and a disk that `make clean` deletes is not a disk of your own. It sits outside
+`build/` for exactly that reason, and `Disks/` is in `.gitignore`.
+
+Delete it by hand if you ever want a fresh one.
+
 ### Where A Program Is Looked For:
 
 Three places, tried in order: